From: Morten Helgesen <morten.helgesen@nextframe.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: writing OOPS/panic info to nvram?
Date: Wed, 4 Sep 2002 14:54:46 +0200 [thread overview]
Message-ID: <20020904145446.B117@sexything> (raw)
In-Reply-To: <1031143752.2788.118.camel@irongate.swansea.linux.org.uk>
On Wed, Sep 04, 2002 at 01:49:12PM +0100, Alan Cox wrote:
> On Wed, 2002-09-04 at 13:31, Morten Helgesen wrote:
> > True - the 'normal' size on a PC is apparently something like 114 bytes ...
> > I guess we could use it for something useful ... but maybe not for
> > OOPSen/panics.
> >
> > I didn`t realize we only had 114 bytes to work with.
>
> We don't. They are all used by the BIOS
That makes it even less useful. Oh well.
== Morten
--
"Livet er ikke for nybegynnere" - sitat fra en klok person.
mvh
Morten Helgesen
UNIX System Administrator & C Developer
Nextframe AS
admin@nextframe.net / 93445641
http://www.nextframe.net
next prev parent reply other threads:[~2002-09-04 12:49 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 [this message]
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
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=20020904145446.B117@sexything \
--to=morten.helgesen@nextframe.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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