From: Pavel Machek <pavel@suse.cz>
To: Remco Post <r.post@sara.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: writing OOPS/panic info to nvram?
Date: Fri, 13 Sep 2002 19:03:48 +0200 [thread overview]
Message-ID: <20020913170347.GA7096@elf.ucw.cz> (raw)
In-Reply-To: <4DE1BD2E-C4CD-11D6-9C2C-000393911DE2@sara.nl>
Hi!
> >>driver oopses... Maybe do something like:
> >>
> >>if there is enough space on disk && ..., use that else
> >>if there is a swap over nfs && ..., use that else
> >>if there is a tape drive attaced and a tape is present and it is
> >>writeable... else
> >>if there is nvram available use that
> >
> >You just killed any data you had on the tape... too bad.
> > Pavel
>
> Yes, so, or you just saved that oops that has been bugging you for
> months... (And yes I'm probably one of those rare people that has
> tapedrives attached that are not used for anything usefull).
If it was bugging you for months, then you'd have probably copied it
using paper and pencil already. cli(); while(1); at the end of oops
handler is not *that* hard to do.
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
next prev parent reply other threads:[~2002-09-13 18:35 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 [this message]
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
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=20020913170347.GA7096@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--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 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.