Date: Wed, 05 Dec 2001 13:03:30 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: "PSI, Mike Smith" <mlsmith@mitre.org> Cc: hackers@freebsd.org Subject: RE: Tracking down system freeze Message-ID: <XFMail.011205130330.jhb@FreeBSD.org> In-Reply-To: <3C0E641B.F65BAC6@mitre.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05-Dec-01 PSI, Mike Smith wrote: > Hi all. > > Does anyone have ANY suggestions on how to determine where the > kernel/program is when the system freezes??? Even hardware solutions, > such as the infamous paperclip across two pins will do. > > I am trying to track down what appears to be a kernel freeze problem, > but alas, debuggers, et.al. are worthless because they too are frozen. > It appears to be one of those difficult problems where part A is doing > something wrong (which it doesn't mind) but later unrelated part B is > being blasted by it. And of course, while it happens often, it doesn't > happen every time. > > But I can't tell where we are when the system freezes. Is there any way > to kick the system in the butt somehow to at least let the debugger do > it's thing? Trigger an NMI. Alfred's post was one way of doing this. There are also various instructions floating around on building NMI switches on the web that you might be able to find. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ 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?XFMail.011205130330.jhb>