On Sat, 17 Dec 2005, Willi Mann wrote: > Ok, here is what I did: > cat 2t > -> minimize the gnome-terminal > -> surfed the web > -> suddenly mouse died > -> Strg + Alt + F1, Alt+ F7 > -> reopened the terminal > -> marked the last > 200 lines > -> pasted in file > -> grepped for the mouse identifier 002:01 > here are the last lines of that output:
> ddd8de40 618383777 S Ii:002:01 -115 4 = 000000ff > ddd8de40 618431747 C Ii:002:01 0 4 = 000000ff > ddd8de40 618431774 S Ii:002:01 -115 4 = 000000ff > ddd8de40 723190277 C Ii:002:01 -84 0 > ddd8de40 769897561 S Ii:002:01 -115 4 = 000000ff > ddd8de40 769910480 C Ii:002:01 0 4 = 00838200 > ddd8de40 769910495 S Ii:002:01 -115 4 = 00838200 > > Does that somehow help to track it down? The event in µs 723190277 seems > very suspicious to me. Yes indeed. This looks very similar to the problem reported in http://bugzilla.kernel.org/show_bug.cgi?id=4916 See especially comment #19. It's possible that the patch adding an HID reset routine (the last attachment in the bug report) will work for you. You might have to fiddle with it a little, because it is now four months old. This _should_ have shown up in the dmesg log if you had CONFIG_USB_DEBUG turned on. Make sure you have it on when running more tests. Alan Stern -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
