From owner-freebsd-current Wed Mar 8 15: 4:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (hda.bicnet.net [208.220.68.243]) by hub.freebsd.org (Postfix) with ESMTP id AD45737B62C for ; Wed, 8 Mar 2000 15:04:37 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id SAA64038; Wed, 8 Mar 2000 18:08:06 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200003082308.SAA64038@hda.hda.com> Subject: Re: current lockups In-Reply-To: <00Mar8.103928est.115210@border.alcanet.com.au> from Peter Jeremy at "Mar 7, 2000 09:45:55 am" To: Peter Jeremy Date: Wed, 8 Mar 2000 18:08:06 -0500 (EST) Cc: Dave Boers , Arun Sharma , freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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). There's no difference between rtprio and P1003.1B scheduling other than the name. rtprio is the same as P1003.1B "SCHED_RR". I'd like to remove the rtprio call from ntpd. I think we ought to do it now before 4.0 ships. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message