Date: Thu, 17 May 2007 20:01:00 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Andrew Edwards <aedwards@sandvine.com> Cc: freebsd-fs@freebsd.org, freebsd-performance@freebsd.org Subject: Re: Ufs dead-locks on freebsd 6.2 Message-ID: <20070517170100.GA41395@deviant.kiev.zoral.com.ua> In-Reply-To: <5230D3C40B842D4F9FB3CD368021BEF72F0908@exchange-2.sandvine.com> References: <5230D3C40B842D4F9FB3CD368021BEF72F08F3@exchange-2.sandvine.com> <5230D3C40B842D4F9FB3CD368021BEF72F0908@exchange-2.sandvine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--oyUTqETQ0mS9luUI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, May 17, 2007 at 11:44:15AM -0400, Andrew Edwards wrote:
> I've upgraded to 6-stable, added the kernel options as per the kernel
> handbook. After about 5 hours of they system in a deadlock it panic'd.
> Here's the backtrace, and show pcpu, show allpcpu, show locks, show
> alllocks, show lockedvnods and alltrace.
>=20
> I will have the system down for approx another 15-20mins if there's
> anything else someone would like while I'm in the debugger.
>=20
>=20
> db> bt
> Tracing pid 46784 tid 105112 td 0xd44a8000
> kdb_enter(c0785f13) at kdb_enter+0x2b
> vfs_badlock(c0785f2c,c0786051,ccd47984) at vfs_badlock+0x47
> assert_vop_locked(ccd47984,c0786051) at assert_vop_locked+0x4a
> vop_lock_post(f9f709dc,0,1002,ccd47984,f9f709f8,...) at
> vop_lock_post+0x2a
> VOP_LOCK_APV(c07dc2e0,f9f709dc) at VOP_LOCK_APV+0xa0
> vn_lock(ccd47984,1002,d44a8000) at vn_lock+0xac
> lookup(f9f70c08) at lookup+0xde
> namei(f9f70c08) at namei+0x39a
> unp_connect(d44b2de8,d44dc380,d44a8000,d44b2de8,25,...) at
> unp_connect+0xf0
> uipc_connect(d44b2de8,d44dc380,d44a8000) at uipc_connect+0x66
> soconnect(d44b2de8,d44dc380,d44a8000) at soconnect+0x4e
> kern_connect(d44a8000,7,d44dc380,d44dc380,0,...) at kern_connect+0x74
> connect(d44a8000,f9f70d04) at connect+0x2f
> syscall(3b,805003b,bfbf003b,bfbfd920,bfbfd922,...) at syscall+0x25b
> Xint0x80_syscall() at Xint0x80_syscall+0x1f
Could you, please, do the "show vnode 0xccd47984" from ddb prompt or
"p/x *(struct vnode *)0xccd47984" from kgdb using dump for this panic ?
Side note: it seems that on HEAD, vnode_if.awk does not generate call to
vop_lock_{pre,post} due to mismatch in the name of vop and pre/post names.
--oyUTqETQ0mS9luUI
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
iD8DBQFGTIpLC3+MBN1Mb4gRAtdjAJ4pBRLR0W6+tKEzFLZBQaO/8TiSlgCZAa1B
npATY/aNbd2+iRhJy8Mdjn8=
=WWY8
-----END PGP SIGNATURE-----
--oyUTqETQ0mS9luUI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070517170100.GA41395>