[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/38291: panic: LOCKDEBUG, _kernel_unlock: assertion failed: nlocks <= 0, unmounting MFS /tmp
The following reply was made to PR kern/38291; it has been noted by GNATS.
From: "Greg A. Woods; Planix, Inc." <woods%planix.ca@localhost>
Subject: Re: kern/38291: panic: LOCKDEBUG, _kernel_unlock: assertion failed:
nlocks <= 0, unmounting MFS /tmp
Date: Tue, 25 Mar 2008 10:52:20 -0400
On 25-Mar-08, at 10:30 AM, Andrew Doran wrote:
> At a guess, the mountpoint is being destroyed. As mount_dounmount
> () returns
> it reads garbage from mp->mnt_iflag and so tries to drop
> kernel_lock. This
> may not have happened before because of a different set of garbage
> in memory
> at the time.
Indeed since the panic does not seem to occur on every reboot there
must be some random or otherwise variable data affecting events.
If I recall correctly the panic I reported occurred after the machine
had sat essentially idle for a while. I'll try to reproduce the
problem today again and see if there's anything salient about how and
when it occurs.
Greg A. Woods; Planix, Inc.
Main Index |
Thread Index |