From owner-freebsd-current Sun Jun 27 5:15:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id A2990150FA; Sun, 27 Jun 1999 05:15:14 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-149.skylink.it [194.185.55.149]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id OAA12709; Sun, 27 Jun 1999 14:14:33 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id OAA02791; Sun, 27 Jun 1999 14:15:06 +0200 (CEST) Date: Sun, 27 Jun 1999 14:15:06 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing list Cc: mckusick@FreeBSD.ORG Subject: lockmgr panics Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kirk, It seems that the recent changes made by Kirk McKusick to the locking mechanism in many files had some side effects. A kernel as of this afternoon kept giving the following panic when compiling a kernel, with the compile and source dir NFS mounted: lockmgr: pid , not exclusive lock holder -2 unlocking lockmgr(c1373b80,6,0,0) + 0x294 relpbuf(c1373b58, c029a384, 2000, c0786e00, c1373b58) + 0x7a swp_pager_async_iodone(c1373b58, 2000, c0786e00, c1373b58, c0786fc4) + 0x1ac biodone(c1373b58, c0786f58, 2000, 3, 1) + 0x4f wdintr(0, 8000000, 10, 10, 10) + 0x63f % mount /dev/wd0s2a on / (NFS exported, local, writes: sync 3 async 106) procfs on /proc (local) /dev/wd0s2e on /var (local, writes: sync 198 async 458) /dev/wd0s2f on /usr (NFS exported, local, writes: sync 455 async 831) 10.1.0.2:/usr/current/src on /usr/src The panic always happened when linking the kernel or objcopy-ing the result. From the DDB prompt 'call boot' failed. After undoing the changes with the commands given at the bottom of the page, it did not fail again. If needed I can try and produce a core file. If I can get the dumping to work that is. BTW and unrelated: In the commit message there was no mentioning of the reviewer for this patch. They probably would mind the credits I guess for the work they've done. Cheers, Nick -- e-Mail: hibma@skylink.it cd /usr/src cvs update -r1.69 sys/sys/buf.h cvs update -r1.13 sys/sys/lock.h cvs update -r1.25 sys/kern/kern_lock.c cvs update -r1.34 sys/kern/kern_physio.c cvs update -r1.52 sys/kern/kern_shutdown.c cvs update -r1.9 sys/kern/subr_dkbad.c cvs update -r1.51 sys/kern/vfs_aio.c cvs update -r1.215 sys/kern/vfs_bio.c cvs update -r1.83 sys/kern/vfs_cluster.c cvs update -r1.202 sys/kern/vfs_subr.c cvs update -r1.74 sys/miscfs/devfs/devfs_vnops.c cvs update -r1.88 sys/miscfs/specfs/spec_vnops.c cvs update -r1.85 sys/msdosfs/msdosfs_vnops.c cvs update -r1.73 sys/nfs/nfs_bio.c cvs update -r1.76 sys/nfs/nfs_subs.c cvs update -r1.131 sys/nfs/nfs_vnops.c cvs update -r1.31 contrib/sys/softupdates/ffs_softdep.c cvs update -r1.57 sys/ufs/ffs/ffs_vnops.c cvs update -r1.44 sys/ufs/mfs/mfs_vnops.c cvs update -r1.39 sys/ufs/ufs/ufs_disksubr.c cvs update -r1.118 sys/vm/swap_pager.c cvs update -r1.47 sys/vm/vm_pager.c cvs update -r1.71 sys/vm/vm_swap.c cvs update -r1.110 sys/vm/vnode_pager.c cvs update -r1.146 sys/isa/fd.c cvs update -r1.29 sys/dev/vinum/vinumio.c cvs update -r1.16 sys/dev/vinum/vinumrequest.c cvs update -r1.12 sys/dev/vinum/vinumrevive.c cvs update -r1.46 sys/gnu/ext2fs/ext2_vnops.c cvs update -r1.4 sys/gnu/ext2fs/fs.h cvs update -r1.17 sys/cam/cam_periph.c cvs update -r1.34 sys/i386/isa/diskslice_machdep.c cvs update -r1.8 sys/alpha/alpha/diskslice_machdep.c cvs update -r1.15 sys/pc98/pc98/atcompat_diskslice.c cvs update -r1.19 sys/pc98/pc98/diskslice_machdep.c cvs update -r1.63 sys/pc98/pc98/fd.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message