Boot hangs at Starting bluetooth (kernel 2.6.27-1 and -2) if device connected

Hi BanjoBoy,

Can you just confirm if you saw this same issue with the 2.6.26 kernel available previously in Intrepid. Thanks.

It new in 2.6.27 and if I boot into 2.6.26-5 (still have 2.6.26-5 and 2.6.27-2) it don't hang and the pvrusb2 is working.

Just to add some detail information, the pvrusb2 uses the following modules (lsmod):
pvrusb2 141272 0
dvb_core 86272 1 pvrusb2
cx2341x 21380 1 pvrusb2
v4l2_common 19840 2 pvrusb2,cx2341x
videodev 41344 1 pvrusb2
v4l1_compat 22404 2 pvrusb2,videodev
tveeprom 20228 1 pvrusb2
i2c_core 31892 3 pvrusb2,v4l2_common,tveeprom
usbcore 148848 6 libusual,pvrusb2,usbhid,ohci_hcd,ehci_hcd

This behavior happens when using other Hauppauge WinTV cards. I have run both a WinTV HVR-1800 (pci-e) and a WinTV HVR-1950 (usb) with the same effect in Kubuntu Intrepid. The system hangs during boot at "Starting Bluetooth" and requires a hard reset (it hangs again at "Stopping Bluetooth" after ctrl-alt-delete).

I have done some more testing and found that: if I boot without the pvrusb2 connected, then connect after login it does NOT load the firmware into the Hauppauge device as it should. If I then turn on my external USB HDD it will not register, so maybe the problem is in the usbcore module, like the usb devices are not registered anymore. Normally at every connect/disconnect the usbcore will log a message, but the does not happens anymore.

I reboot again without both pvrusb2 and usb hdd connected, then connect the usb hdd, it register and works, then connect the pvrusb2 and now the firmware loads, but still does not work and the /dev/video0 and /dev/radio0 devices is still not created.

Sorry, I forgot to write: I'm now using kernel 2.6.27-4-generic and I don't have a bluetooth device.

More testing. I boot without the Hauppauge WinTV USB2 device connected. My Compaq Presario laptop has 2 USB ports and I'm using one for the WinTV and one with a USB hub. After boot I disconnect the hub and reconnect and gets:
Sep 24 22:44:14 laptop kernel: [ 129.008065] usb 1-3: USB disconnect, address 2
Sep 24 22:44:14 laptop kernel: [ 129.008083] usb 1-3.1: USB disconnect, address 3
Sep 24 22:44:15 laptop kernel: [ 129.076182] usb 1-3.4: USB disconnect, address 4
Sep 24 22:44:26 laptop kernel: [ 140.480078] usb 1-3: new high speed USB device using ehci_hcd and address 5
Sep 24 22:44:26 laptop kernel: [ 140.655977] usb 1-3: configuration #1 chosen from 1 choice
Sep 24 22:44:26 laptop kernel: [ 140.658561] hub 1-3:1.0: USB hub found
Sep 24 22:44:26 laptop kernel: [ 140.659124] hub 1-3:1.0: 4 ports detected
Sep 24 22:44:28 laptop kernel: [ 142.065546] usb 1-3.1: new low speed USB device using ehci_hcd and address 6
Sep 24 22:44:28 laptop kernel: [ 142.167642] usb 1-3.1: configuration #1 chosen from 1 choice
Sep 24 22:44:28 laptop kernel: [ 142.197995] input: Microsft Microsoft Wireless Desktop Receiver 3.1 as /class/input/input11
Sep 24 22:44:28 laptop kernel: [ 142.224434] input,hidraw0: USB HID v1.11 Keyboard [Microsft Microsoft Wireless Desktop Receiver 3.1] on usb-0000:02:0e.2-3.1
Sep 24 22:44:28 laptop kernel: [ 142.240147] Fixing up Microsoft Wireless Receiver Model 1028 report descriptor
Sep 24 22:44:28 laptop kernel: [ 142.256277] input: Microsft Microsoft Wireless Desktop Receiver 3.1 as /class/input/input12
Sep 24 22:44:28 laptop kernel: [ 142.304441] input,hidraw1: USB HID v1.11 Mouse [Microsft Microsoft Wireless Desktop Receiver 3.1] on usb-0000:02:0e.2-3.1
Sep 24 22:44:28 laptop kernel: [ 142.388689] usb 1-3.4: new high speed USB device using ehci_hcd and address 7
Sep 24 22:44:28 laptop kernel: [ 142.492687] usb 1-3.4: configuration #1 chosen from 1 choice
Sep 24 22:44:28 laptop kernel: [ 142.493801] hub 1-3.4:1.0: USB hub found
Sep 24 22:44:28 laptop kernel: [ 142.494257] hub 1-3.4:1.0: 4 ports detected

Then connect a USB-flashstick and gets:
Sep 24 22:45:59 laptop kernel: [ 233.400421] usb 1-3.4.3: new high speed USB device using ehci_hcd and address 8
Sep 24 22:45:59 laptop kernel: [ 233.547774] usb 1-3.4.3: configuration #1 chosen from 1 choice
Sep 24 22:46:00 laptop kernel: [ 234.226706] usbcore: registered new interface driver libusual
Sep 24 22:46:00 laptop kernel: [ 234.301566] Initializing USB Mass Storage driver...
Sep 24 22:46:00 laptop kernel: [ 234.305571] scsi2 : SCSI emulation for USB Mass Storage devices
Sep 24 22:46:00 laptop kernel: [ 234.316217] usbcore: registered new interface driver usb-storage
Sep 24 22:46:00 laptop kernel: [ 234.319708] USB Mass Storage support registered.
Sep 24 22:46:05 laptop kernel: [ 239.323153] scsi 2:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS
Sep 24 22:46:07 laptop kernel: [ 241.710501] sd 2:0:0:0: [sdb] 15638528 512-byte hardware sectors (8007 MB)
Sep 24 22:46:07 laptop kernel: [ 241.715751] sd 2:0:0:0: [sdb] Write Protect is off
Sep 24 22:46:07 laptop kernel: [ 241.732375] sd 2:0:0:0: [sdb] 15638528 512-byte hardware sec...

2.6.27-5 kernel exhibits the same behavior, only it freezes on a PAM notification immediately after the "Starting Bluetooth" now.

2.6.27-7 and it still happens on my box. Is it an upstream problem ? Or something that happens only with the Ubuntu flavour ?

I tried to install the new Mandriva 2009, which also uses the 2.6.27 kernel and it got the same problem, so I think it's a general kernel problem.

workaround from pvrusb2 mailing list (http://www.isely.net/pipermail/pvrusb2/2008-October/001918.html)

aarne@mythtv:~$ cat /etc/modprobe.d/pvrusb2
options pvrusb2 initusbreset=0

Thank you! The workaround works.

Thank you! I've been booting into 2.6.26-5 for a month now, and things have been slowly breaking around it.

This should be trivial to create a patch for, so hopefully it will make the release.

According to Mike Isely (the author of the pvrusb2 driver) a fix should be in the next upstream stable kernel release (2.6.27.3 I guess), so hopefully the Ubuntu Kernel team will pull it in.

Hi Everyone,

I just wanted to add a note that the Ubuntu kernel team is hoping to keep the Intrepid kernel in sync with the upstream stable 2.6.27.x kernels through Stable Release Updates - http://wiki.ubuntu.com/StableReleaseUpdates . So with that said, this patch should be pulled in and available I'm guessing in a post Intrepid kernel update. Hope that helps, and thanks for your patience.

I have the same problem in ubuntu 8.04 with the 2.6.24-21 kernel and a different USB device: the Keyspan USA-19QW. The relevant module list from lsmod is:
keyspan 128772 0
usbserial 35816 2 keyspan,ftdi_sio
usbcore 146412 6 keyspan,ftdi_sio,usbserial,ehci_hcd,uhci_hcd

Booting hangs when "Starting Bluetooth" appears.

This is on a Dell Inspiron 9300 with NO bluetooth interface.

What other testing should I do?

Another note.. the keyspan module wasn't included in Ubuntu until this kernel update, so I can test with earlier versions and was never able to get it to work.

er, my previous message supposed to read "can't test with earlier versions"... but that may be incorrect anyway, becuase my desktop is running Ubuntu 8.04 with 2.6.24-19 and it has the driver and works (see below)..

On my laptop I tried to use the workaround that apparently works with the pvrusb2 driver. I added options keyspan initusbreset=0 to my modprobe.d/options file, but this just causes the keyspan module to not even be loaded when the device is plugged in.

If I plug in the Keyspan device after booting, the status indicator LED on it begins to blink, but the device doesn't show up under /dev/ like it should.

I have also tested the device on my desktop computer (2.6.24-19) and it doesn't have this problem at all. I'm going to boot back into that kernel with my laptop and see if it works.

Sure enough, the problem does not exist in 2.6.24-19 with either my laptop or desktop computer.

So it was introduced in -20 or -21. Unfortunately I don't have -20 to test with.

Oddly enough, the problem has fixed itself for my case.

I'm having the same exact issue on my pc with is a Gateway X500 desktop PC. I have a WinTV PVR2 USB2 card and when I attempt to boot ubuntu interpid with it connected to the pc, the pc hangs and have to do a hard power off. If I did not search through the forums and did a google search I would have not known why my pc is not able ot boot and find a workaround for it.

Hi Guys,

You'll likely want to track bug 294155 which is tracking the 2.6.27.4 upstream stable kernel patch set being merged into the Intrepid kernel via a Stable Release Update. It contains the following patch which I assume will resolve this bug:

1b146f86965053c2496f9ce22c9e26a770930c66 V4L/DVB (9300): pvrusb2: Fix deadlock problem

For those of running Intrepid, it would be great if you could test intrepid-proposed and verify this is resolved. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thanks.

I had the bug with kernel 2.6.27.7-16. It was solved in proposed kernel 2.6.27-8.17 but reintroduced in normal update 2.6.27-9.19

Hi Firefox,

That seems a bit strange. Can you test the 2.6.27-10 kernel currently in intrepid-proposed? Thanks.

Hi Leann,

2.6.27-10 kernel in intrepid-proposed boots fine with my WinTV PVR USB 2 connected.

Thanks

Marking as Fix Committed since there's an intrepid-proposed package that is purported to fix the issue.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

The kernel that was in -proposed that fixed this bug has since moved to -updates. Moving this from Fix Committed to Fix Released.