CC: George Anzginer <[email protected]>
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.
---
linux-2.6.13-trini/drivers/char/keyboard.c | 1 +
1 files changed, 1 insertion(+)
diff -puN drivers/char/keyboard.c~sysrq_bugfix drivers/char/keyboard.c
--- linux-2.6.13/drivers/char/keyboard.c~sysrq_bugfix 2005-08-08
19:16:04.000000000 -0700
+++ linux-2.6.13-trini/drivers/char/keyboard.c 2005-08-08 19:16:04.000000000
-0700
@@ -1070,6 +1070,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
_
-
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/
