On 25-Mar-2003 Andrew Gallatin wrote:
>
> Martin Karlsson writes:
>
> > #9 0xc02dca88 in calltrap () at {standard input}:96
> > #10 0xc01e7b0b in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:528
> > #11 0xc020256e in witness_lock (lock=0xc03760c0, flags=8, file=0xc0332416
> "/usr/src/sys/vm/vm_fault.c", line=206)
> > at /usr/src/sys/kern/subr_witness.c:604
> > #12 0xc01e0237 in _mtx_lock_flags (m=0xc03760c0, opts=0, file=0xc0332416
> "/usr/src/sys/vm/vm_fault.c", line=206) at /usr/src/sys/kern/kern_mutex.c:336
>
>
> It looks like the witness mutex debugging system crashed. This sort
> of thing tends to happen when the witness data structures become
> corrupt. A frequent cause of this is a module failing to destroy a
> mutex.
>
> I think the recent addition of the
>
> MTX_SYSINIT(linux_osname, &osname_lock, "linux osname", MTX_DEF);
>
> could be causing the problem, as I do not see how its getting torn
> down.
Oh, good catch Drew. My bad it seems :( I'll work up a patch.
--
John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
