mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Seiji Aguchi <seiji.aguchi@hds.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
	Andrew Morton <akpm@linux-foundation.org>,
	"Artem.Bityutskiy@nokia.com" <Artem.Bityutskiy@nokia.com>,
	"simon.kagstrom@netinsight.net" <simon.kagstrom@netinsight.net>,
	"David.Woodhouse@intel.com" <David.Woodhouse@intel.com>,
	"anders.grafstrom@netinsight.net"
	<anders.grafstrom@netinsight.net>,
	"jason.wessel@windriver.com" <jason.wessel@windriver.com>,
	"jslaby@suse.cz" <jslaby@suse.cz>,
	"jmorris@namei.org" <jmorris@namei.org>,
	"eparis@redhat.com" <eparis@redhat.com>,
	"hch@lst.de" <hch@lst.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kyungmin.park@samsung.com" <kyungmin.park@samsung.com>,
	"marco.stornelli@gmail.com" <marco.stornelli@gmail.com>,
	"namhyung@gmail.com" <namhyung@gmail.com>,
	Aaron Durbin <adurbin@google.com>,
	"randy.dunlap@oracle.com" <randy.dunlap@oracle.com>,
	"dle-develop@lists.sourceforge.net" 
	<dle-develop@lists.sourceforge.net>,
	Satoru Moriya <satoru.moriya@hds.com>
Subject: Re: [PATCH 2/2] kmsg_dump: adding to reboot, halt, poweroff and emergency_restart path
Date: Tue, 23 Nov 2010 17:58:04 +0900 (JST)	[thread overview]
Message-ID: <20101123175450.7BCE.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <5C4C569E8A4B9B42A84A977CF070A35B2C12D6E2FE@USINDEVS01.corp.hds.com>

>  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 <seiji.aguchi@hds.com>

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" <tony.luck@intel.com>
Subject: [RFC] persistent store




  parent reply	other threads:[~2010-11-23  8:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 14:58 [PATCH 0/2] " Seiji Aguchi
2010-11-17 15:00 ` [PATCH 1/2] " Seiji Aguchi
2010-11-17 15:03   ` [PATCH 2/2] " Seiji Aguchi
2010-11-18  8:17     ` Artem Bityutskiy
2010-11-23  8:58     ` KOSAKI Motohiro [this message]
2010-11-18  8:16   ` [PATCH 1/2] " Artem Bityutskiy
2010-11-23  8:54   ` KOSAKI Motohiro
2010-11-17 20:45 ` [PATCH 0/2] " Andrew Morton

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=20101123175450.7BCE.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=David.Woodhouse@intel.com \
    --cc=adurbin@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=anders.grafstrom@netinsight.net \
    --cc=dle-develop@lists.sourceforge.net \
    --cc=eparis@redhat.com \
    --cc=hch@lst.de \
    --cc=jason.wessel@windriver.com \
    --cc=jmorris@namei.org \
    --cc=jslaby@suse.cz \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.stornelli@gmail.com \
    --cc=namhyung@gmail.com \
    --cc=randy.dunlap@oracle.com \
    --cc=satoru.moriya@hds.com \
    --cc=seiji.aguchi@hds.com \
    --cc=simon.kagstrom@netinsight.net \
    /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

all inboxes | Powered by JetHome®