Date: Wed, 24 Jan 2001 20:31:47 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: John Baldwin <jhb@FreeBSD.ORG> Cc: alpha@FreeBSD.ORG Subject: RE: cvs commit: src/sys/i386/i386 exception.s src/sys/kern kern_ Message-ID: <14959.33141.988328.39242@grasshopper.cs.duke.edu> In-Reply-To: <XFMail.010124151836.jhb@FreeBSD.org> References: <200101242159.f0OLxPG97598@freefall.freebsd.org> <XFMail.010124151836.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14959.33141.988328.39242>