From owner-freebsd-current Mon Mar 6 14:45:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 8B74D37BB25 for ; Mon, 6 Mar 2000 14:45:06 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115210>; Tue, 7 Mar 2000 09:45:55 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: current lockups In-reply-to: <20000306202718.A26973@relativity.student.utwente.nl>; from djb@wit389306.student.utwente.nl on Tue, Mar 07, 2000 at 06:29:17AM +1100 To: Dave Boers Cc: Arun Sharma , freebsd-current@FreeBSD.ORG Message-Id: <00Mar7.094555est.115210@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <20000304235010.B10778@sharmas.dhs.org> <20000306202718.A26973@relativity.student.utwente.nl> Date: Tue, 7 Mar 2000 09:45:55 +1100 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message