Date: Fri, 11 May 2007 17:47:35 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Roger Miranda <rmiranda@digitalrelay.ca> Cc: freebsd-stable@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: Hard Hang, nothing in logs / no panics Message-ID: <20070511214735.GA31850@xor.obsecurity.org> In-Reply-To: <200705111643.08417.rmiranda@digitalrelay.ca> References: <200705111442.52523.rmiranda@digitalrelay.ca> <200705111621.26691.rmiranda@digitalrelay.ca> <20070511213830.GA31604@xor.obsecurity.org> <200705111643.08417.rmiranda@digitalrelay.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 11, 2007 at 04:43:06PM -0500, Roger Miranda wrote: > > > You missed that the debugger is there to debug bugs (including > > deadlocks). Break to the debugger and obtain the necessary debugging > > I should've been more clear. I can not break to the debugger (CTRL-ALT-ESC) > when the system locks up. You may need the KDB_STOP_NMI option, especially if it is an SMP system. I forget if you also need to enable a sysctl on 6.x (look at sysctl -a | grep nmi for the obvious one) > Am I possible looking at a hardware issue? If so > what is the best way to test for it? If that doesn't work then in my experience it is likely to be hardware-related. The usual debugging procedure then involves trying to replicate on an unrelated machine, and/or swapping out hardware components. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070511214735.GA31850>