linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@gmail.com>
To: linux-embedded@vger.kernel.org
Subject: kernel dump solutions
Date: Wed, 13 Aug 2008 15:48:23 -0400	[thread overview]
Message-ID: <1218656903.10489.50.camel@localhost.localdomain> (raw)

Hi All,

I'm curious what people are using for a kernel dump solution on embedded
platforms.  It seems that kexec/kdump is the default solution for
desktop and server machines, but this seems to be a bit heavy for
embedded platforms.  Requiring a second kernel to do the dump seems like
a cost that most platform designers wouldn't be willing to incur.

The only other alternative that I'm aware of is LKCD.  It doesn't seem
particularly active at all these days.  Mcore has been sufficiently dead
for years.  So what's left?  What else are people using?

josh

             reply	other threads:[~2008-08-13 19:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 19:48 Josh Boyer [this message]
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 ` kernel dump solutions Randy MacLeod
2008-08-22  2:54   ` 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=1218656903.10489.50.camel@localhost.localdomain \
    --to=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).