Re: Oops assist...

Dan Hollis (goemon@sasami.anime.net)
Wed, 5 May 1999 11:11:49 -0700 (PDT)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Steve Dodd: "Re: Linux 2.2.7-ac1 Path MTU bug"
Previous message: Steve Dodd: "Re: Invalid inode->i_sb in clear_inode()? (was Re: Kernel Oops, 2.2.7)"
In reply to: Olaf Titz: "Re: Oops assist..."
Next in thread: Paul Jakma: "Re: Oops assist..."

On Wed, 5 May 1999, Olaf Titz wrote:
> > Even more ideal would be to dump the oops to somewhere non volatile over
> > a reboot. I'm not sure there are good candidates for this on a PC.
> SunOS thinks the swap disk is a good one (for making crash dumps of
> the whole system actually). If code in the boot scripts checks for a
> crash-dump signature on the primary swap disk _before_ swapon'ing it,
> this could be easily accessed (i.e. written elsewhere).

SGI preserves ram on a reboot, unlike some PC BIOS which scribbles all
over RAM on a reboot. So SGI can do a 100% safe crashdump by dumping after
the system has been reset. Anyone know a PC BIOS which doesnt mangle RAM?

-Dan

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

Next message: Steve Dodd: "Re: Linux 2.2.7-ac1 Path MTU bug"
Previous message: Steve Dodd: "Re: Invalid inode->i_sb in clear_inode()? (was Re: Kernel Oops, 2.2.7)"
In reply to: Olaf Titz: "Re: Oops assist..."
Next in thread: Paul Jakma: "Re: Oops assist..."