mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Christian Borntraeger <linux-kernel@borntraeger.net>
Cc: linux-kernel@vger.kernel.org, "shabanip" <shabanip@avapajoohesh.com>
Subject: Re: how to capture kernel panics
Date: Fri, 25 Feb 2005 09:42:49 -0500	[thread overview]
Message-ID: <16927.14697.76256.482062@segfault.boston.redhat.com> (raw)
In-Reply-To: <200502251517.56254.linux-kernel@borntraeger.net>

==> Regarding Re: how to capture kernel panics; Christian Borntraeger <linux-kernel@borntraeger.net> adds:

linux-kernel> shabanip wrote:
>> is there any way to capture and log kernel panics on disk or ...?

linux-kernel> In former times, the Linux kernel tried to sync in the panic
linux-kernel> function. (If the panic did not happen in interrupt context)
linux-kernel> Unfortunately this had severe side effects in cases where the
linux-kernel> panic was triggered by file system block device code or any
linux-kernel> other part which is necessary for syncing. In most cases the
linux-kernel> call trace never made it onto disk anyway. So currently the
linux-kernel> kernel does not support saving a panic.

linux-kernel> Apart from using a serial console, you might have a look at
linux-kernel> several kexec/kdump/lkcd tools where people are working on
linux-kernel> being able to dump the memory of a paniced kernel.

Or netconsole, which will dump printk's do the server:port of your
choosing.

-Jeff

  reply	other threads:[~2005-02-25 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24 23:35 shabanip
2005-02-25  3:08 ` James Colannino
2005-02-25 13:26   ` Trond Hasle Amundsen
2005-02-25 14:17 ` Christian Borntraeger
2005-02-25 14:42   ` Jeff Moyer [this message]
2005-02-25 15:07     ` shabanip
2005-02-25 15:28       ` Jeff Moyer
2005-02-25 15:51         ` shabanip
2005-02-25 15:48           ` Jeff Moyer

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=16927.14697.76256.482062@segfault.boston.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=linux-kernel@borntraeger.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shabanip@avapajoohesh.com \
    /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®