From owner-freebsd-current Mon Mar 6 12: 0:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from c62443-a.frmt1.sfba.home.com (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id E54A037BC3C for ; Mon, 6 Mar 2000 12:00:40 -0800 (PST) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id MAA16054; Mon, 6 Mar 2000 12:00:34 -0800 Date: Mon, 6 Mar 2000 12:00:34 -0800 From: Arun Sharma To: Dave Boers Cc: freebsd-current@freebsd.org Subject: Re: current lockups Message-ID: <20000306120033.A16043@sharmas.dhs.org> References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <20000306202718.A26973@relativity.student.utwente.nl>; from Dave Boers on Mon, Mar 06, 2000 at 08:27:18PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 06, 2000 at 08:27:18PM +0100, Dave Boers wrote: > > Has this been fixed ? Is anyone interested in investigating ? > > I'll post more info if I find anything. > > I'm interested in the fix, of course :-) But where to start looking? I've > had three lockups so far (none before january 2000) but I didn't find > anything that reliably triggered it. 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. 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. If you'd like to do something about it, working on getting a reproducible hang would be the most beneficial one. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message