From: Pavel Machek <pavel@suse.cz>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: "J.A. Magallon" <jamagallon@able.es>, linux-kernel@vger.kernel.org
Subject: Re: writing OOPS/panic info to nvram?
Date: Fri, 6 Sep 2002 10:09:33 +0000 [thread overview]
Message-ID: <20020906100933.E35@toy.ucw.cz> (raw)
In-Reply-To: <20020904144938.GA1106@marowsky-bree.de>; from lmb@suse.de on Wed, Sep 04, 2002 at 04:49:38PM +0200
Hi!
> > Ah, ther is no way to write raw blocks at a very low level to disk...??
>
> Not reliably; you _know_ your infrastructure has crashed, otherwise you
> wouldn't be inside the crash dump handler ;), so you can't possibly trust the
> normal block layer to write the crash dump (and not write it over your salary
> and customer database).
Floppy seems like safe choice. Verify its special "crash floppy" by checking
signature, then write.
> A network dump is much safer, though I would suggest running it over a
> dedicated card / driver combo and on a special ethernet protocol, because you
> might have lost your IP configuration...
Its enough for it to work 99% cases. Separate ethernet card is overkill,
serial console is easier than that.
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2002-09-06 20:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 11:50 writing OOPS/panic info to nvram? 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 [this message]
2002-09-04 23:34 ` Paul Mackerras
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
-- strict thread matches above, loose matches on Subject: below --
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=20020906100933.E35@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.