From: "Christopher Friesen" <cfriesen@nortel.com>
To: mgross <mgross@linux.intel.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
vherva@vianova.fi, bunk@stusta.de, folkert@vanheusden.com,
linux-kernel@vger.kernel.org
Subject: Re: capturing oopses
Date: Mon, 28 Nov 2005 10:42:14 -0600 [thread overview]
Message-ID: <438B3366.5070700@nortel.com> (raw)
In-Reply-To: <200511280820.02473.mgross@linux.intel.com>
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've worked on a few blades that had this. Serial console wasn't going
to be available in the field, so being able to just dump debug
information to persistent memory was really nice.
Chris
next prev parent reply other threads:[~2005-11-28 16:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 13:07 capturing oopses 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 [this message]
2005-11-28 19:35 ` Ville Herva
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=438B3366.5070700@nortel.com \
--to=cfriesen@nortel.com \
--cc=bunk@stusta.de \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=rdunlap@xenotime.net \
--cc=vherva@vianova.fi \
/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