June 2011 - 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] [patch #2 0/5] scripts/sequence-patch.sh: Add some useful options
by Jeff Mahoney 05 Oct '11

05 Oct '11

Hi all - There are a few things I do every time I expand the source tree with sequence-patch.sh. Or, rather, things I should do and forget to do a lot. The first I always remember to do: Copy the config I want to test with to my build directory. The second I forget more often than not: Expand the kABI references into my build directory. One of the things that bites me occasionally is when there are kABI changes that go un-noticed until the automated build checker flags them and sends me an email yelling at me for my carelessness. This patch adds three options to scripts/sequence-patch.sh to take care of these automatically. --build-dir=PATH allows you to specify the build directory you'll be using. It will create the directory if it doesn't exist. It defaults to $PATCH_DIR. --config=ARCH-FLAVOR allows you to specify the config you'll use. It will copy the config to your build directory. It is not a fatal error if the config does not exist. It will just not copy one. --kabi allows you to direct sequence-patch to expand the kABI references into your build directory. Since the references are arch/flavor specific, it depends on --config=ARCH-FLAVOR. It is not a fatal error if the kABI reference doesn't exist since this is always the case in the master branch. The --build-dir PATH is subject to shell expansion. It is expanded late enough in the script that most variables should be available. There are also three new variables available when --config is used: $CONFIG contains the --config contents. $CONFIG_ARCH contains the arch part of the config. $CONFIG_FLAVOR contains the flavor part. For reference, I have this in my .bashrc: export SEQUENCE_PATCH_ARGS="--config=x86_64-desktop --build-dir=~/src/scratch/build/\$CONFIG_ARCH/linux-\$SRCVERSION-\$TAG-\$CONFIG_FLAVOR --kabi" I've also added patches for --ctags and --cscope which will automatically generate the databases for either of those tools in the build directory after the source tree is expanded. - Issues addressed in patchset #2: - Help text is now a here document for easy addition of more documentation - Explanation of which variables are allowed by --build-dir - Missing rpm/modversions script is not an error on older branches - Missing symvers files are not errors - Uses true/false for simple feature flags -Jeff -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

5 13

[opensuse-kernel] TOMOYO for 12.1?
by Marcus Meissner 22 Jul '11

22 Jul '11

Hi, Folks in #opensuse-security were asking what stops TOMOYO from being enabled in newer kernels. FATE#310292 https://bugzilla.novell.com/show_bug.cgi?id=668381 Not sure what the issue is with enabling it. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

7 11

[opensuse-kernel] Workshop on profiling, tracing, debugging both userspace and kernelspace for openSUSE conference
by Andreas Jaeger 02 Jul '11

02 Jul '11

Kernel developers, I've seen some requests for a workshop (see $subject) for the openSUSE conference. Are there any volunteers? Details on how to submit a proposal: http://news.opensuse.org/2011/06/02/opensuse-conference-cfp-going-strong/ You can also submit other proposals that you like! Andreas -- Andreas Jaeger, Program Manager openSUSE aj(a){novell.com,suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

7 10

[opensuse-kernel] preload-kmp madness
by Ismail Doenmez 30 Jun '11

30 Jun '11

Hi; Everytime kernel is updated I see something similar to this: Problem: preload-kmp-desktop-1.2_k3.0.0_rc3_3-66.7.x86_64 requires kernel-desktop = 3.0.rc3-3, but this requirement cannot be provided deleted providers: kernel-desktop-3.0.rc3-3.1.x86_64 Solution 1: do not keep preload-kmp-desktop-1.2_k3.0.0_rc3_3-66.7.x86_64 installed Solution 2: do not install kernel-desktop-3.0.rc4-2.2.x86_64 Solution 3: break preload-kmp-desktop by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c] (c): I think preload-kmp is the system similar to DKMS, is there any work going to replace kmp with DKMS which I _think_ (maybe naively?) would create less update problems? Regards. -- Ismail Dönmez - openSUSE Booster SUSE LINUX Products GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

7 9

[opensuse-kernel] crash with kernel 2.6.39-2 (factory) & usb eicon 225 umts/3g
by Bruno Friedmann 29 Jun '11

29 Jun '11

When I try to plug (by mistake) in an usb3 port I get those messages in dmesg [ 9458.254834] usb 3-1: new full speed USB device number 2 using xhci_hcd [ 9458.279163] xhci_hcd 0000:0a:00.0: WARN: short transfer on control ep [ 9458.282150] xhci_hcd 0000:0a:00.0: WARN: short transfer on control ep [ 9458.285158] xhci_hcd 0000:0a:00.0: WARN: short transfer on control ep [ 9458.288217] xhci_hcd 0000:0a:00.0: WARN: short transfer on control ep [ 9458.289182] usb 3-1: New USB device found, idVendor=0af0, idProduct=6971 [ 9458.289191] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 9458.289196] usb 3-1: Product: Globetrotter HSDPA Modem [ 9458.289201] usb 3-1: Manufacturer: Option N.V. [ 9458.289204] usb 3-1: SerialNumber: Serial Number [ 9458.294560] xhci_hcd 0000:0a:00.0: WARN: Stalled endpoint [ 9458.298173] xhci_hcd 0000:0a:00.0: WARN: transfer error on endpoint [ 9596.489031] INFO: task mtp-probe:15604 blocked for more than 120 seconds. [ 9596.489038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 9596.489043] mtp-probe D ffffffff81605060 0 15604 3011 0x00000004 [ 9596.489054] ffff88024967fbe0 0000000000000086 0000000000000000 ffff88024967ffd8 [ 9596.489065] ffffffff81165e75 ffff88024967ffd8 ffff88024967ffd8 ffff88024967ffd8 [ 9596.489074] ffffffff81a0b020 ffff880280318280 00ff8804102e4e40 ffff88040b3c48e8 [ 9596.489084] Call Trace: [ 9596.489111] [<ffffffff8156849b>] __mutex_lock_slowpath+0x11b/0x1d0 [ 9596.489124] [<ffffffff81567fca>] mutex_lock+0x1a/0x40 [ 9596.489135] [<ffffffff813c0a95>] usbdev_open+0x135/0x280 [ 9596.489150] [<ffffffff811522c9>] chrdev_open+0x1d9/0x2e0 [ 9596.489162] [<ffffffff8114c00f>] __dentry_open+0x18f/0x3b0 [ 9596.489174] [<ffffffff8115bf58>] do_last+0x3e8/0x7f0 [ 9596.489186] [<ffffffff8115d671>] path_openat+0xd1/0x3f0 [ 9596.489196] [<ffffffff8115d9d5>] do_filp_open+0x45/0xb0 [ 9596.489205] [<ffffffff8114d7a7>] do_sys_open+0xf7/0x1d0 [ 9596.489219] [<ffffffff81570712>] system_call_fastpath+0x16/0x1b [ 9596.489255] [<00007f337d5333d0>] 0x7f337d5333cf [ 9716.427390] INFO: task mtp-probe:15604 blocked for more than 120 seconds. [ 9716.427397] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 9716.427402] mtp-probe D ffffffff81605060 0 15604 3011 0x00000004 [ 9716.427413] ffff88024967fbe0 0000000000000086 0000000000000000 ffff88024967ffd8 [ 9716.427424] ffffffff81165e75 ffff88024967ffd8 ffff88024967ffd8 ffff88024967ffd8 [ 9716.427433] ffffffff81a0b020 ffff880280318280 00ff8804102e4e40 ffff88040b3c48e8 [ 9716.427442] Call Trace: [ 9716.427469] [<ffffffff8156849b>] __mutex_lock_slowpath+0x11b/0x1d0 [ 9716.427482] [<ffffffff81567fca>] mutex_lock+0x1a/0x40 [ 9716.427493] [<ffffffff813c0a95>] usbdev_open+0x135/0x280 [ 9716.427508] [<ffffffff811522c9>] chrdev_open+0x1d9/0x2e0 [ 9716.427520] [<ffffffff8114c00f>] __dentry_open+0x18f/0x3b0 [ 9716.427532] [<ffffffff8115bf58>] do_last+0x3e8/0x7f0 [ 9716.427544] [<ffffffff8115d671>] path_openat+0xd1/0x3f0 [ 9716.427554] [<ffffffff8115d9d5>] do_filp_open+0x45/0xb0 [ 9716.427562] [<ffffffff8114d7a7>] do_sys_open+0xf7/0x1d0 [ 9716.427576] [<ffffffff81570712>] system_call_fastpath+0x16/0x1b [ 9716.427609] [<00007f337d5333d0>] 0x7f337d5333cf [ 9836.365866] INFO: task mtp-probe:15604 blocked for more than 120 seconds. [ 9836.365873] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 9836.365878] mtp-probe D ffffffff81605060 0 15604 3011 0x00000004 [ 9836.365889] ffff88024967fbe0 0000000000000086 0000000000000000 ffff88024967ffd8 [ 9836.365900] ffffffff81165e75 ffff88024967ffd8 ffff88024967ffd8 ffff88024967ffd8 [ 9836.365909] ffffffff81a0b020 ffff880280318280 00ff8804102e4e40 ffff88040b3c48e8 [ 9836.365919] Call Trace: [ 9836.365947] [<ffffffff8156849b>] __mutex_lock_slowpath+0x11b/0x1d0 [ 9836.365959] [<ffffffff81567fca>] mutex_lock+0x1a/0x40 [ 9836.365971] [<ffffffff813c0a95>] usbdev_open+0x135/0x280 [ 9836.365986] [<ffffffff811522c9>] chrdev_open+0x1d9/0x2e0 [ 9836.365998] [<ffffffff8114c00f>] __dentry_open+0x18f/0x3b0 [ 9836.366011] [<ffffffff8115bf58>] do_last+0x3e8/0x7f0 [ 9836.366022] [<ffffffff8115d671>] path_openat+0xd1/0x3f0 [ 9836.366032] [<ffffffff8115d9d5>] do_filp_open+0x45/0xb0 [ 9836.366041] [<ffffffff8114d7a7>] do_sys_open+0xf7/0x1d0 [ 9836.366055] [<ffffffff81570712>] system_call_fastpath+0x16/0x1b [ 9836.366091] [<00007f337d5333d0>] 0x7f337d5333cf [ 9956.304331] INFO: task mtp-probe:15604 blocked for more than 120 seconds. [ 9956.304338] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 9956.304343] mtp-probe D ffffffff81605060 0 15604 3011 0x00000004 [ 9956.304354] ffff88024967fbe0 0000000000000086 0000000000000000 ffff88024967ffd8 [ 9956.304365] ffffffff81165e75 ffff88024967ffd8 ffff88024967ffd8 ffff88024967ffd8 [ 9956.304374] ffffffff81a0b020 ffff880280318280 00ff8804102e4e40 ffff88040b3c48e8 [ 9956.304384] Call Trace: [ 9956.304411] [<ffffffff8156849b>] __mutex_lock_slowpath+0x11b/0x1d0 [ 9956.304424] [<ffffffff81567fca>] mutex_lock+0x1a/0x40 [ 9956.304436] [<ffffffff813c0a95>] usbdev_open+0x135/0x280 [ 9956.304451] [<ffffffff811522c9>] chrdev_open+0x1d9/0x2e0 [ 9956.304463] [<ffffffff8114c00f>] __dentry_open+0x18f/0x3b0 [ 9956.304476] [<ffffffff8115bf58>] do_last+0x3e8/0x7f0 [ 9956.304487] [<ffffffff8115d671>] path_openat+0xd1/0x3f0 [ 9956.304497] [<ffffffff8115d9d5>] do_filp_open+0x45/0xb0 [ 9956.304506] [<ffffffff8114d7a7>] do_sys_open+0xf7/0x1d0 [ 9956.304520] [<ffffffff81570712>] system_call_fastpath+0x16/0x1b [ 9956.304555] [<00007f337d5333d0>] 0x7f337d5333cf [ 9956.304562] INFO: task lsusb:17610 blocked for more than 120 seconds. [ 9956.304565] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 9956.304569] lsusb D 0000000000000004 0 17610 3875 0x00000000 [ 9956.304578] ffff8802ec5e3be0 0000000000000086 0000000000000000 ffff8802ec5e3fd8 [ 9956.304586] ffffffff81165e75 ffff8802ec5e3fd8 ffff8802ec5e3fd8 ffff8802ec5e3fd8 [ 9956.304595] ffff880335e20880 ffff88027ec56240 00ff88042d6f2500 ffff8804109f08e8 [ 9956.304603] Call Trace: [ 9956.304615] [<ffffffff8156849b>] __mutex_lock_slowpath+0x11b/0x1d0 [ 9956.304626] [<ffffffff81567fca>] mutex_lock+0x1a/0x40 [ 9956.304635] [<ffffffff813c0a95>] usbdev_open+0x135/0x280 [ 9956.304647] [<ffffffff811522c9>] chrdev_open+0x1d9/0x2e0 [ 9956.304656] [<ffffffff8114c00f>] __dentry_open+0x18f/0x3b0 [ 9956.304667] [<ffffffff8115bf58>] do_last+0x3e8/0x7f0 [ 9956.304677] [<ffffffff8115d671>] path_openat+0xd1/0x3f0 [ 9956.304686] [<ffffffff8115d9d5>] do_filp_open+0x45/0xb0 [ 9956.304695] [<ffffffff8114d7a7>] do_sys_open+0xf7/0x1d0 [ 9956.304706] [<ffffffff81570712>] system_call_fastpath+0x16/0x1b [ 9956.304718] [<00007f9f3b84a3d0>] 0x7f9f3b84a3cf [10076.242939] INFO: task mtp-probe:15604 blocked for more than 120 seconds. [10076.242947] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10076.242952] mtp-probe D ffffffff81605060 0 15604 3011 0x00000004 [10076.242963] ffff88024967fbe0 0000000000000086 0000000000000000 ffff88024967ffd8 [10076.242975] ffffffff81165e75 ffff88024967ffd8 ffff88024967ffd8 ffff88024967ffd8 [10076.242984] ffffffff81a0b020 ffff880280318280 00ff8804102e4e40 ffff88040b3c48e8 [10076.242993] Call Trace: [10076.243021] [<ffffffff8156849b>] __mutex_lock_slowpath+0x11b/0x1d0 [10076.243033] [<ffffffff81567fca>] mutex_lock+0x1a/0x40 [10076.243045] [<ffffffff813c0a95>] usbdev_open+0x135/0x280 [10076.243061] [<ffffffff811522c9>] chrdev_open+0x1d9/0x2e0 [10076.243073] [<ffffffff8114c00f>] __dentry_open+0x18f/0x3b0 [10076.243085] [<ffffffff8115bf58>] do_last+0x3e8/0x7f0 [10076.243097] [<ffffffff8115d671>] path_openat+0xd1/0x3f0 [10076.243108] [<ffffffff8115d9d5>] do_filp_open+0x45/0xb0 [10076.243116] [<ffffffff8114d7a7>] do_sys_open+0xf7/0x1d0 [10076.243130] [<ffffffff81570712>] system_call_fastpath+0x16/0x1b [10076.243166] [<00007f337d5333d0>] 0x7f337d5333cf [10076.243173] INFO: task lsusb:17610 blocked for more than 120 seconds. [10076.243176] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10076.243181] lsusb D 0000000000000004 0 17610 3875 0x00000000 [10076.243189] ffff8802ec5e3be0 0000000000000086 0000000000000000 ffff8802ec5e3fd8 [10076.243197] ffffffff81165e75 ffff8802ec5e3fd8 ffff8802ec5e3fd8 ffff8802ec5e3fd8 [10076.243206] ffff880335e20880 ffff88027ec56240 00ff88042d6f2500 ffff8804109f08e8 [10076.243215] Call Trace: [10076.243226] [<ffffffff8156849b>] __mutex_lock_slowpath+0x11b/0x1d0 [10076.243238] [<ffffffff81567fca>] mutex_lock+0x1a/0x40 [10076.243247] [<ffffffff813c0a95>] usbdev_open+0x135/0x280 [10076.243258] [<ffffffff811522c9>] chrdev_open+0x1d9/0x2e0 [10076.243268] [<ffffffff8114c00f>] __dentry_open+0x18f/0x3b0 [10076.243278] [<ffffffff8115bf58>] do_last+0x3e8/0x7f0 [10076.243289] [<ffffffff8115d671>] path_openat+0xd1/0x3f0 [10076.243299] [<ffffffff8115d9d5>] do_filp_open+0x45/0xb0 [10076.243308] [<ffffffff8114d7a7>] do_sys_open+0xf7/0x1d0 [10076.243319] [<ffffffff81570712>] system_call_fastpath+0x16/0x1b [10076.243331] [<00007f9f3b84a3d0>] 0x7f9f3b84a3cf [10196.181174] INFO: task mtp-probe:15604 blocked for more than 120 seconds. [10196.181176] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10196.181177] mtp-probe D ffffffff81605060 0 15604 3011 0x00000004 [10196.181180] ffff88024967fbe0 0000000000000086 0000000000000000 ffff88024967ffd8 [10196.181183] ffffffff81165e75 ffff88024967ffd8 ffff88024967ffd8 ffff88024967ffd8 [10196.181185] ffffffff81a0b020 ffff880280318280 00ff8804102e4e40 ffff88040b3c48e8 [10196.181187] Call Trace: [10196.181212] [<ffffffff8156849b>] __mutex_lock_slowpath+0x11b/0x1d0 [10196.181226] [<ffffffff81567fca>] mutex_lock+0x1a/0x40 [10196.181237] [<ffffffff813c0a95>] usbdev_open+0x135/0x280 [10196.181252] [<ffffffff811522c9>] chrdev_open+0x1d9/0x2e0 [10196.181264] [<ffffffff8114c00f>] __dentry_open+0x18f/0x3b0 [10196.181276] [<ffffffff8115bf58>] do_last+0x3e8/0x7f0 [10196.181288] [<ffffffff8115d671>] path_openat+0xd1/0x3f0 [10196.181298] [<ffffffff8115d9d5>] do_filp_open+0x45/0xb0 [10196.181306] [<ffffffff8114d7a7>] do_sys_open+0xf7/0x1d0 [10196.181319] [<ffffffff81570712>] system_call_fastpath+0x16/0x1b [10196.181352] [<00007f337d5333d0>] 0x7f337d5333cf [10196.181358] INFO: task lsusb:17610 blocked for more than 120 seconds. [10196.181361] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10196.181366] lsusb D 0000000000000004 0 17610 3875 0x00000000 [10196.181374] ffff8802ec5e3be0 0000000000000086 0000000000000000 ffff8802ec5e3fd8 [10196.181383] ffffffff81165e75 ffff8802ec5e3fd8 ffff8802ec5e3fd8 ffff8802ec5e3fd8 [10196.181391] ffff880335e20880 ffff88027ec56240 00ff88042d6f2500 ffff8804109f08e8 [10196.181400] Call Trace: [10196.181411] [<ffffffff8156849b>] __mutex_lock_slowpath+0x11b/0x1d0 [10196.181422] [<ffffffff81567fca>] mutex_lock+0x1a/0x40 [10196.181431] [<ffffffff813c0a95>] usbdev_open+0x135/0x280 [10196.181442] [<ffffffff811522c9>] chrdev_open+0x1d9/0x2e0 [10196.181452] [<ffffffff8114c00f>] __dentry_open+0x18f/0x3b0 [10196.181462] [<ffffffff8115bf58>] do_last+0x3e8/0x7f0 [10196.181472] [<ffffffff8115d671>] path_openat+0xd1/0x3f0 [10196.181482] [<ffffffff8115d9d5>] do_filp_open+0x45/0xb0 [10196.181490] [<ffffffff8114d7a7>] do_sys_open+0xf7/0x1d0 [10196.181501] [<ffffffff81570712>] system_call_fastpath+0x16/0x1b [10196.181513] [<00007f9f3b84a3d0>] 0x7f9f3b84a3cf [10316.119850] INFO: task mtp-probe:15604 blocked for more than 120 seconds. [10316.119857] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [10316.119862] mtp-probe D ffffffff81605060 0 15604 3011 0x00000004 [10316.119873] ffff88024967fbe0 0000000000000086 0000000000000000 ffff88024967ffd8 [10316.119884] ffffffff81165e75 ffff88024967ffd8 ffff88024967ffd8 ffff88024967ffd8 [10316.119893] ffffffff81a0b020 ffff880280318280 00ff8804102e4e40 ffff88040b3c48e8 [10316.119903] Call Trace: [10316.119930] [<ffffffff8156849b>] __mutex_lock_slowpath+0x11b/0x1d0 [10316.119943] [<ffffffff81567fca>] mutex_lock+0x1a/0x40 [10316.119955] [<ffffffff813c0a95>] usbdev_open+0x135/0x280 [10316.119970] [<ffffffff811522c9>] chrdev_open+0x1d9/0x2e0 [10316.119982] [<ffffffff8114c00f>] __dentry_open+0x18f/0x3b0 [10316.119995] [<ffffffff8115bf58>] do_last+0x3e8/0x7f0 [10316.120007] [<ffffffff8115d671>] path_openat+0xd1/0x3f0 [10316.120017] [<ffffffff8115d9d5>] do_filp_open+0x45/0xb0 [10316.120026] [<ffffffff8114d7a7>] do_sys_open+0xf7/0x1d0 [10316.120039] [<ffffffff81570712>] system_call_fastpath+0x16/0x1b [10316.120076] [<00007f337d5333d0>] 0x7f337d5333cf Is there, beside a bug report, anything I can/should try/install ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

4 4

[opensuse-kernel] What Solves the BNC#673944?
by Andi Sugandi 25 Jun '11

25 Jun '11

Hi developers! Is the Bug #673944[0] related to Linux kernel or just (vendor) hardware's fault (bios, acpi?) ? If it is about the kernel, then what part of the kernel that "solves" the issue (c#9)? Thanks in advance. [0] https://bugzilla.novell.com/show_bug.cgi?id=673944 Best regards, -- Andi Sugandi. Bandung, Indonesia. openSUSE-id Team, openSUSE Community Member. http://en.opensuse.org/User:Andisugandi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] Disable autoloading of staging drivers?
by Stefan Seyfried 16 Jun '11

16 Jun '11

Hi all, after I found today that with 3.0-rc2 the "mei" module successfully prevents suspend with [39736.728116] pci_pm_suspend(): mei_pci_suspend+0x0/0xc0 [mei] returns 9999 I was wondering if it is a good idea to autoload staging drivers :-) mei being a staging driver and 3.0-rc2 being ancient, I have not yet opened a bug on LKML. I have, however, looked at the code and could not find out where the 9999 come from... -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 4

[opensuse-kernel] wrong sysctl in /boot/sysctl.conf-3.0.0-rc2-1-default
by Cristian Rodríguez 15 Jun '11

15 Jun '11

Hi: In current kernel head there is an entry in sysctl.conf-3.0.0-rc2-1-default that says: kernel.hung_task_timeout = 0 which is an invalid sysctl value it should say AFAICS kernel.hung_task_timeout_secs = 0 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 3

[opensuse-kernel] bnc #696474 and more weirdness
by Cristian Rodríguez 15 Jun '11

15 Jun '11

The following post is about the following bug that you must read to understand the rest... https://bugzilla.novell.com/show_bug.cgi?id=696474 After removing commit=100 from the mount options the symptoms mentioned in the bug report disappear, but still there is a mayor weirdness.. I call it, "everything is fine before midnight" Between 23:00 and 00:00 each day, cron jobs start rsync and various IO intensive processes, and it is when the apache server running in the same machine starts to segfault with random errors, sometimes there is not even a workable backtrace, memory gets corrupted somehow, It will keep segfaulting randomly even after rsync process has ended, the only solution is the reboot the box after those processes end. There is no kernel warning, error, I have run memtest86++ and memtester user-space utility, more than once, even for a complete night. The machine is not out of ram, it has at least 5 GB free and other 5GB cached. The only remotely related (????) warning I get is this: un 15 00:19:32 eq6 smartd[2555]: Device: /dev/twa0 [3ware_disk_00], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 110 to 111 Jun 15 00:19:32 eq6 smartd[2555]: Device: /dev/twa0 [3ware_disk_00], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 34 to 35 Googling says it is not something to worry about unless smart reports fail, neither the raid controller built-in error reporting nor smartd says nothing about broken disks. Everything is fine after reboot, until next midnight approaches.. Lossing hair here, any hints ? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 1

[opensuse-kernel] kernel package versioning
by Michal Marek 14 Jun '11

14 Jun '11

Hi, Today I finally got round to properly fix the versioning mess in master and the upstream branches (vanilla and linux-next). This mail is meant to document how it's supposed to work. You can skip to the table at the end of the mail for a summary. In upstream ~~~~~~~~~~~ Upstream git tags look like "v3.0-rc1", "v3.0-rc2", the final tag is going to be "v3.0" and the subsequent stable releases will be tagged as "v3.0.1", "v3.0.2" and so on. The tarballs are named after these tags, so we have linux-3.0-rc2.tar.bz2 that contains the linux-3.0-rc2 directory. HOWEVER: Several userspace programs expect the kernel release string be three numbers and fail if it isn't the case. This also affects depmod, so omitting the third zero would break all setups using modules. So the kernel continues to call itself "3.0.0-rc2" and this will probably stay for some time now. In short, there are two version numbers now: I'll refer to them as the "tarball" version and the "uname" version (might differ from the "tarball" version in the trailing zero). In openSUSE ~~~~~~~~~~~ The SRCVERSION variable in the config.sh file is set to the "tarball" version. The mkspec script takes this and generates two more versions: The "uname" version (appends a zero if necessary), that is used during the build (so the actual build didn't require any modifications in the end) and the "rpm" version. I used the fact that the build was broken anyway as an opportunity to revamp the way the rpm packages are numbered. The final releases will have three numbers, i.e. "kernel-desktop-3.0.0-...", "kernel-desktop-3.0.1-...", etc. However, -rc releases will use the "rcX" tag instead of the last zero, so the current package will look like "kernel-desktop-3.0.rc2-...". Letters sort before numbers in rpm, so this will not break ordering and at the same time you will be able to tell the upstream version from the rpm version easily. Until now, we abused the rpm Release: field for this, but this only worked in the Kernel:* projects and not in the official distribution. To summarize, the mapping will be like: rpm tarball uname -r kernel-desktop-3.0.rc2-* linux-3.0-rc2.tar.bz2 3.0.0-rc2-*-desktop kernel-desktop-3.0.0-* linux-3.0.tar.bz2 3.0.0-*-desktop kernel-desktop-3.0.1-* linux-3.0.1.tar.bz2 3.0.1-*-desktop The "*" above is the rpm Release: number assigned by the build service. I hope that despite the long mail, the scheme will actually be easy to understand, that would will be able to quickly tell what kernel is in the distro by just looking at the rpm packages. Michal PS: I didn't cover KMPs at all at this point, they might work or there might be some fixes needed, I'll look into this later. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

4 6

[opensuse-kernel] Kernel:HEAD failure
by Cristian Rodríguez 13 Jun '11

13 Jun '11

Hi: Currently Kernel:HEAD failed to build completely All packages fail with ake: Leaving directory `/usr/src/packages/BUILD/kernel-desktop-3.0/linux-3.0-rc2' ++ make -s kernelrelease -C /usr/src/packages/BUILD/kernel-desktop-3.0/linux-3.0-rc2 O=/usr/src/packages/BUILD/kernel-desktop-3.0/linux-obj + krel=3.0.0-rc2-1-desktop + '[' 3.0.0-rc2-1-desktop '!=' 3.0-rc2-1-desktop ']' + echo 'Kernel release mismatch: 3.0.0-rc2-1-desktop != 3.0-rc2-1-desktop' Kernel release mismatch: 3.0.0-rc2-1-desktop != 3.0-rc2-1-desktop + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.t9w0V6 (%prep) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

5 8

[opensuse-kernel] BNC #608060 Status
by Andi Sugandi 13 Jun '11

13 Jun '11

Hello developers! I filled a bug[0] about a year ago, and now find it can be resolved by installing these packages on openSUSE 11.4: rtl8192se-kmp-desktop-0019.1207.2010_k2.6.37.6_0.5-1.4.x86_64 rtl8192se-0019.1207.2010-1.4.x86_64 rtl8192se-firmware-0019.1207.2010-1.4.noarch *Btw, is it needed by all of those three packages or only rtl8192se-kmp-desktop to get the device work?* from driver:/wireless/11.4-update repository. Should I change the status to: RESOLVED - FIX *or* RESOLVED - UPSTREAM ? Because I have no idea about the "resolved" process, whether it is fixed by openSUSE Team or by upstream work. Thanks in advance. [0] https://bugzilla.novell.com/show_bug.cgi?id=608060 Best regards, -- Andi Sugandi. Bandung, Indonesia. openSUSE-id Team, openSUSE Community Member. http://en.opensuse.org/User:Andisugandi -- 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] How do I submit a new package to opensuse-contrib
by doiggl＠velocitynet.com.au 12 Jun '11

12 Jun '11

On Sat, 11 Jun 2011 19:51:47 +0200, Pavol Rusnak <prusnak(a)opensuse.org> wrote: > On 11/06/11 16:38, doiggl(a)velocitynet.com.au wrote: >> Hello >> How do I submit a new package to opensuse-contrib ? >> It does not exist in factory. >> It has been built in bs [1] and announced on [2][3] >> >> What do I do next for submission to opensuse-contrib ? > > In general, we try not to add more packages to Contrib and submit them > directly to Factory instead. This is somehow special case. Please ask on > opensuse-kernel(a)opensuse.org mailinglist what would be the best option ... Hello The above answer I got on the opensuse-contrib(a)opensuse.org [4] I'll re-ask the original question in this list. opensuse-kernel(a)opensuse.org How do I submit a new package to opensuse-contrib ? It does not exist in factory. It has been built in bs [1] and announced on [2][3] What do I do next for submission to opensuse-contrib ? Hopefully this is the correct list to ask. Thanks Glenn [1] https://build.opensuse.org/package/show?package=kernel-reiser4&project=home… [2] http://www.spinics.net/lists/reiserfs-devel/msg02830.html [3] https://reiser4.wiki.kernel.org/index.php/Main_Page [4] http://lists.opensuse.org/opensuse-contrib/2011-06/msg00005.html -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 1

[opensuse-kernel] Kernel:HEAD failure
by Cristian Rodríguez 11 Jun '11

11 Jun '11

Hi: Currently Kernel:HEAD failed to build completely All packages fail with ake: Leaving directory `/usr/src/packages/BUILD/kernel-desktop-3.0/linux-3.0-rc2' ++ make -s kernelrelease -C /usr/src/packages/BUILD/kernel-desktop-3.0/linux-3.0-rc2 O=/usr/src/packages/BUILD/kernel-desktop-3.0/linux-obj + krel=3.0.0-rc2-1-desktop + '[' 3.0.0-rc2-1-desktop '!=' 3.0-rc2-1-desktop ']' + echo 'Kernel release mismatch: 3.0.0-rc2-1-desktop != 3.0-rc2-1-desktop' Kernel release mismatch: 3.0.0-rc2-1-desktop != 3.0-rc2-1-desktop + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.t9w0V6 (%prep) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] FYI - an announcement on news.o.o.
by Andreas Jaeger 07 Jun '11

07 Jun '11

The news team just published "Get your fresh kernels from openSUSE and test Linux 3.0!" http://news.opensuse.org/2011/06/06/get-your-fresh-kernels-from-opensuse-an… test-linux-3-0/ Thanks Michal for your input on this! Andreas -- Andreas Jaeger, Program Manager openSUSE aj(a){novell.com,suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 2

Re: [opensuse-kernel] Will OpenSuse 12 release with pvops Kernel 3.0, and Xen to match?
by Jan Beulich 05 Jun '11

05 Jun '11

>>> 06/03/11 5:10 PM >>> >If so, will that be the pvops-capable kernel? Or a port, as is current, >to a non-pvops, traditional kernel? > >I'm looking to know if v12 will release with native/pvops Xen support >(http://blog.xen.org/index.php/2011/06/02/xen-celebrates-full-dom0-and-domu-…) >or whether we'll still need to use versions of SuSE's forward ported >kernels. A firm decision wasn't made afaik, but I'm personally expecting to continue the forward port route until the pv-ops code is really on par wrt features currently present in the forward ported version, and shows an acceptable rate of regressions. >If pvops, I gather that Xen itself will need to be compiled against/for >the pvops kernel. Is that also the plan for v12? Xen doesn't get built for a particular guest OS, even less a particular implementation of one. Jan

2 1

[opensuse-kernel] Will OpenSuse 12 release with pvops Kernel 3.0, and Xen to match?
by p17000＠operamail.com 03 Jun '11

03 Jun '11

@openSUSE:Factory_versions states "the current version of" kernel --> v2.6.39. I was informed in #opensuse-factory that that's going to be bumped to new '3.0' kernel, which ,iiuc, is "just" a version numbering change, with no functional changes (not 100% sure of that yet)? Is that correct? If so, will that be the pvops-capable kernel? Or a port, as is current, to a non-pvops, traditional kernel? I'm looking to know if v12 will release with native/pvops Xen support (http://blog.xen.org/index.php/2011/06/02/xen-celebrates-full-dom0-and-domu-…) or whether we'll still need to use versions of SuSE's forward ported kernels. If pvops, I gather that Xen itself will need to be compiled against/for the pvops kernel. Is that also the plan for v12? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0