From: "Igor Podlesny" <for.poige+linux@gmail.com>
To: "Sitsofe Wheeler" <sitsofe@yahoo.com>
Cc: "Willy Tarreau" <w@1wt.eu>, linux-kernel@vger.kernel.org
Subject: Re: > I even didn't have a backtrace.
Date: Mon, 29 Dec 2008 19:52:30 +0700 [thread overview]
Message-ID: <43d009740812290452l7a90de01nea3dad14cba58d85@mail.gmail.com> (raw)
In-Reply-To: <4958C2CE.7060206@yahoo.com>
2008/12/29 Sitsofe Wheeler <sitsofe@yahoo.com>:
> Igor Podlesny wrote:
>>
>> BTW, I wonder -- can the kernel store crash related information (if
>> any) in RAM, at certain addresses, so it can survive warm reboot and
>> get displayed "in dmesg" on the next boot?
>
> Perhaps you are thinking of kdump - http://lwn.net/Articles/108595/ ?
Similar, but no exactly. I just thought that unlikely BIOS erases
memory content during "fast checks", so kernel diagnostic could be
left at certain addresses, probably duplicated for safety, and newly
booted kernel could check if there were something left for it in RAM.
That's simpler than kdump/kexec, the question is only whether memory
is really left intact during BIOS work, at least partly.
--
End of message. Next message?
next parent reply other threads:[~2008-12-29 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.49EGxNgCILq/XfuGCazHZV8OJlg@ifi.uio.no>
[not found] ` <4958C2CE.7060206@yahoo.com>
2008-12-29 12:52 ` Igor Podlesny [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.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
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=43d009740812290452l7a90de01nea3dad14cba58d85@mail.gmail.com \
--to=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®