From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: for.poige+linux@gmail.com, Willy Tarreau <w@1wt.eu>,
linux-kernel@vger.kernel.org
Subject: Re: > I even didn't have a backtrace.
Date: Mon, 29 Dec 2008 14:07:28 +0000 [thread overview]
Message-ID: <20081229140728.GB31266@srcf.ucam.org> (raw)
In-Reply-To: <4958C9CD.5050003@yahoo.com>
On Mon, Dec 29, 2008 at 12:59:57PM +0000, Sitsofe Wheeler wrote:
> Igor Podlesny wrote:
> > Similar, but no exactly. I just thought that unlikely BIOS erases
> >memory content during "fast checks", so kernel diagnostic could be
>
> My understanding is that the only part of the BIOS that doesn't get
> cleared over a reboot (the hardware clock) is already being abused for
> suspend tracing -
> http://mjmwired.net/kernel/Documentation/power/s2ram.txt .
That's the only part of the system that's guaranteed to persist over a
power cycle. You probably have a little more flexibility with a warm
reboot.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-12-29 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.q3E31Fk9IOYkDJ38/mQp9Iyp2TI@ifi.uio.no>
[not found] ` <fa.qMGHzuTz1nuoHKywmH/aLmriclo@ifi.uio.no>
[not found] ` <fa.LbTTdeLVGfaCxioVgNMO13Libio@ifi.uio.no>
2008-12-29 12:59 ` Sitsofe Wheeler
2008-12-29 14:07 ` Matthew Garrett [this message]
[not found] <bOpT3-2LN-13@gated-at.bofh.it>
[not found] ` <bOpT3-2LN-15@gated-at.bofh.it>
[not found] ` <bOpT3-2LN-11@gated-at.bofh.it>
2008-12-29 19:24 ` Bodo Eggert
2008-12-29 23:33 ` Alan Cox
[not found] <fa.49EGxNgCILq/XfuGCazHZV8OJlg@ifi.uio.no>
[not found] ` <4958C2CE.7060206@yahoo.com>
2008-12-29 12:52 ` Igor Podlesny
2008-12-29 7:03 Igor Podlesny
2008-12-30 2:17 ` Daniel Barkalow
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=20081229140728.GB31266@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=for.poige+linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sitsofe@yahoo.com \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®