Date: Fri, 20 May 2005 23:32:33 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Kachun Lee <kachun@pathlink.com> Cc: freebsd-stable@freebsd.org Subject: Re: 5.4 panic at lockmgr Message-ID: <20050521063233.GA51618@xor.obsecurity.org> In-Reply-To: <5.0.2.1.2.20050520163227.00b99ec0@dvl.pathlink.com> References: <5.0.2.1.2.20050520163227.00b99ec0@dvl.pathlink.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Fri, May 20, 2005 at 04:39:19PM -0700, Kachun Lee wrote: > Hi, > > I upgraded a server from 4.10 to 5.4-rel and it paniced at soon as I put > some load on it... > > panic: lockmgr: thread 0xfffffffe, not exclusive lock holder 0x76fe0300 > unlocking > cpuid = 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 > 0x6f448c7d > vop_stdputpages(bcd33b28,bcd33b14,6f2ebb6f,bcd33b28,bcd33b54) at 0x6f37191e > 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 = 0, esp = 0xbcd33d7c, ebp = 0 --- > > The hardware is a Intel 7501 with a single 3G Xeon 6G mem. I tried disable > option MP and made no difference. Any help or suggestion!? Run 'show lockedvnods' and then 'trace <pid>' for each pid listed. Also, if you can explain how to reproduce this it would be greatly helpful. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCjtYBWry0BWjoQKURAlGNAKC+rENyYXsROxYfv2ZD0z7Au82vpQCgjDko ZN+HkBwo41AAmsmGcwYrjfs= =qBFF -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050521063233.GA51618>