After upgrading udev to any version beyond 046, I get the following oops when I plug in my AVM BlueFritz! USB bluetooth dongle: usb 2-2: new full speed USB device using address 2 usb 2-2: configuration #1 chosen from 2 choices Bluetooth: Core ver 2.6 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: BlueFRITZ! USB driver ver 1.1 Unable to handle kernel NULL pointer dereference at virtual address 00000004 printing eip: f9faa1a5 *pde = 00000000 Oops: 0000 [#1] PREEMPT SMP Modules linked in: bfusb firmware_class bluetooth tg3 snd_seq snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd_page_allocsnd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore pktcdvd cdrom uhci_hcd ehci_hcd usbcore psmouse aes_i586 dm_cryptdm_mod reiserfs CPU: 0 EIP: 0060:[<f9faa1a5>] Not tainted VLI EFLAGS: 00010246 (2.6.9) EIP is at firmware_loading_store+0xb5/0x100 [firmware_class] eax: 00000000 ebx: f9fac564 ecx: f9fac564 edx: 00000001 esi: eb739280 edi: 00000002 ebp: eb504fac esp: eb504f34 ds: 007b es: 007b ss: 0068 Process firmware.agent (pid: 7978, threadinfo=eb504000 task=eb2a4f30) Stack: 000000d0 eb255804 00000000 f9faa0f0 eb2f9f80 eb34d000 c01fc866 c03109d8 00000002 f9fac620 c0185e1b 00000002 f3bf76e0 eb227700 eb504fac c0185e71 c02d11c0 eb227700 00000002 c015315e eb504fac eb2552e4 eb2552dc b7e9d000 Call Trace: [<f9faa0f0>] firmware_loading_store+0x0/0x100 [firmware_class] [<c01fc866>] class_device_attr_store+0x36/0x50 [<c0185e1b>] flush_write_buffer+0x2b/0x40 [<c0185e71>] sysfs_write_file+0x41/0x60 [<c015315e>] vfs_write+0xfe/0x130 [<c0153241>] sys_write+0x41/0x70 [<c0106199>] sysenter_past_esp+0x52/0x71 Code: 0c 8b 74 24 10 8b 7c 24 14 83 c4 18 c3 83 f8 ff 75 95 eb ac bb 64 c5 fa f9 89 d9 f0 ff 0d 64 c5 fa f9 0f 88 72 09 0000 8b 46 48 <8b> 40 04 e8 63 39 1a c6 8b 46 48 c7 40 04 00 00 00 00 8b 46 48 <3>bfusb_probe: Firmware request failed bfusb: probe of 2-2:1.0 failed with error -5 usbcore: registered new driver bfusb Reproducible: Always Steps to Reproduce: 1. emerge udev (>046) 2. reboot 3. plug in device Actual Results: I get the above kernel oops message. Expected Results: The firmware should be loaded into the device. Downgrading udev to 046 solves the problem.
Forgot to mention: Kernel is 2.6.9.
Huh? Udev has nothing to do with the firmware stuff, nor should it be able to oops the kernel. really odd. Does this still happen with a 2.6.10-rc3 kernel?
I was also wondering about this, but verified it twice. As for kernel 2.6.10-rc3: It works now, but the first attempt to load the firmware still fails. I have to plug it out and in again to get the firmware into the device: usb 2-2: new full speed USB device using uhci_hcd and address 2 usb 2-2: configuration #1 chosen from 2 choices Bluetooth: Core ver 2.7 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: BlueFRITZ! USB driver ver 1.1 bfusb_probe: Firmware request failed bfusb: probe of 2-2:1.0 failed with error -5 usbcore: registered new driver bfusb usb 2-2: USB disconnect, address 2 usb 2-2: new full speed USB device using uhci_hcd and address 3 usb 2-2: configuration #1 chosen from 2 choices Bluetooth: BlueFRITZ! USB loading firmware Bluetooth: BlueFRITZ! USB device ready Bluetooth: L2CAP ver 2.6 Bluetooth: L2CAP socket layer initialized Bluetooth: RFCOMM ver 1.3 Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized
I have been running 2.6.10-rc3 and 2.6.10 now for a while. The problem seems to be gone as I allready wrote in my previous message. However, bot kernel versions have proven to be quite unstable (at least for me). I get random (sometimes at boot time, sometimes during ebuild compilation, etc) system freezes with both of them. So I would prefer to stay with 2.6.9 and have the issue fixed in udev.
It's a kernel bug (for the most part) that we can't fix in 2.6.9.
and as such, I'm closing this.
