It is possible that when SysRq-G is triggered via the keyboard that we will
miss the "up" event and once KGDB lets the kernel go another SysRq will be
required to clear this, without this change.
drivers/char/keyboard.c | 1 +
1 file changed, 1 insertion(+)
Index: linux-2.6.14/drivers/char/keyboard.c
===================================================================
--- linux-2.6.14.orig/drivers/char/keyboard.c
+++ linux-2.6.14/drivers/char/keyboard.c
@@ -1069,6 +1069,7 @@ static void kbd_keycode(unsigned int key
}
if (sysrq_down && down && !rep) {
handle_sysrq(kbd_sysrq_xlate[keycode], regs, tty);
+ sysrq_down = 0; /* In case we miss the 'up' event. */
return;
}
#endif
--
Tom
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]