Date: Sun, 8 Jul 2001 19:27:25 -0400 From: Michael Lucas <mwlucas@blackhelicopters.org> To: hackers@freebsd.org Subject: deliberate kernel panic? Message-ID: <20010708192725.A9093@blackhelicopters.org>
next in thread | raw e-mail | index | archive | help
Hello, I'm writing an article on kernel panics -- specifically, how to prepare for one, how to deal with one, and a cookbook on what to do to give an admin the best possible chance of getting help with the issue. Unfortunately, I haven't built a panicing kernel in years. Is there any way to force a system to panic in such a way as to save a core? I'm sure someone out there has a little program that creates a panic. :) Also, I've found extensive information on how to set up a system, how to save a core, and so on. What I haven't found is what you folks would like from the debug kernel in a trouble report. (I know about dmesg, etc, of course!) What should a user type in kgdb to get information for the initial report? I've seen people say that they have a debug kernel, and be told what to type. Is this the accepted standard? Slightly related question: can you set a system to reboot automatically at a panic, save a core, and continue? Thanks, Michael -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010708192725.A9093>