USB device insertion causes total system lockup on Ubuntu 9.10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ModemManager |
Invalid
|
Undecided
|
Unassigned | ||
hotplug |
Incomplete
|
Undecided
|
Unassigned | ||
udev |
Incomplete
|
Undecided
|
Unassigned | ||
udev (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
affects udev
affects hotplug
affects ubuntu 9.10
On two separate systems I have upgraded from 9.04 to 9.10 I get a
complete, immediate and total system lockup when I install a specific
device in a USB port. The device is an AT&T Quicksilver GSM/HSDPA
Cellular modem, on 8.10 and 9.04 systems, lsusb shows the device as "Bus
002 Device 006: ID 0af0:d033 Option".
On 8.10 and 9.04 systems the device initially shows up as a CDROM
containing the driver and application software needed on an MS Windows
box. There is a linux package ( Ozerocdoff found at
http://
Manufacturer "Option" which uses udev to disable this "zerocd" and then
the Option Cellular Modem appears which works with the linux hso kernel
module. On a 9.10 system with or without Ozerocdoff installed I get
the lockup even before the CDROM or Modem appears or is logged.
The device worked fine in the same systems before the 9.04 to 9.10
upgrade. Other USB devices work fine under 9.04 and 9.10. I have not
yet tried on a fresh 9.10 install only 9.04 to 9.10 upgrades.
The lockup is immediate and total. The only way I have found to
regain access to the systems is to remove the device, then do a hard
power cycle.
I cannot identify or recover any meaningful details from the log files
in /var/log.
I would appreciate any clues on how I can capture better debug
information on this situation. The immediate and total system lockup
has me stumped for where to go from here. I do realize the above is
insufficient to work with, I am asking for how to capture better
information for a proper bug report.
Thank you;
Patrick Hickel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkr
/KcAnA86BvzDb0k
=Q/Vp
-----END PGP SIGNATURE-----
Finally got a chance to come back to this. After swapping in a freshly wiped disk ( mke2fs -c -c ), I then did a total clean default Ubuntu 9.10 Desktop i386 install. So I am absolutely sure I am starting with a totally clean base. I wanted this because the two systems I worked with previously were both 9.04 to 9.10 upgrades as opposed to new clean installs.
So this time I know for sure there is nothing accidently carried forward through the upgrade process.
At this point I opened a terminal window and did "cd /var/adm ; tail -f messages" and left it running.
I then plugged the Option/AT&T Quicksilver GSM modem into the USB port.
My terminal window captured 10 new lines of /var/adm/messages after the device was inserted but before the system locked up and had to be power cycled. I had to hand write them on paper to save them for entry here, so please forgive any minor transcription errors.
usb 1-5: USB disconnect, address 5 buildd/ linux-2. 6.31/drivers/ net/usb/ hso.c: 1.2 Option Wireless
usb 1-5: new high speed USB device using ehci_hcd and address 9
usb 1-5: configuration #1 chosen from 1 choice
scsi 4: SCSI emulation for USB Mass Storage devices
usb 1-5: USB disconnect, address 9
hso: /build/
usbcore: registered new interface driver hso
usb 1-5: new high speed USB device using ehci_hcd and address 10
usb 1-5: configuration #1 chosen from 1 choice
hso0: Disabled Privacy Extensions
So it would appear the system is actually recognizing the initial ZeroCD function correctly, then correctly disconnects the ZeroCD device, and then somehow hands off to the hso driver to disable the ZeroCD and then re-registers the device as a new interface tied to the hso driver, at some point after the hso driver disables the Privacy Extensions I got the expected total system lockup.
Hopefully, this will provide a clue to someone.