Messages in this thread | | | Date | Mon, 25 Oct 1999 17:23:52 +0200 (CEST) | From | willy tarreau <> | Subject | Re: kmsgdump 0.4.1 released (bugfix) |
| |
> It may simply have bounced back out of the BIOS > with a trail of corrupted memory
well, I can't see how it may have bounced back out of the bios, since the bios is only entered with a cpu reset. Most of the CPU's context is lost by the reset, including IDT and GDT, and I don't imagine the kernel being able to display an "oops" on the console under these conditions.
What is possible however, is that the reset doesn't work and causes the oops. And perhaps in this case it may overlap memory.
Willy
___________________________________________________________ Do You Yahoo!? Votre e-mail @yahoo.fr gratuit sur http://courrier.yahoo.fr
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |