From owner-freebsd-arch  Thu Jan 18 23:35:52 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP
	id B555937B401; Thu, 18 Jan 2001 23:35:32 -0800 (PST)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id IAA60706;
	Fri, 19 Jan 2001 08:35:15 +0100 (CET)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200101190735.IAA60706@freebsd.dk>
Subject: Re: HEADS-UP: await/asleep removal imminent
In-Reply-To: <200101190701.f0J71Bk09591@mobile.wemm.org> from Peter Wemm at "Jan 18, 2001 11:01:11 pm"
To: peter@netplex.com.au (Peter Wemm)
Date: Fri, 19 Jan 2001 08:35:14 +0100 (CET)
Cc: jhb@FreeBSD.ORG (John Baldwin),
	bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.ORG,
	arch@FreeBSD.ORG, rjesup@wgate.com
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Peter Wemm wrote:
> Soren Schmidt wrote:
> > It seems Peter Wemm wrote:
> > > 
> > > Soren, can you retest a buildworld with the currently committed kernel
> > > with no other changes?  Let us see if the forward_signal() stuff is the
> > > culprit, and if not, try adding just the i386/i386/machdep.c patch to HLT
> > > the idle CPU.  (if *that* makes a difference then we have got trouble!)
> > 
> > It seems that the HLT thing is exactly the patch that makes it work!
> > 
> > So we have trouble, I said that all along .5 :)
> 
> So, the difference between -current working for you or not is this:

[diff snipped]
 
> ??  No other changes?

I need the FULL change to machdep.c and apparently the chagne to subr_prf.c
is needed too, at least it hasnt broke yet with that in place too, not
that I can see why it matters though.

The new diff to machdep.c that jhb made yesterday also causes trouble.

> This is bad news..  This means we have races somewhere, or some other badness.

That is what I've been harping about for months...

What strikes me here as a very serious problem is that the SMPng developers
has told me over and over that it works fine for them on -current, but
when we get to the matter after months of frustration, it suddenly appears
that they are not running the same -current as the rest of us.

Now guys, excuse my language, but that *sucks* bigtime.

However I'm still running tests here, and I'm offering to test every patch
you can come up with to help locate the problem, just as always...

-Søren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message