usb disconnect

Bug #89974 reported by Jowi
6
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-2.6.17-11-generic

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-2.6.17-11-generic keyboard and mouse does not function.
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-2.6.17-10-generic works fine.

Revision history for this message
Brian Murray (brian-murray) wrote :

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.
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://wiki.ubuntu.com/DebuggingKernelProblems . Thanks in advance!

Changed in linux-source-2.6.17:
assignee: nobody → brian-murray
status: Unconfirmed → Needs Info
Revision history for this message
Jowi (k4p0w3r) wrote :

as my keyboard does not work while in 2.6.17-11-generic I will try to find the relevant info for you.

$ uname -a (not the one i have problem with)
Linux whitebox 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux

Revision history for this message
Jowi (k4p0w3r) wrote :
Revision history for this message
Jowi (k4p0w3r) wrote :
Revision history for this message
Jowi (k4p0w3r) wrote :
Changed in linux-source-2.6.17:
assignee: brian-murray → nobody
status: Needs Info → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.17:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Changed in linux-source-2.6.17:
status: Confirmed → Invalid
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

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.

Revision history for this message
Jim Lieb (lieb) wrote :

This bug report was marked as Incomplete a while ago and has not had any feedback to provide the requested information. As a result this bug is being closed. Please reopen if this is still an issue in the latest Karmic 9.10 Alpha release http://cdimage.ubuntu.com/releases/karmic/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.