Re: Oops assist...

Michael B. Trausch (mtrausch@wcnet.org)
Thu, 6 May 1999 06:04:12 -0400 (EDT)

On Thu, 6 May 1999, Keith Owens wrote:
KO>
KO>Obvious downsides - requires a dedicated disk partion below cylinder
KO>1024, extra kernel code, a chunk of real code memory is dedicated to
KO>the dump code and (the big one) all Oops would result in a reboot.
KO>That last requirement is because the dump code has no way of telling if
KO>the kernel is usable after an Oops so we have to assume worst case.
KO>Obviously this entire procedure would be a compile time option or
KO>module, not everybody wants to reboot after every Oops.
KO>

OTOH, the kernel should be restarted... My Linux oops'd once when I put
buggy RAM in it, and it instantly rebooted. I found that, personally to
be a good thing, becuase that's the quickest and most reliable way to get
all the system services and the kernel back up and running.

----------------------------------------------------------------
Michael B. Trausch
President of Linux Operations, ADK Computers
----------------------------------------------------------------
ADK Computers, Walbridge Office Phone: 419.838.8104
5375 Keller Road Main Office: 419.882.7435
Walbridge, OH 43465 E-Mail: mtrausch@wcnet.org
----------------------------------------------------------------
Thursday, May 06, 1999
FLOPPY DISK: Serious curvature of the spine.

-
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/