From owner-freebsd-current Mon Mar 6 11:27:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id C7FDB37B817 for ; Mon, 6 Mar 2000 11:27:09 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1000) id 867385D7E; Mon, 6 Mar 2000 20:27:18 +0100 (CET) Date: Mon, 6 Mar 2000 20:27:18 +0100 From: Dave Boers To: Arun Sharma Cc: freebsd-current@freebsd.org Subject: Re: current lockups Message-ID: <20000306202718.A26973@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <20000304235010.B10778@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000304235010.B10778@sharmas.dhs.org>; from adsharma@sharmas.dhs.org on Sat, Mar 04, 2000 at 11:50:10PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is rumoured that Arun Sharma had the courage to say: > Compiling Mozilla with make -j 2 got -current to lock up, twice in > succession. I'm running a fairly recent snapshot (a week or two old) > on a Dual celeron box (BP6) with UDMA66 enabled. Finally. I've been complaining about this on several occasions. I'm also running UDMA66 and Dual Celeron BP6. No overclocking. > The kernel had DDB enabled. I was running X, but I didn't see any > signs of the kernel attempting to get into the debugger. Ditto here. > 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. Regards, Dave. -- 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