On 10/13/2010 09:34 PM, Maxim Levitsky wrote: > > Nope, still same problem. > Maybe more keys were released, but still > pressing Alt+SysRQ+g second time doesn't break to the debugger. > > Thanks for trying this out Maxim. I have to wonder if part of the problem is the way that raw events can propagate directly via the old keyboard interface vs the input layer. I had noticed something somewhat similar with an xorg.conf which appeared to be using both the raw keyboard and the input layer for input. I was having all sorts of problems until I changed the xorg.conf settings to use the input layer. I noticed that even pressing the up arrow in an xterm was invoking the screen shot mechanism for example. Perhaps you can provide some more data to see if this is a similar problem or not. On the Fedora 13 test system I made sure the following were commented out in the xorg.conf file. # InputDevice "Keyboard0" "CoreKeyboard" # Option "AllowEmptyInput" "off" This had resolved the issue at least for the system with the Intel graphics chip and non-usb keyboard. The next step might be to have you run with an instrumented kernel if this is not the issue, and of course if you are willing to help further debug this. Thanks, Jason. -- 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
