> I even didn't have a backtrace.
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Igor Podlesny
2008/12/29 Sitsofe Wheeler <[email protected]>:
Quoted 6 lines
Quoted 3 lines · Igor Podlesny
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?
Quoted 8 lines
Quoted 1 line
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"
HTH.
One place to hide stuff is the upper areas of video ram as a lot of videocards don't clear the ram on a crash/reboot. I used to use a 3Dfx 32Mb card as a buffer with good effect.
Alan