From: Jason Wessel <jason.wessel@windriver.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 15/21] KGDB: Fix possibility of missing SysRq-G
Date: Mon, 15 Oct 2007 13:33:42 -0500 [thread overview]
Message-ID: <4713B286.7030100@windriver.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 57 bytes --]
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
[-- Attachment #2: sysrq_bugfix.patch --]
[-- Type: text/x-patch, Size: 951 bytes --]
sysrq_bugfix.patch
From: Jason Wessel <jason.wessel@windriver.com>
Subject: [PATCH] Fix possibility of missing SysRq-G
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.
Signed-off-by: Tom Rini <trini@kernel.crashing.org>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
---
drivers/char/keyboard.c | 1 +
1 file changed, 1 insertion(+)
Index: linux-2.6.21.1/drivers/char/keyboard.c
===================================================================
--- linux-2.6.21.1.orig/drivers/char/keyboard.c
+++ linux-2.6.21.1/drivers/char/keyboard.c
@@ -1176,6 +1176,7 @@ static void kbd_keycode(unsigned int key
sysrq_down = 0;
if (sysrq_down && down && !rep) {
handle_sysrq(kbd_sysrq_xlate[keycode], tty);
+ sysrq_down = 0; /* In case we miss the 'up' event. */
return;
}
#endif
reply other threads:[~2007-10-15 18:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4713B286.7030100@windriver.com \
--to=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.