From owner-freebsd-stable@FreeBSD.ORG Sat May 21 06:32:34 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDF6E16A4CE for ; Sat, 21 May 2005 06:32:34 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BE3943D80 for ; Sat, 21 May 2005 06:32:33 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6E4A751459; Fri, 20 May 2005 23:32:33 -0700 (PDT) Date: Fri, 20 May 2005 23:32:33 -0700 From: Kris Kennaway To: Kachun Lee Message-ID: <20050521063233.GA51618@xor.obsecurity.org> References: <5.0.2.1.2.20050520163227.00b99ec0@dvl.pathlink.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <5.0.2.1.2.20050520163227.00b99ec0@dvl.pathlink.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: 5.4 panic at lockmgr X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 May 2005 06:32:34 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 20, 2005 at 04:39:19PM -0700, Kachun Lee wrote: > Hi, >=20 > I upgraded a server from 4.10 to 5.4-rel and it paniced at soon as I put= =20 > some load on it... >=20 > panic: lockmgr: thread 0xfffffffe, not exclusive lock holder 0x76fe0300= =20 > unlocking > cpuid =3D 0 > KDB: enter: panic > [thread pid 101 tid 100112 ] > Stopped at 0x6f33c5a7: nop > db> > db> trace > Tracing pid 101 tid 100112 td 0x76fe0300 > kdb_enter(6f4af15b) at 0x6f33c5a7 > panic(6f4add4c,fffffffe,6f4add36,76fe0300,fffffffe) at 0x6f324cc7 > lockmgr(775d57e4,6,775d5738,0,bcd33a1c) at 0x6f319421 > vop_stdunlock(bcd33a4c,bcd33a28,6f2ebb6f,bcd33a4c,bcd33a68) at 0x6f3711c7 > vop_defaultop(bcd33a4c,bcd33a68,6f2ec0fc,bcd33a4c,1000) at 0x6f371077 > spec_vnoperate(bcd33a4c,1000,7f010000,7747fa00,bcd33ab4) at 0x6f2ebb6f > spec_write(bcd33a94,bcd33ae0,6f448c7d,bcd33a94,2b3) at 0x6f2ec0fc > spec_vnoperate(bcd33a94) at 0x6f2ebb6f > vnode_pager_generic_putpages(775d5738,bcd33bf0,1000,0,bcd33b70) at=20 > 0x6f448c7d > vop_stdputpages(bcd33b28,bcd33b14,6f2ebb6f,bcd33b28,bcd33b54) at 0x6f3719= 1e > vop_defaultop(bcd33b28,bcd33b54,6f448a1a,bcd33b28,1000) at 0x6f371077 > spec_vnoperate(bcd33b28) at 0x6f2ebb6f > vnode_pager_putpages(774dbe70,bcd33bf0,1,0,bcd33b70) at 0x6f448a1a > vm_pageout_flush(bcd33bf0,1,0,78a2f300,bcd33bc8) at 0x6f4403e7 > vm_pageout_clean(6f8cc70c) at 0x6f440311 > vm_pageout_scan(0) at 0x6f441192 > vm_pageout(0,bcd33d48) at 0x6f441f12 > fork_exit(6f441c00,0,bcd33d48) at 0x6f30f3bd > fork_trampoline() at 0x6f46bdcc > --- trap 0x1, eip =3D 0, esp =3D 0xbcd33d7c, ebp =3D 0 --- >=20 > The hardware is a Intel 7501 with a single 3G Xeon 6G mem. I tried disabl= e=20 > option MP and made no difference. Any help or suggestion!? Run 'show lockedvnods' and then 'trace ' for each pid listed. Also, if you can explain how to reproduce this it would be greatly helpful. Kris --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCjtYBWry0BWjoQKURAlGNAKC+rENyYXsROxYfv2ZD0z7Au82vpQCgjDko ZN+HkBwo41AAmsmGcwYrjfs= =qBFF -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB--