system continuously boots/reboots when usb wireless keyboard is plugged in

Bug #42297 reported by Luis Villa
12
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Invalid
Medium
Unassigned
linux-source-2.6.20 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

With latest kernel and a new adesso keyboard:
http://www.adesso.com/products_detail.asp?productid=281

my desktop box gets 1-2 seconds into the kernel's boot sequence and immediately reboots. Remove the keyboard, boot, and plug it in during boot, and everything works like a charm. No idea where to start debugging this one- pointers welcome.

May be related to bug 40933, but not sure.

Note: the original reporter indicated the bug was in package 'kernel-image-2.6'; however, that package was not published in Ubuntu.

Revision history for this message
Luis Villa (luis-villa) wrote :

Still occurs with 2.6.20 in current feisty. (Was originally 2.6.15, and probably before that, though I don't recall.)

Revision history for this message
Ben Collins (ben-collins) wrote :

Do not change the target when it's still known not to work.

Revision history for this message
Luis Villa (luis-villa) wrote :

Apologies. It is... uh... 'vastly unobvious' WTF you're supposed to do in malone in that situation.

Revision history for this message
Ben Collins (ben-collins) wrote :

Please test the upcoming 2.6.20-4 kernel. I saw a fix go in that sounded similar to your problem.

Changed in linux-source-2.6.20:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Luis Villa (luis-villa) wrote :

Will take a look; am not in the same city as the afflicted box and won't be until Monday, so some time next week.

Revision history for this message
Luis Villa (luis-villa) wrote :

Still happens with latest feisty kernel (2.6.20-4-generic).

Revision history for this message
Paul Sladen (sladen) wrote :

How utterly crazy. One possibility is a watchguard reboot (maybe by the BIOS) if the IR transceiver is drawing more current on the USB than is allowed.

Do you see any message just before the reboot if you try to boot with '(recovery mode)' ?

Revision history for this message
Luis Villa (luis-villa) wrote :

Unfortunately, in a bit of a fit the other night, I chucked the keyboard across the room (yay wireless!), so it is sitting in some large-ish pieces ATM. I'll try to plug it in and see if I can still duplicate the problem later this week.

Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
mike (mikehu4722) wrote :

Any solution to this yet ? I experienced the same continuous rebooting events overnight.
I tried the same sequence as above (Remove the keyboard, boot, and plug it in during boot,),
and the unit is still down, won't recover at all.

My kernel is 2.6.17-11. ( I rebooted with 2.6.17-10 from the box as well, end up the same results)
PC is Dell/Optiplex/SX280

Any advice or suggestion on how to rescue it back is highly appreciated..

Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

This bug has had no activity for a considerable period. This is a check to see if there is still interest in investigating this bug report.
Sounds like Luis is no longer available for testing.
Luis, I gather this was not a continuing issue with your replacement keyboard? (ie. the issue is definitely related to the keyboard specified in the original bug report).
Has anyone with this issue tested it against any later releases?

Changed in linux-source-2.6.15:
status: New → Incomplete
Revision history for this message
Luis Villa (luis-villa) wrote :

Yeah, that is correct; I can no longer duplicate with current keyboard/kernel. (I'd offer to send someone the keyboard to debug, but like I said I threw it across the room at some point. ;)

Changed in linux-source-2.6.20:
assignee: ubuntu-kernel-team → nobody
status: Confirmed → Incomplete
Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

Closing.

Changed in linux-source-2.6.15:
status: Incomplete → Invalid
Changed in linux-source-2.6.20:
status: Incomplete → Invalid
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.