Date: 07 Feb 2002 21:10:10 -0800 From: swear@blarg.net (Gary W. Swearingen) To: freebsd-stable@freebsd.org Subject: How do I handle repeatable OS crash? Message-ID: <3gpu3gwoct.u3g@localhost.localdomain>
next in thread | raw e-mail | index | archive | help
I'm running 4.5-PRE from about 26'dec'02 and have a badly-burned CD-R with which I can repeatably hang the system by simply trying to mount it. I haven't seen any error messages in /var/log/messages, but did see a bunch of stuff come to the console which it seemed to be re-writing slightly differently (it seemed to be flashing) and which I failed to try to copy to paper. Any way to get that to go to a file when it's still writable? I'd like to know how to gather info for a good PR. Is this documented somewhere? I didn't see it in the Handbook. I suppose I can determine how to create a "crash file" from the dumpon man page, but I'll bet it'd be real helpful to have some cookbook recipes for using a debugger on the crash file. Which debugger? gdb? ddb? Can I do anything with a normal kernel, or do I HAVE to rebuild it with extra options? I'm thinking I should work with the now-old OS version because if I upgrade to 4.5-R or -S, some weird interaction may hide the bug. Even if it has simply been fixed, I'd sort of like to see how this works for next time, before upgrading the OS. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3gpu3gwoct.u3g>