Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932066AbVKJQp6 (ORCPT ); Thu, 10 Nov 2005 11:45:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932071AbVKJQp6 (ORCPT ); Thu, 10 Nov 2005 11:45:58 -0500 Received: from fed1rmmtao01.cox.net ([68.230.241.38]:13005 "EHLO fed1rmmtao01.cox.net") by vger.kernel.org with ESMTP id S932066AbVKJQpX (ORCPT ); Thu, 10 Nov 2005 11:45:23 -0500 From: Tom Rini To: Andrew Morton Cc: Tom Rini , lkml Message-Id: <20051110164515.20950.68313.sendpatchset@localhost.localdomain> In-Reply-To: <20051110163906.20950.45704.sendpatchset@localhost.localdomain> References: <20051110163906.20950.45704.sendpatchset@localhost.localdomain> Subject: [PATCH,RFC 2.6.14 14/15] KGDB: Fix for 'lost' SysRq events Date: Thu, 10 Nov 2005 11:45:00 -0500 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 954 Lines: 27 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/