From: "Jeremy Jackson" <jerj@coplanar.net>
To: "Suparna Bhattacharya" <suparna@in.ibm.com>
Cc: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
<linux-kernel@vger.kernel.org>,
<lkcd-devel@lists.sourceforge.net>
Subject: Re: Faster reboots (and a better way of taking crashdumps?)
Date: Wed, 10 Apr 2002 20:47:17 -0700 [thread overview]
Message-ID: <007b01c1e10b$93b27300$7e0aa8c0@bridge> (raw)
In-Reply-To: <00c501c1dce3$0ed806d0$7e0aa8c0@bridge> <1674141067.1018028922@[10.10.2.3]> <003301c1dd16$855df1b0$7e0aa8c0@bridge> <3CB144BE.9DC8B034@in.ibm.com>
Should this go off lkml?
----- Original Message -----
From: "Suparna Bhattacharya" <suparna@in.ibm.com>
Sent: Monday, April 08, 2002 12:20 AM
> > I'm currently researching combining the two, to create a LinuxBIOS
> > firmware debug console, which will allow complete crash dump to
> > be taken after a hardware reset, with the smallest possible Heisenburg
> > effect, aside from a hardware debugger.
>
> So how is the actual writeout accomplished ?(via LinuxBIOS ?)
well it's just an idea just now. In order to do this from code in rom,
I immagine it would just dump physical memory to a raw partition,
using polling ide drivers in LinuxBIOS. This is probably a step
backwards, compared to modern crash dumps, but it would
allow zero alteration of memory.
It may be possible to do with a standard flash size of 128KiB,
though, which would allow virtually all motherboards to support it.
Jeremy
next prev parent reply other threads:[~2002-04-11 3:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 19:13 Faster reboots (and a better way of taking crashdumps?) Martin J. Bligh
2002-04-05 20:47 ` Jeremy Jackson
2002-04-06 1:48 ` Martin J. Bligh
2002-04-06 2:55 ` Jeremy Jackson
2002-04-06 17:04 ` Faster reboots - calling _start? Byron Stanoszek
2002-04-06 20:00 ` Eric W. Biederman
2002-04-06 21:37 ` Martin J. Bligh
2002-04-06 21:57 ` Eric W. Biederman
2002-04-08 7:20 ` Faster reboots (and a better way of taking crashdumps?) Suparna Bhattacharya
2002-04-11 3:47 ` Jeremy Jackson [this message]
2002-04-11 14:28 ` Suparna Bhattacharya
2002-04-06 17:56 ` Alan Cox
2002-04-07 1:35 ` Martin J. Bligh
2002-04-06 23:27 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2002-04-07 1:32 Martin J. Bligh
2002-04-07 2:50 ` Eric W. Biederman
2002-04-07 4:00 ` Martin J. Bligh
2002-04-07 4:12 ` Eric W. Biederman
2002-04-08 14:31 ` Suparna Bhattacharya
2002-04-08 17:09 ` Eric W. Biederman
2002-04-09 15:26 ` Suparna Bhattacharya
2002-04-10 15:40 ` Eric W. Biederman
2002-04-10 17:58 ` Andy Pfiffer
2002-04-11 14:15 ` Suparna Bhattacharya
2002-04-11 15:08 ` Eric W. Biederman
2002-04-16 10:02 ` Pavel Machek
2002-04-16 22:59 ` Alan Cox
2002-04-11 13:56 ` Suparna Bhattacharya
2002-04-11 15:35 ` Eric W. Biederman
2002-04-12 14:49 ` Suparna Bhattacharya
2002-04-12 17:59 ` Eric W. Biederman
2002-04-15 10:07 ` Suparna Bhattacharya
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='007b01c1e10b$93b27300$7e0aa8c0@bridge' \
--to=jerj@coplanar.net \
--cc=Martin.Bligh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcd-devel@lists.sourceforge.net \
--cc=suparna@in.ibm.com \
/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