From owner-freebsd-smp Sun Apr 5 16:29:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21182 for freebsd-smp-outgoing; Sun, 5 Apr 1998 16:29:30 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21118 for ; Sun, 5 Apr 1998 16:29:24 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id TAA24641; Sun, 5 Apr 1998 19:26:08 -0400 (EDT) From: Peter Dufault Message-Id: <199804052326.TAA24641@hda.hda.com> Subject: Re: beware! -current under SMP is "not looking good". In-Reply-To: <199804050750.PAA07051@spinner.netplex.com.au> from Peter Wemm at "Apr 5, 98 03:50:49 pm" To: peter@netplex.com.au (Peter Wemm) Date: Sun, 5 Apr 1998 19:26:07 -0400 (EDT) Cc: peter@netplex.com.au, smp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It seems that doing a 'setpriority()' is the last thing that happens > before the hang with ntpdate. I wonder if the posix4 stuff is having an > effect here? The latest round of changes were minor. The "maybe_resched" that went in near the beginning of March would be more likely to cause problems - that was what broke idle priority. That leaves a big window from the beginning of March until now so I expect the problem would have shown up earlier. Anyone suspecting them can roll back to the date of that last change to sys/_posix.h and verify if the problems are new or not. The only recent non-optional change is the check of the new scheduling classes in swtch.s and I don't think that can cause any problems. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message