January 2014 - 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] Keep 3.11.y kernel for openSUSE 13.1 updates?
by Takashi Iwai 12 Sep '14

12 Sep '14

Hi, Since 3.11.y maintenance was discontinued by Greg, Ubuntu took over it. It made me wonder: are we willing to continue 3.11.y for openSUSE 13.1 updates, just relying on Ubuntu? Or, can we just move on 3.12.y? Takashi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

27 80

[opensuse-kernel] [PATCH] Revert "HID: Fix logitech-dj: missing Unifying device issue"
by Rick Salevsky 24 Mar '14

24 Mar '14

Hi all, the attached patch for openSUSE 12.3 is the fix for bnc#828481. Ciao, -- Rick Salevsky, Trainee SUSE LINUX GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-538 - rsalevsky(a)suse.com SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)

2 1

[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] Why is CONFIG_X86_X32 enabled?
by Richard Weinberger 31 Jan '14

31 Jan '14

Hi! Why is CONFIG_X86_X32 enabled by default on openSUSE kernels? Currently the x32 ABI has 0 users and got obviously very poor testing so far. Dave Jones trinity does also not support it. This is a feature with no user space support in openSUSE, why do we need it? I'm very sure that CVE-2014-0038 is not the last horrid bug hidden in x32. -- Thanks, //richard -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

[opensuse-kernel] Acpi Warnings missing package ?
by Bruno Friedmann 19 Jan '14

19 Jan '14

I've seen recently a number of acpi warning on my Dell Precision Jan 18 12:03:10 c-3po kernel: ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20130725/tbfadt-395) Jan 18 12:03:10 c-3po kernel: ACPI Warning: \_SB_.PCI0.PEG0.VID_._DSM: Argument #4 type mismatch - Found [Integer], ACPI requires [Package] (20130725/nsarguments-95) Jan 18 12:03:10 c-3po kernel: ACPI Warning: \_SB_.PCI0.PEG0.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95) Jan 18 12:03:10 c-3po kernel: ACPI Warning: \_SB_.PCI0.PEG0.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95) Jan 18 12:03:10 c-3po kernel: ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20130725/utaddress-251) Jan 18 12:03:10 c-3po kernel: ACPI Warning: 0x0000000000000540-0x000000000000054f SystemIO conflicts with Region \GPIO 1 (20130725/utaddress-251) Jan 18 12:03:10 c-3po kernel: ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20130725/utaddress-251) Jan 18 12:03:10 c-3po kernel: ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \_SB_.PCI0.PEG0.VID_.GPSP 2 (20130725/utaddress-251) Jan 18 12:03:10 c-3po kernel: ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20130725/utaddress-251) Jan 18 12:03:10 c-3po kernel: ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \_SB_.PCI0.PEG0.VID_.GPSP 2 (20130725/utaddress-251) Jan 18 12:03:10 c-3po kernel: ACPI Warning: 0x0000000000007000-0x000000000000701f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130725/utaddress-251) kernel is 3.12.7-2.g78b11e9-desktop coming from kernel:stable and kernel-firmware version is 20130714git-38.1 same repository. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 3

[opensuse-kernel] btrfs crash at 97% space usage
by Cristian Rodríguez 18 Jan '14

18 Jan '14

Hi: In current kernel HEAD I have a btrfs crash on a filesystem that is 97% full.. While I was able to dmesg > crash with no error before the machine locked up and becomes unusable (CPU rages fan to full speed, freezes or causes a thermal shutdown) for some reason the "crash" file supposed to be written is not there anymore after reboot, I will try sending the output to a different device the next time it happens, but I wonder if you have any other suggestion how to debug the problem without a serial console. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 4

[opensuse-kernel] Opensuse 13.1 Xen guest OOPS @ "kernel BUG at .../kernel-xen-3.11.6/linux-3.11/mm/slab.c:3011!"
by ar16 17 Jan '14

17 Jan '14

I've installed Opensuse 13.1 as a Xen Guest at Linode.com. Booting via pvgrub to the Guest's opensuse kernel, kernel-xen-3.11.6-4.1.x86_64 I'm seeing intermittent Guest crashes. Seems to occur @/near ip(6)tables work ... but not reproducibly. on crash, @ the linode "lish" xen-console, I see: http://pastebin.com/1WPp01X4 which is, currently, limited only to 250 lines. Checking journalctl I see: http://pastebin.com/JjKQEevV Chatting @ linode IRC, I was pointed to this: Re: BUG: sleeping function called from invalid context at mm/slab.c:3060 https://lkml.org/lkml/2013/10/7/10 which similarly references BUG(a)/mm/slab.c as in my case. For reference, booting the Linode to their latest provided kernel ("Latest 64 bit (3.11.6-x86_64-linode35)"), instead, results in a stable environment; i.e., has yet to crash under any usage/load. (1) is this yet a known issue @ opensuse? (2) is it likely related to the lkml post? (3) what additional info, if any, is useful to troubleshoot? (4) does this belong @ -kernel or -virtual? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

5 10

[opensuse-kernel] variable boot device
by Felix Miata 17 Jan '14

17 Jan '14

Once upon a time, OS installed to sole HD as sda would stay sda even when PCI eSATA was both added and powered on at boot time. Not any more: host gx27b (PCI SiI3512=esata) 11.4 2.6.37 esata=sdb, / on ICH5 sda9 12.1 3.1.10 esata=sdb, / on ICH5 sda10 12.2 3.4.63 esata=sdb, / on ICH5 sda11 12.3 3.7.10 esata=sdb, / on ICH5 sda12 13.1 3.11.6 esata=sdb, / on ICH5 sda20 13.1 3.12.5 esata=sdb, / on ICH5 sda20 13.2 3.12.1 esata=NA, / on ICH5 sda21 13.2 3.12.1 esata=sda, (/ on ICH5 sdb21 non-existent; dracut emergency shell) host gx620 (PCI SiI3512=esata) 11.4 2.6.37 esata=sdb, / on ICH7 sda8 11.4 3.6.2 esata=sdb, / on ICH7 sda8 12.1 3.1.10 esata=sdb, / on ICH7 sda10 13.1 3.11.6 esata=sda, / on ICH7 sdb9 host gx745 (PCI SiI3114=esata) 11.4 2.6.37 esata=sdb, / on ICH8 sda8 11.4 3.6.2 esata=sdb, / on ICH8 sda8 12.1 3.1.10 esata=sdb, / on ICH8 sda10 13.1 3.11.6 esata=sda, / on ICH8 sdb9 Is there some kernel config option or cmdline option or anything else in latest distro releases that can ensure an internal (aka non-removable) HD attached to a motherboard SATA port gets its device name assigned prior to any (removable) USB device and prior to any (removable) (e)SATA device attached to a PCI slot device port, like it used to do automatically? It's really annoying for device names to vary according to which master boot menu selection one makes, or especially, whether an external device is powered up at boot time, and even more specially, when having an external device powered at boot time causes emergency shell instead of boot success. In the case of emergency shell example listed above on gx27b 13.2, both root= on cmdline and / mounting in fstab are using LABEL syntax, meaning, device names should be irrelevant in any event, as they apparently are for 13.1 on the other two hosts. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 34

[opensuse-kernel] cirrus fb textconsoles broken
by Ludwig Nussel 15 Jan '14

15 Jan '14

Hi, Current Factory has problems with text consoles when using the cirrus driver in qemu/kvm. Only a cursor shows up but no getty. The following message shows up in dmesg: [ 3.197938] fb: conflicting fb hw usage cirrusdrmfb vs simple - removing generic driver [ 3.199240] [drm:cirrus_vram_init] *ERROR* can't reserve VRAM [ 3.201360] cirrus 0000:00:02.0: Fatal error during GPU init: -6 The funny thing is that the text console works during installation. Any idea what could be wrong and how to fix it? With "-vga std" in qemu the getty shows up. In general I wonder what would be the best video driver to use in qemu? The requirement would be to be able to define a fixed resolution of the text console and X somehow and that UEFI works with it (for openQA). cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

6 14