Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751576Ab0KWI6M (ORCPT ); Tue, 23 Nov 2010 03:58:12 -0500 Received: from fgwmail7.fujitsu.co.jp ([192.51.44.37]:37931 "EHLO fgwmail7.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751008Ab0KWI6K (ORCPT ); Tue, 23 Nov 2010 03:58:10 -0500 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 From: KOSAKI Motohiro To: Seiji Aguchi Subject: Re: [PATCH 2/2] kmsg_dump: adding to reboot, halt, poweroff and emergency_restart path Cc: kosaki.motohiro@jp.fujitsu.com, Andrew Morton , "Artem.Bityutskiy@nokia.com" , "simon.kagstrom@netinsight.net" , "David.Woodhouse@intel.com" , "anders.grafstrom@netinsight.net" , "jason.wessel@windriver.com" , "jslaby@suse.cz" , "jmorris@namei.org" , "eparis@redhat.com" , "hch@lst.de" , "linux-kernel@vger.kernel.org" , "kyungmin.park@samsung.com" , "marco.stornelli@gmail.com" , "namhyung@gmail.com" , Aaron Durbin , "randy.dunlap@oracle.com" , "dle-develop@lists.sourceforge.net" , Satoru Moriya In-Reply-To: <5C4C569E8A4B9B42A84A977CF070A35B2C12D6E2FE@USINDEVS01.corp.hds.com> References: <5C4C569E8A4B9B42A84A977CF070A35B2C12D6E2FA@USINDEVS01.corp.hds.com> <5C4C569E8A4B9B42A84A977CF070A35B2C12D6E2FE@USINDEVS01.corp.hds.com> Message-Id: <20101123175450.7BCE.A69D9226@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Mailer: Becky! ver. 2.50.07 [ja] Date: Tue, 23 Nov 2010 17:58:04 +0900 (JST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 972 Lines: 26 > We need to know the reason why system rebooted in support service. > However, we can't inform our customers of the reason because > final messages are lost on current Linux kernel. > > This patch improves the situation above because the final messages > are saved by adding kmsg_dump() to reboot, halt, poweroff and > emergency_restart path. > > Signed-off-by: Seiji Aguchi This patch doesn't have any notification consumer. It's too bad. As far as I know, some poeple are now discussing to make generic firmware access interface. perhaps your one can be integrate it. Please see and join following discussion. From: "Luck, Tony" Subject: [RFC] persistent store -- 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/