From: Morten Helgesen <morten.helgesen@nextframe.net>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: writing OOPS/panic info to nvram?
Date: Wed, 4 Sep 2002 14:02:41 +0200 [thread overview]
Message-ID: <20020904140241.A123@sexything> (raw)
In-Reply-To: <200209041350.21358.roy@karlsbakk.net>
Hey, Roy
On Wed, Sep 04, 2002 at 01:50:21PM +0200, Roy Sigurd Karlsbakk wrote:
> hi
>
> I just read in the OS X.2 technote
So did I :)
> (http://developer.apple.com/technotes/tn2002/tn2053.html#TN001016) that
> they're writing the panic dump to nvram.
>
> Is it hard to implement this on Linux?
Doesn`t look like too much work. As far as I can see, from a quick
glance, we have everything we need at hand - just have to write a snippet
of code in traps.c. I`ll give it a whirl now.
>
> roy
> --
> Roy Sigurd Karlsbakk, Datavaktmester
> ProntoTV AS - http://www.pronto.tv/
> Tel: +47 9801 3356
>
== 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 11:56 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 [this message]
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
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=20020904140241.A123@sexything \
--to=morten.helgesen@nextframe.net \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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.