Date: Wed, 06 Nov 2002 22:07:23 -0800 From: "Joel M. Baldwin" <qumqats@outel.org> Cc: current@FreeBSD.ORG Subject: Re: Why is my -current system Hard Locking? Message-ID: <101370893.1036620443@[192.168.1.20]>
next in thread | raw e-mail | index | archive | help
--On Wednesday, November 06, 2002 9:23 PM -0600 Sean Kelly <smkelly@zombie.org> wrote: > > . . . snip . . . > > I just came across this problem for the first time on my -CURRENT > from Wed Oct 30. I was in the middle of reading a message in mutt (my > MUA) on the console and the system just froze. I was also cvsup'ing > ports on another vty at the time. There was no way to get a dump or > backtrace. Nothing, including networking, was responding. > > Here are a few things you might want to try: > 1. Check your syslog to get an estimate of when the machine dies. Is > it during high disk activity? Mine did it during a ports cvsup. > Could it be doing it in relation to the /etc/security stuff? Does > it happen around the same times every day? The harder I press the system, the greater the odds of the lockup. A buildworld and other stuff will eventually crash. > 2. Build a kernel with GDB_REMOTE_CHAT and try a remote gdb session > against the kernel? Not sure how much information this will > provide, since the machine will most likely stop responding to the > remote gdb. 3. Figure out when the problem started happening for the > first time and see what was commit'd around then. I've hooked up a serial console and am going to try forcing a NMI via the ISA IOCHK pin. > . . . snip . . . > > -- > Sean Kelly | PGP KeyID: 77042C7B > smkelly@zombie.org | http://www.zombie.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?101370893.1036620443>