From owner-freebsd-current Tue Mar 7 16: 8: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 49F4537BAFC for ; Tue, 7 Mar 2000 16:08:06 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA59006; Tue, 7 Mar 2000 16:08:00 -0800 (PST) (envelope-from dillon) Date: Tue, 7 Mar 2000 16:08:00 -0800 (PST) From: Matthew Dillon Message-Id: <200003080008.QAA59006@apollo.backplane.com> To: Peter Jeremy Cc: Dave Boers , Arun Sharma , freebsd-current@FreeBSD.ORG Subject: Re: current lockups References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> <00Mar8.103928est.115210@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On 2000-Mar-07 06:29:17 +1100, Dave Boers wrote: :>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. : :Later postings mention possible problems with UDMA66. The other :possibility that has been discussed recently is potential priority :inversions for processes using rtptio and idprio. : :Note that ntpd will use rtprio if the Posix P1003.1b extensions aren't :enabled in the kernel. (These were enabled by default in GENERIC on :i386 in mid-January). If you have the new ntpd (rather than xntpd) :and are running a kernel without options P1003_1B, :_KPOSIX_PRIORITY_SCHEDULING and _KPOSIX_VERSION=199309L, you could :potentially get a lockup due to a priority inversion. (Though I :think the probability is very small). : :Peter p.s. the first thing anyone having potential IDE problems should do is try the older 'wd' driver (if it supports their chipset) and see if that solves the problem. At least then we can focus on the precise location of the problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message