From owner-freebsd-alpha Wed Jan 24 17:32: 9 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 90A4B37B401; Wed, 24 Jan 2001 17:31:51 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA29177; Wed, 24 Jan 2001 20:31:47 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f0P1Vlh18838; Wed, 24 Jan 2001 20:31:47 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 24 Jan 2001 20:31:47 -0500 (EST) To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: RE: cvs commit: src/sys/i386/i386 exception.s src/sys/kern kern_ In-Reply-To: References: <200101242159.f0OLxPG97598@freefall.freebsd.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14959.33141.988328.39242@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > > On 24-Jan-01 John Baldwin wrote: > > jhb 2001/01/24 13:59:25 PST > > > > Modified files: > > sys/i386/i386 exception.s > > sys/kern kern_fork.c > > sys/sys proc.h > > sys/alpha/alpha swtch.s trap.c vm_machdep.c > > Log: > > - Change fork_exit() to take a pointer to a trapframe as its 3rd argument > > instead of a trapframe directly. (Requested by bde.) > > - Convert the alpha switch_trampoline to call fork_exit() and use the MI > > fork_return() instead of child_return(). > > - Axe child_return(). > > This should fix Drew's WITNESS panic as the mutex release of sched_lock > by a forked child will be noticed by WITNESS now. Bingo. I'm now booting a WITNESS kernel. Thanks for fixing this so quickly! One last thing to point out -- when amd starts, I see this: lock order reversal 1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:644 2nd 0xfffffc000074d030 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940 3rd 0xfffffe0006a774c0 vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949 But it keeps on booting. I'm running a fairly old world, so there may be some sort of kernel / userland sync issue.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message