Date: Mon, 12 Jan 2009 15:00:41 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Pete French <petefrench@ticketswitch.com> Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net Subject: Re: Big problems with 7.1 locking up :-( Message-ID: <alpine.BSF.2.00.0901121458140.16794@fledge.watson.org> In-Reply-To: <E1LLg5j-000Lmm-QO@dilbert.ticketswitch.com> References: <E1LLg5j-000Lmm-QO@dilbert.ticketswitch.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 10 Jan 2009, Pete French wrote: >> FWIW, the other guy I know who is having this problem had already switched >> to using ULE under 7.0-release, and did not have any problems with it. So >> *his* problem was probably not related to SCHED_ULE, unless something has >> recently changed there. > > Well, one of my machines just locked up again, even with SCHED_4BSD on it, > so I am now thinking it is unrelated. > > The machine has completely locked - no response to pings, no response to > keypresses, nor to the power button. There is nothing printed on the console > - it is just sitting there with a login prompt :-( > > This is really not good - these are extremely common servers after all, and > I am just running bog standard 7.1 with apache and mysql. This is happening > across several different servers, all of which are slight variants on the > DL360, so I dont think it is something perculiar to me. I'm not sure if you've done this already, but the normal suggestions apply: have you compiled with INVARIANTS/WITNESS/DDB/KDB/BREAK_TO_DEBUGGER, and do any results / panics / etc result? Sometimes these debugging tools are able to convert hangs into panics, which gives us much more ability to debug them. If it still hangs rather than panicking, are you able to break into the debugger on the console? If you're using a video console and not able to get to the debugger, would it be possible to configure a serial console and use that -- serial breaks are often more successful at getting to the debugger than keyboard breaks. Likewise, I'm not sure if this hardware has an NMI button -- some HP servers have one on the motherboard that you can press -- but that is also potentially a way to get into the debugger the analyze the crash. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0901121458140.16794>