[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1275464359-1566-1-git-send-email-v.mayatskih@gmail.com>
Date: Wed, 2 Jun 2010 09:39:14 +0200
From: Vitaly Mayatskikh <v.mayatskih@...il.com>
To: linux-kernel@...r.kernel.org
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Vivek Goyal <vgoyal@...hat.com>,
Randy Dunlap <rdunlap@...otime.net>
Subject: [PATCH 0/5] kdump: extract log buffer and registers from vmcore on NMI button pressing
Sometimes non-interactive dump capture environment silently fails to
store vmcore due to hardware or software bug. It is hard then to
understand and fix reasons of system failure in both production and
dump capture environments to prevent this failure to reoccur. It would
be quite usefull to see log buffer contents of crashed kernel at
least.
This patchset adds possibility for dump capture mode to extract and
print log buffer and CPU registers from captured vmcore. Also the
state of running kernel is printed. This action can be triggered via
NMI button.
Signed-off-by: Vitaly Mayatskikh <v.mayatskih@...il.com>
arch/x86/include/asm/elf.h | 46 +++++
arch/x86/include/asm/kdebug.h | 1 +
arch/x86/include/asm/nmi.h | 1 +
arch/x86/kernel/apic/nmi.c | 27 +++
arch/x86/kernel/process_32.c | 22 ++-
arch/x86/kernel/process_64.c | 20 ++-
fs/proc/vmcore.c | 365 +++++++++++++++++++++++++++++++++++++++--
include/linux/sysctl.h | 1 +
kernel/sysctl.c | 7 +
kernel/sysctl_binary.c | 1 +
10 files changed, 463 insertions(+), 28 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists