From: "Randy MacLeod" <rwmacleod@gmail.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linux-embedded@vger.kernel.org
Subject: Re: kernel dump solutions
Date: Thu, 21 Aug 2008 21:53:32 -0400 [thread overview]
Message-ID: <21f828e90808211853r6e92f6b9ta4bf9252ed63eccd@mail.gmail.com> (raw)
In-Reply-To: <1218656903.10489.50.camel@localhost.localdomain>
On Wed, Aug 13, 2008 at 3:48 PM, Josh Boyer <jwboyer@gmail.com> wrote:
> Hi All,
>
> I'm curious what people are using for a kernel dump solution on embedded
Create a region of memory that pesist across resets.
Put kernel panic info, exceptiions and scheduling events into said memory.
Profit!
If only more manufactures would support this in the bios...
Intel and BIOS writter folks are you listening?
--
// Randy
next prev parent reply other threads:[~2008-08-22 1:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 19:48 kernel dump solutions Josh Boyer
2008-08-14 5:44 ` Flatten device tree & PPC linux Fundu
2008-08-14 6:43 ` Flatten device tree & PPC linu Grant Likely
2008-08-14 17:27 ` David VomLehn
2008-08-22 1:53 ` Randy MacLeod [this message]
2008-08-22 2:54 ` kernel dump solutions Josh Boyer
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=21f828e90808211853r6e92f6b9ta4bf9252ed63eccd@mail.gmail.com \
--to=rwmacleod@gmail.com \
--cc=jwboyer@gmail.com \
--cc=linux-embedded@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).