From owner-freebsd-current Thu Jan 18 4: 6:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id BD8FB37B401; Thu, 18 Jan 2001 04:05:58 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0IC5rK13062; Thu, 18 Jan 2001 04:05:54 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101181205.f0IC5rK13062@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Soren Schmidt Cc: jhb@FreeBSD.ORG (John Baldwin), bright@wintelcom.net (Alfred Perlstein), current@FreeBSD.ORG, arch@FreeBSD.ORG, rjesup@wgate.com Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <200101180957.KAA33489@freebsd.dk> Content-Transfer-Encoding: 8bit Date: Thu, 18 Jan 2001 04:05:53 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > It seems Soren Schmidt wrote: > > > I actually used this: > > > > > > CFLAGS ?= -O -pipe -mcpu=i686 -march=i686 > > > COPTFLAGS ?= -O -pipe -mcpu=i686 -march=i686 > > > > > > All the diffs in sys/ on the box I built this kernel on are at > > > http://www.FreeBSD.org/~jhb/patches/sys-mutex.patch. One possibly notabl e > > > patch I had forgotten about is the fix to forward_signal() to lock with > > > sched_lock. I've just committed that though. > > > > OK, I have installed those patches and will try out a kernel build on > > that asap.... > > Hmm, now we are getting somewhere, it ran through a make world with > that patch installed! > > I'll test some more, maybe you should get it all committed it seems to > make a hell of a difference.... Hmm. with the mp_machdep.c fix committed, that leaves the only other significant difference being the re-enable of HLT when a cpu goes idle in i386/i386/machdep.c. The refcount.[ch] stuff is not relevant to this problem. The kern/subr_prf.c change doesn't *appear* to be a likely candidate, unless you are printing lots of console messages during the buildworld.. The kern/vfs_aio.c are not relevant as VFS_AIO is not in GENERIC. The rest are comments, mtx_assert()'s or DDB activation related. 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!) Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message