Date: Mon, 6 Mar 2000 21:26:07 +0100 From: Dave Boers <djb@relativity.student.utwente.nl> To: Arun Sharma <adsharma@sharmas.dhs.org> Cc: Dave Boers <djb@wit389306.student.utwente.nl>, freebsd-current@freebsd.org Subject: Re: current lockups Message-ID: <20000306212607.B27212@relativity.student.utwente.nl> In-Reply-To: <20000306120033.A16043@sharmas.dhs.org>; from adsharma@sharmas.dhs.org on Mon, Mar 06, 2000 at 12:00:34PM -0800 References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> <20000306120033.A16043@sharmas.dhs.org>
next in thread | previous in thread | raw e-mail | index | archive | help
It is rumoured that Arun Sharma had the courage to say: > The cooling theory sounds the most plausible so far. I'm not over clocking > my CPUs (Celeron 366s) and have appropriate cooling installed. But the > machine is kept in a small room, with a bunch of other machines and gets > a bit warm at times. My system has been 50 degrees Celcius for the past half year or so. Yet, the lockups only started occurring around January 2000. Once again, my system is not overclocked and the temperature is well within Intel's and Abit's temperature specifications, so there shouldn't be hardware problems. > There has been no reproducible case of locking up. Each one looks different. > But most were trigerred by heavy compilation and I/O. One was a lockup > overnight with no activity on the system. When it happens, it does not > respond to pings or scroll lock. Most of my lockups occurred when the system was relatively idle. Mostly they happened only after 9 - 11 days of uptime. As you say, each one looks different and there doesn't seem to be a pattern to it. When it locks up, there is no response to the console, the network or the serial terminal. Only the reset button is obeyed. I have DDB in my kernel, but there's no getting into it. Also, no log messages of any kind from just before the lockups. > If you'd like to do something about it, working on getting a reproducible > hang would be the most beneficial one. That's what I have been trying to do for the past few weeks, but I can't seem to trigger it. Uptime is now 2 days and I intend to let it run to 12 or so before make installworld again, to see if I can reproduce it. However, I did recently change from UDMA66 to an U2W SCSI disk for my main partitions (/, /usr, /var, /tmp and swap). It may have impact on the situation and it is the reason for the short uptime. If the problem has gone away now, it might indicate something with the ATA driver. I'll keep you informed. So far, since the disk change I've been putting my system under some heavy load from time to time (like building three large ports and make -j 12 buildworld at the same time). So far, the system is quite stable. Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) 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?20000306212607.B27212>