June 2013 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] kernel-default-base-2.6.29-5.2.x86_64 rpm errors
by Dave Plater 18 Jul '24

18 Jul '24

Hi, I'm busy updating to the latest factory kernel and have received the following errors from kernel-default-base installation (I did insert a blank dvd during the installation of the rpm by zypper):- WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sd_mod.ko needs unknown symbol crc_t10dif WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol register_cdrom WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_ioctl WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_media_changed WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_get_media_event WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_release WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_open WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol unregister_cdrom WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_number_of_slots And then these errors which I think IIRC happened before when the kernel was first split into three:- Kernel image: /boot/vmlinuz-2.6.29-rc8-5-default Initrd image: /boot/initrd-2.6.29-rc8-5-default Root device: /dev/disk/by-id/ata-WDC_WD800JB-00JJC0_WD-WMAM9RA78067-part3 (/dev/sda3) (mounted on / as xfs) Resume device: /dev/disk/by-id/ata-WDC_WD800JB-00JJC0_WD-WMAM9RA78067-part2 (/dev/sda2) FATAL: Module processor not found. WARNING: no dependencies for kernel module 'processor' found. FATAL: Module thermal not found. WARNING: no dependencies for kernel module 'thermal' found. FATAL: Module ata_generic not found. WARNING: no dependencies for kernel module 'ata_generic' found. FATAL: Module piix not found. WARNING: no dependencies for kernel module 'piix' found. FATAL: Module ide_pci_generic not found. WARNING: no dependencies for kernel module 'ide_pci_generic' found. FATAL: Module fan not found. WARNING: no dependencies for kernel module 'fan' found. FATAL: Module xfs not found. WARNING: no dependencies for kernel module 'xfs' found. FATAL: Module usbhid not found. WARNING: no dependencies for kernel module 'usbhid' found. Kernel Modules: scsi_mod libata ata_piix edd ahci sd_mod usbcore ohci-hcd ehci-hcd uhci-hcd WARNING: /dev/shm/mkinitramfs.0drQsZ/mnt/lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sd_mod.ko needs unknown symbol crc_t10dif Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 22669 blocks Should I open a bug report about the errors which are possibly from inserting a dvd while the kernel rpm was installing? Regards Dave P -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 2

[opensuse-kernel] Modular drivers which could be built-in
by Jean Delvare 10 Mar '14

10 Mar '14

Hi all, Having worked on built-in drivers which could be modularized, I am now looking for modular drivers which could be built-in. Our policy is that drivers which are not hardware-specific and are needed on a majority of systems should be built into the kernel directly. So I checked which modules were loaded on my 4 systems. After filtering out hardware-specific modules, I am left with the following list: ACPI and thermal drivers: * button * processor * thermal_sys Block device drivers * cdrom * scsi_dh * scsi_dh_alua * scsi_dh_emc * scsi_dh_hp_sw * scsi_dh_rdac * sg * sr_mod Graphics helper drivers * drm * drm_kms_helper * i2c_algo_bit Filesystem drivers: * fuse * lockd * sunrpc CPU drivers: * microcode Sound drivers: * pcspkr * snd * snd_page_alloc * snd_pcm * snd_seq * snd_seq_device * snd_timer * soundcore If anyone has an opinion on whether these should be built into the kernel or left as modules, this is the right time to discuss it. My personal thoughts, with mostly x86 in mind: * The ACPI button and processor drivers could be built-in. Most x86 systems use ACPI and they supposedly all have at least one processor and one power button ;) And thermal_sys is selected by processor. * While all my systems have an optical drive, I know they have disappeared from many systems, both very small and very large ones, so leaving cdrom and sr_mod as modules seems fine. * I have no idea why/how sg is being loaded, it has no modalias and no other module depend on it. But /dev/sd* nodes are created so it is certainly useful. Hannes? * No idea what the scsi_dh* modules are about either, no modalias and no dependencies either. Hannes? * With DRM/KMS being the norm now, I believe drm and drm_kms_helper could be built-in, even though the former is quite large. drm selects i2c-algo-bit, most (all?) DRM/KMS drivers use it. Even servers have graphics chips. * I suppose fuse is only used on desktop machines by default, for gvfs, so having it as a module seems OK. * lockd and sunrpc are dependencies of nfs and nfsd. I suppose there are many users out there who don't serve nor mount NFS shares so modules make sense. * I think microcode could be unloaded after use, maybe for security reasons it might even be preferable, or just because there is simply no point in keeping it in memory. Thomas? Either way we should keep it modular. * For sound drivers, Takashi should know better than me. I suppose that the rationale for having these modular is that servers have no sound chip? -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

15 61

[opensuse-kernel] CONFIG_CC_STACKPROTECTOR
by richard -rw- weinberger 14 Dec '13

14 Dec '13

Hi! I'm wondering why CONFIG_CC_STACKPROTECTOR is disabled on openSUSE. Debian and Fedora seem to enabled it per default. What's the deal? -- Thanks, //richard -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

7 17

[opensuse-kernel] Debuginfo for x86_64 kernels (systemtap complaints about arch mismatch)
by Andrey Borzenkov 15 Jul '13

15 Jul '13

I'm trying to make systemtap work on 12.3 x86_64. Attempt to compile latencytap.stp from included examples gives bor@opensuse:/tmp> sudo stap latencytap.stp semantic error: ELF machine i?86| (code 3) mismatch with target x86_64 in '/usr/lib/debug/boot/vmlinux-3.7.10-1.11-desktop.debug' semantic error: while resolving probe point: identifier 'kernel' at latencytap.stp:51:7 source: kernel.function("deactivate_task") { ^ semantic error: no match semantic error: while resolving probe point: identifier 'kernel' at :62:7 source: kernel.function("activate_task") { ^ semantic error: while resolving probe point: identifier 'scheduler' at :81:7 source: probe scheduler.cpu_on { ^ Pass 2: analysis failed. Try again with another '--vp 01' option. Well, there is no debuginfo for x86_64, only for i586. Is it missing indeed or is it systemtap issue? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

5 7

[opensuse-kernel] [PATCH] armv7hl: Fix CuBox flavor build
by Dirk Müller 30 Jun '13

30 Jun '13

Hi, could you please merge the attached commit to master? TIA, Dirk

2 1

[opensuse-kernel] How to bisect the SUSE kernel?
by Stefan Seyfried 30 Jun '13

30 Jun '13

Hi all, please excuse me if the answer is obvious :-) Is there an easy way to bisect between two SUSE update kernels? The 12.2 update from 3.4.33 to 3.4.42 broke my parallel printer -- the device is simply not detected anymore (it's on a NetMos Technology PCI 9835 Multi-I/O Controller, "parport_serial" driver, seria ports on the same card/chip still work). An update to the current tumbleweed kernel also does not help, so something got broken for me after 3.4.33... I already looked through the diff of vanilla 3.4.33 --> 3.4.42 and can't imagine what would cause this, so I'm suspecting a strange side effect of something totally different. This is where I think bisection would come in handy :-) How would I best do that? Best regards, Stefan -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 2

[opensuse-kernel] [PATCH] Fix ARM kernel-lpae build
by Guillaume Gardet 27 Jun '13

27 Jun '13

Hi, please find in attachment a patch against master to fix ARM kernel-lpae build. (Build it as zImage instead of uImage). Regards, Guillaume

1 0

[opensuse-kernel] [PATCH] Fix kernel-cubox build
by Dirk Müller 26 Jun '13

26 Jun '13

Hi, could you please merge the patch below to master.... TIA, Dirk

2 1

[opensuse-kernel] zcache=deflate no longer works in kernel HEAD
by Cristian Rodríguez 26 Jun '13

26 Jun '13

Hi: With current 3.10.rcX kernels, booting with zcache=deflate no longer works, 3.9 is fine however [ 0.815330] zcache: compressor initialization failed "deflate" module isin the initrd just like it was with 3.9.x. Any input about the issue is appreciated. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 3

Re: [opensuse-kernel] kernel-xen 3.9.2 leads to oops'es in domU xennet
by Jan Beulich 26 Jun '13

26 Jun '13

>>> On 26.06.13 at 03:16, Eugene Istomin <e.istomin(a)edss.ee> wrote: > I tested with > http://download.opensuse.org/repositories/Kernel:/HEAD/standard/x86_64/k > ernel-xen-3.10.rc6-2.1.g20cc894.x86_64.rpm: > Dom0 3.10.rc6 + DomU 3.4.50 -> OK > Dom0 3.10.rc6 + DomU 3.10.rc6 -> netif_poll+0x4ac/0xe80 [xennet] So - as expected - the same as before iiuc. In which case we continue to depend on understanding why all of the sudden these oddly shaped packets appear in the receive path, and so far Wei doesn't seem to have found time to look into this in depth (but I think you also didn't really help him in trying to repro this). > By the way, echo "options netbk bind=1" >> /etc/modprobe.d/99- > local.conf fixed inter-VM network bandwith in high pps. Is this correct way > to > fix issue http://www.novell.com/support/kb/doc.php?id=7009790 ? This is not "fixing" the issue, but trading one issue for another. And the document is pretty clear that either of "bind=1" or "tasklets=1" would have similar effects, so I'm not sure what your asking for anyway. Jan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0