From owner-freebsd-current Thu Jan 18 5: 9:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 948E537B400; Thu, 18 Jan 2001 05:09:32 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA84777; Thu, 18 Jan 2001 14:09:21 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200101181309.OAA84777@freebsd.dk> Subject: Re: HEADS-UP: await/asleep removal imminent In-Reply-To: <200101181205.f0IC5rK13062@mobile.wemm.org> from Peter Wemm at "Jan 18, 2001 04:05:53 am" To: peter@netplex.com.au (Peter Wemm) Date: Thu, 18 Jan 2001 14:09:21 +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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Peter Wemm wrote: > > 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. That still lockups, tried a freshly checked out sys... > 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!) I'll try adding the forward_signal stuff see if that helps... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message