mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@au1.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "J.A. Magallon" <jamagallon@able.es>, Remco Post <r.post@sara.nl>,
	morten.helgesen@nextframe.net, linux-kernel@vger.kernel.org
Subject: Re: writing OOPS/panic info to nvram?
Date: Thu, 5 Sep 2002 09:34:52 +1000 (EST)	[thread overview]
Message-ID: <15734.39068.766611.169333@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <1031149539.2788.120.camel@irongate.swansea.linux.org.uk>

Alan Cox writes:

> With what will you write it - not the linux block layer thats for sure.
> Ingo has patches for doing network dumps which are kind of neat

Rusty has written a very basic polled-mode IDE driver for precisely
this situation.  He even tested it on x86 and powermac. :)  He has a
little user-space program that allocates a file and uses FIOBMAP to
work out which disk blocks it is using.  The program writes a
signature to the blocks and then tells the kernel crashdump module the
block numbers.  When the kernel panics, it calls the crashdump module
which first reads the blocks it was told and makes sure they have the
right signature, then writes the oops information to those blocks and
then reboots.

IDE was relatively straightforward since you can do basic block I/O
with just the ATA-1 or ATA-2 registers and command set and PIO.  In
contrast, I believe SCSI defeated him. :)

Paul.

  parent reply	other threads:[~2002-09-04 23:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-04 11:50 Roy Sigurd Karlsbakk
2002-09-04 12:02 ` Morten Helgesen
2002-09-04 12:21 ` Alan Cox
2002-09-04 12:31   ` Morten Helgesen
2002-09-04 12:49     ` Alan Cox
2002-09-04 12:54       ` Morten Helgesen
2002-09-04 14:02         ` Remco Post
2002-09-04 14:08           ` J.A. Magallon
2002-09-04 14:23             ` Remco Post
2002-09-06 10:06               ` Pavel Machek
2002-09-10 14:55                 ` Remco Post
2002-09-13 17:03                   ` Pavel Machek
2002-09-04 14:25             ` Alan Cox
2002-09-04 14:41               ` J.A. Magallon
2002-09-04 14:49                 ` Lars Marowsky-Bree
2002-09-06 10:09                   ` Pavel Machek
2002-09-04 23:34               ` Paul Mackerras [this message]
2002-09-04 23:48                 ` David S. Miller
2002-09-05  0:07                 ` Alan Cox
2002-09-06  6:48                   ` Rusty Russell
2002-09-05 10:38               ` Suparna Bhattacharya
2005-01-24 15:18 Christoph Stueckjuergen

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=15734.39068.766611.169333@argo.ozlabs.ibm.com \
    --to=paulus@au1.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morten.helgesen@nextframe.net \
    --cc=r.post@sara.nl \
    /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®