On Mon, 17 February 2014 Daniel J Blueman <daniel@xxxxxxxxx> wrote: > Across 5+ years of kernels, I've been seeing occasional (1-2 times per > day) key-stuck issues where eg a fn+delete combo repeats delete until > I press delete again. I've seen this happen with fn+ctrl+left, leaving > left held and likewise with right. > > This has occurred on Apple laptops, external USB keyboards and Dell > laptops, so seems like a linux USB input issue, as I haven't seen > occur on Windows or MacOS on the same hardware. > > It seems a good move for me to rebuild and run a kernel with some USB > HID instrumentation to locate this issue over time. Without apriori > knowledge of the linux USB input stack, what is a good initial > approach? I've seen some similar behavior on servers connected to a KVM switch (USB keyboard/mouse) where without apparent reason the ENTER key became pressed and did continuously send repeat events. Physically touching the KVM keyboard or unbinding&rebinding the HID keyboard solved the issue (on a console that triggers a busy loop of agettys on active vt). I've been tempted to attribute it to the KVM switch doing something when switching to another server via key-press (yes, some co-worker as at the KVM terminal when the getty load started). On the other hand, some other co-worker had "dead keyboard" issues though only under X, things still worked at console level, for quite some time now. Annoying but not regular enough to look further into it. If you want to look at what happens for you, monitoring the USB activity for your keyboard (in combination with output from event device) might be the most useful way (it would also catch details on when the USB side goes into power-saving, if at all). Bruno -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
