From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755194Ab1KUPRo (ORCPT ); Mon, 21 Nov 2011 10:17:44 -0500 Received: from mx1.redhat.com ([209.132.183.28]:49624 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751624Ab1KUPRn (ORCPT ); Mon, 21 Nov 2011 10:17:43 -0500 Date: Mon, 21 Nov 2011 10:17:27 -0500 From: Vivek Goyal To: "K.Prasad" Cc: linux-kernel@vger.kernel.org, Borislav Petkov , "Luck, Tony" , "Eric W. Biederman" , anderson@redhat.com, tachibana@mxm.nes.nec.co.jp, oomichi@mxs.nes.nec.co.jp, Valdis.Kletnieks@vt.edu, Nick Bowler Subject: Re: [RFC Patch 0/2] Slimdump framework using CRASH_REASON - v2 Message-ID: <20111121151727.GF313@redhat.com> References: <20111121095405.GA2289@in.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111121095405.GA2289@in.ibm.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 21, 2011 at 03:24:05PM +0530, K.Prasad wrote: > Hi All, > In furtherance of the previous discussion regarding 'slimdump' > (refer: http://article.gmane.org/gmane.linux.kernel/1204967), it was > decided that, > > - An entry in VMCOREINFO elf-note be added to denote the cause of crash, > instead of creating a new elf-note. > > - Upstream tools such as 'makedumpfile' and 'crash' be modified to > recognise this string and inform the user accordingly. > > Accordingly, this new version of the patchset makes the following > changes > > Changelog - version 2 > ----------------------- > (First version posted here: > http://article.gmane.org/gmane.linux.kernel/1198435) > > - Append VMCOREINFO elf-note with a new variable CRASH_REASON whose > value will be populated using arch_add_crash_reason() function. > > - Define arch_add_crash_reason() in the x86 MCE path to return "PANIC_MCE" > in the panic path of MCE. > > - 'makedumpfile' tool is taught to recognise PANIC_MCE string as one > value of CRASH_REASON for which 'slimdump' must be captured. So again, what is slimdump? I mean, what information is now being captured in the case of slimdump? Are you capturing atleast the kernel message buffers? I am assuming that any register info emitted on console will make into kernel buffers and that should be useful to figure out what MCE happened. Thanks Vivek