usb disconnect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
linux-source-2.6.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: linux-image-
Keyboard and mouse are PS/2 connected via a PS/2->USB adapter (due to lack of PS/2 ports on the intel mac mini).
After upgrade to linux-image-
Keyboard leds flash constantly. Keyboard show no reaction to keypresses. Mouse cursor is not moving. No other USB devices are connected.
/var/log/messages show multiple USB disconnect and redetections.
[short version of a very long log:]
Mar 5 22:18:00 localhost kernel: [17179602.916000] usb 4-2: new low speed USB device using uhci_hcd and address 11
Mar 5 22:18:00 localhost kernel: [17179603.100000] usb 4-2: configuration #1 chosen from 1 choice
Mar 5 22:18:02 localhost kernel: [17179605.196000] usb 4-2: USB disconnect, address 11
Mar 5 22:18:03 localhost kernel: [17179606.192000] usb 4-2: new low speed USB device using uhci_hcd and address 12
Mar 5 22:18:03 localhost kernel: [17179606.376000] usb 4-2: configuration #1 chosen from 1 choice
Mar 5 22:18:06 localhost kernel: [17179608.724000] usb 4-2: USB disconnect, address 12
[end]
System seem to be functioning otherwise. GDM starts. Pressing the Power button shuts down the system cleanly.
Booting into linux-image-
Changed in linux-source-2.6.17: | |
assignee: | brian-murray → nobody |
status: | Needs Info → Confirmed |
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information. wiki.ubuntu. com/DebuggingKe rnelProblems . Thanks in advance!
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at http://