Date: Fri, 4 Apr 2008 11:01:08 +0100 From: Rui Paulo <rpaulo@FreeBSD.org> To: "Tuc at T-B-O-H.NET" <ml@t-b-o-h.net> Cc: freebsd-current@freebsd.org Subject: Re: Reproducable Kernel HARD lockup Message-ID: <20080404095923.GA955@fnop.net> In-Reply-To: <200804040424.m344OQZ3012363@himinbjorg.tucs-beachin-obx-house.com> References: <200804040424.m344OQZ3012363@himinbjorg.tucs-beachin-obx-house.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 04, 2008 at 12:24:26AM -0400, Tuc at T-B-O-H.NET wrote: > Hi, > > LONG LONG LONG story made short. > > Running Soekris 4801-60 previously on 5.5 . Would lock up > every so often, then more often, then finally constantly. Shipped > back to vendor, replaced, all good. Months later started to lock > every few weeks, then every few hours. Replace CF with hard drive, > locks in 10 minutes, etc. > > Load OpenBSD on disk. Runs for days with no problem. > Decide I don't like OpenBSD ports system so decide to go FreeBSD > 7. Glitch with memory stick, but otherwise system seems to run > fine. Start SETI, system locks HARD. I have it set to be able > to break to debugger with CR ~ ^b, but that just doesn't happen. > (Previously tested it would in single user when system running > fine). > > Is there any way to debug a kernel lockup if you CAN'T > break to debugger?? http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Hope this helps. -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080404095923.GA955>