Re: kern/38291: panic: LOCKDEBUG, _kernel_unlock: assertion failed: nlocks <= 0, unmounting MFS /tmp

["Greg A. Woods" <woods%planix.com@localhost>]

The following reply was made to PR kern/38291; it has been noted by GNATS.

From: "Greg A. Woods" <woods%planix.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: ad%NetBSD.org@localhost,
        gnats-admin%netbsd.org@localhost,
        netbsd-bugs%netbsd.org@localhost,
        "Greg A. Woods" <woods%planix.com@localhost>
Subject: Re: kern/38291: panic: LOCKDEBUG, _kernel_unlock: assertion failed: 
nlocks <= 0, unmounting MFS /tmp
Date: Fri, 28 Mar 2008 07:18:07 -0400

 I think I can confirm this problem has been fixed -- no sign of it in
 reboots since installing the new kernel today anyway.
 
 There's only one oddity that I'm not sure was there before.  The date on
 the root node of the MFS /tmp filesystem is now showing up as zero(0):
 
 15:23 [105] # TZ=GMT0 lla -T /tmp
 total 6
 2 2 drwxrwxrwt   2 root  wheel   512 Jan  1 00:00:00 1970 .
 2 4 drwxr-xr-x  21 root  wheel  1536 Mar 27 17:19:06 2008 ..
 15:23 [106] # df
 Filesystem  512-blocks       Used      Avail %Cap Mounted on
 /dev/wd0a     50630888    4703664   43395680   9% /
 mfs:156        1016286          2     965470   0% /tmp
 kernfs               2          2          0 100% /kern
 15:23 [107] # mount  
 /dev/wd0a on / type ffs (local)
 mfs:156 on /tmp type mfs (synchronous, nosuid, nodev, local)
 kernfs on /kern type kernfs (local)
 15:23 [108] # fgrep /tmp /etc/fstab
 swap                    /tmp    mfs     rw,-s=512m,nodev,nosuid  0 0
 15:23 [109] # 
 
 
 I also see that /tmp is not unmounted upon reboot, and I think it should
 be, at least with "options DIAGNOSTIC" if nothing else
 
 -- 
                                                Greg A. Woods
                                                Planix, Inc.
 
 <woods%planix.com@localhost>     +1 416 489-5852 x122     
http://www.planix.com/