The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: James Colannino <lkml@colannino.org>
To: linux-kernel@vger.kernel.org
Subject: Re: how to capture kernel panics
Date: Thu, 24 Feb 2005 19:08:31 -0800	[thread overview]
Message-ID: <421E96AF.1070908@colannino.org> (raw)
In-Reply-To: <52765.69.93.110.242.1109288148.squirrel@69.93.110.242>

shabanip wrote:

>is there any way to capture and log kernel panics on disk or ...?
>  
>

My guess would be, at the very least, it depends on what part of the 
kernel is causing the panic.  Most likely I would say no, although 
here's another question: if running a second kernel under user-mode 
Linux, can this be done?

James

  reply	other threads:[~2005-02-25  3:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24 23:35 how to capture kernel panics shabanip
2005-02-25  3:08 ` James Colannino [this message]
2005-02-25 13:26   ` Trond Hasle Amundsen
2005-02-25 14:17 ` Christian Borntraeger
2005-02-25 14:42   ` Jeff Moyer
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=421E96AF.1070908@colannino.org \
    --to=lkml@colannino.org \
    --cc=linux-kernel@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