public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Tom Rini <trini@kernel.crashing.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH,RFC 2.6.14 14/15] KGDB: Fix for 'lost' SysRq events
Date: Thu, 10 Nov 2005 11:45:00 -0500	[thread overview]
Message-ID: <20051110164515.20950.68313.sendpatchset@localhost.localdomain> (raw)
In-Reply-To: <20051110163906.20950.45704.sendpatchset@localhost.localdomain>

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

  parent reply	other threads:[~2005-11-10 16:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 16:38 [PATCH,RFC 2.6.14 00/15] KGDB Support Tom Rini
2005-11-10 16:39 ` [PATCH,RFC 2.6.14 01/15] KGDB: core infrastructure Tom Rini
2005-11-10 16:39 ` [PATCH,RFC 2.6.14 03/15] KGDB: ppc32-specific changes Tom Rini
2005-11-10 16:39 ` [PATCH,RFC 2.6.14 02/15] KGDB: i386-specific changes Tom Rini
2005-11-10 16:40 ` [PATCH,RFC 2.6.14 04/15] KGDB: 8250-like UART driver Tom Rini
2005-11-10 16:41 ` [PATCH,RFC 2.6.14 06/15] KGDB: IA64-specific changes Tom Rini
2005-11-10 16:41 ` [PATCH,RFC 2.6.14 05/15] KGDB: MIPS-specific changes Tom Rini
2005-11-10 16:41 ` [PATCH,RFC 2.6.14 08/15] KGDB: x86_64-specific changes Tom Rini
2005-11-10 16:41 ` [PATCH,RFC 2.6.14 07/15] x86_64: Add a notifier hook to the "no context" part of do_page_fault Tom Rini
2005-11-10 16:42 ` [PATCH,RFC 2.6.14 09/15] KGDB: SuperH-specific changes Tom Rini
2005-11-10 16:42 ` [PATCH,RFC 2.6.14 10/15] KGDB: ARM-specific changes Tom Rini
2005-11-10 16:43 ` [PATCH,RFC 2.6.14 11/15] KGDB: ppc64-specific changes Tom Rini
2005-11-11  0:55   ` Paul Mackerras
2005-11-11  1:13     ` Tom Rini
2005-11-10 16:44 ` [PATCH,RFC 2.6.14 13/15] KGDB: CFI annotations for better unwinding Tom Rini
2005-11-10 16:44 ` [PATCH,RFC 2.6.14 12/15] KGDB: netpoll-based ethernet driver Tom Rini
2005-11-10 16:45 ` Tom Rini [this message]
2005-11-10 16:45 ` [PATCH,RFC 2.6.14 15/15] KGDB: Better support for loaded modules Tom Rini

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=20051110164515.20950.68313.sendpatchset@localhost.localdomain \
    --to=trini@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox