lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1LHNit-0001cP-EQ@be1.7eggert.dyndns.org>
Date:	Mon, 29 Dec 2008 20:24:18 +0100
From:	Bodo Eggert <7eggert@....de>
To:	for.poige+linux@...il.com, Sitsofe Wheeler <sitsofe@...oo.com>,
	Willy Tarreau <w@....eu>, linux-kernel@...r.kernel.org
Subject: Re: > I even didn't have a backtrace.

Igor Podlesny <for.poige+linux@...il.com> wrote:
> 2008/12/29 Sitsofe Wheeler <sitsofe@...oo.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.

You may want to read "ISA System Architecture
 By Tom Shanley, Don Anderson, John Swindle, MindShare, Inc"

http://books.google.com/books?id=iXE6mwUCNWQC&pg=PA110&lpg=PA112&ots=ZH_c88LEqd&dq=post+reset+flag+0072+0040&ie=ISO-8859-1&output=htmlhttp://books.google.com/books?id=iXE6mwUCNWQC&pg=PA112&lpg=PA112&dq=post+reset+flag+0072+0040&source=web&ots=ZH_c88LEqd&sig=3EbSpcxbKrPvd1ixhysJK4AuOrA&hl=en&sa=X&oi=book_result&resnum=1&ct=result

HTH.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ