From: Ville Herva <vherva@vianova.fi>
To: mgross <mgross@linux.intel.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
bunk@stusta.de, folkert@vanheusden.com,
linux-kernel@vger.kernel.org
Subject: Re: capturing oopses
Date: Mon, 28 Nov 2005 21:35:51 +0200 [thread overview]
Message-ID: <20051128193551.GG6966@vianova.fi> (raw)
In-Reply-To: <200511280820.02473.mgross@linux.intel.com>
On Mon, Nov 28, 2005 at 08:20:02AM -0800, you [mgross] wrote:
>
> You know some platforms that perserve the memory above some addresses across
> warm boots. For such platforms, one could reserve a buffer in that area can
> copy the sys log buffer to it on panic along with a bit pattern that could be
> searched for upon the next boot.
I think there was a patch to do this a couple of years ago.
The only references I can find now are:
http://groups.google.com/groups?q=%22Utility+module+to+capture+OOPS+output+over+reboot%22&hl=en&selm=fa.fbd0l7v.14hau3n%40ifi.uio.no&rnum=1)
http://marc.theaimsgroup.com/?l=linux-kernel&m=93077831203565&w=2
-- v --
v@iki.fi
next prev parent reply other threads:[~2005-11-28 19:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 13:07 Folkert van Heusden
2005-11-22 14:08 ` bert hubert
2005-11-23 1:27 ` Brice Goglin
2005-11-23 10:55 ` Folkert van Heusden
2005-11-23 11:17 ` bert hubert
2005-11-26 15:56 ` Adrian Bunk
2005-11-26 19:33 ` Ville Herva
2005-11-28 4:41 ` Randy.Dunlap
2005-11-28 16:20 ` mgross
2005-11-28 16:42 ` Christopher Friesen
2005-11-28 19:35 ` Ville Herva [this message]
2005-11-28 5:11 ` Maneesh Soni
[not found] <5bG4q-8ks-17@gated-at.bofh.it>
[not found] ` <5daDm-1Cg-15@gated-at.bofh.it>
[not found] ` <5de3Z-6CJ-13@gated-at.bofh.it>
2005-11-27 1:10 ` Bodo Eggert
2005-11-27 12:16 ` Ville Herva
2005-11-27 13:55 ` Sander
2005-11-27 14:44 ` Ville Herva
2005-11-27 14:56 ` Ville Herva
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=20051128193551.GG6966@vianova.fi \
--to=vherva@vianova.fi \
--cc=bunk@stusta.de \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=rdunlap@xenotime.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®