Re: SysRq annoyance

Andreas Schwab (schwab@issan.informatik.uni-dortmund.de)
20 Apr 1998 13:39:57 +0200


Martin Mares <mj@atrey.karlin.mff.cuni.cz> writes:

|> Hi,
|>> Took a look at that annoying beeping that you get after a sysrq and it
|>> turns out that if you release alt before printscreen, alt gets "stuck"
|>> down. To try this out hit +alt +ps -alt -ps. Now you can just hit the
|>> right arrow to switch to the next console and everything is back to
|>> normal. Is this a bug in the keyboard handling code or a hardware quirk
|>> of the sysrq key? Any keyboard gurus out there know whats going on?

|> It's a known problem. In case you hold the sysrq combination, all
|> key codes are passed to the sysrq code without any other processing until
|> a SysRq release code is seen to prevent sysrq commands from being passed to
|> apps. Anyway, this has the side-effect you describe, but as I still think
|> of sysrq as of a hacker-only tool and I don't know of any trivial way how
|> to fix it, I don't plan doing anything with it.

FWIW, the m68k port already handles this quite nicely. All you have to do
is to still process modifier keys (ie, update shift_state) when in "sysrq
mode".

-- 
Andreas Schwab                                      "And now for something
schwab@issan.informatik.uni-dortmund.de              completely different"
schwab@gnu.org

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu