Date: Fri, 9 Mar 2007 17:10:10 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Oleg Derevenetz <oleg@vsi.ru> Cc: freebsd-stable@freebsd.org Subject: Re: Processes get stuck in "ufs" state Message-ID: <20070309151010.GC73957@deviant.kiev.zoral.com.ua> In-Reply-To: <001101c7625c$c9997860$c8c55358@delloleg> References: <007d01c7605f$79fa60c0$3b215250@NOTEBOOK> <20070307030448.GQ10453@deviant.kiev.zoral.com.ua> <001101c7625c$c9997860$c8c55358@delloleg>
next in thread | previous in thread | raw e-mail | index | archive | help
--nmemrqcdn5VTmUEE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 09, 2007 at 06:08:25PM +0300, Oleg Derevenetz wrote: > On Wed, Mar 07, 2007 at 05:22:38AM +0300, Oleg Derevenetz wrote: >=20 > >>Sometimes (once a week approximately) I have a problem with the same > >>symptoms described here on SMP FreeBSD 6.2-STABLE with dual AMD=20 > >>Opteron(tm) > >>Processor 850: > >> > >>http://www.freebsd.org/cgi/query-pr.cgi?pr=3D104406&cat=3D > >> > >>Sometimes (apparently when CPU load suddenly goes up) all processes that > >>interacts with disk gets stuck in "ufs" state, but in my case > >>SIGSTOP/SIGCONT seemingly does not help. > > > >See developer handbook, Deadlock Debugging chapter for instruction what > >information shall be gathered to debug the problem. >=20 > OK, I built kernel with debug options and will wait for stuck. By the way= ,=20 > when debug options turned on, I see this message on every boot when nullf= s=20 > mounting in progress: >=20 > acquiring duplicate lock of same type: "vnode interlock" > 1st vnode interlock @ /usr/src/sys/kern/vfs_vnops.c:806 > 2nd vnode interlock @ /usr/src/sys/kern/vfs_subr.c:2040 > KDB: stack backtrace: > kdb_backtrace(3,cfc60300,c05926d0,c05926d0,c05542c4,...) at=20 > kdb_backtrace+0x29 > witness_checkorder(cfd5c4dc,9,c051cf1e,7f8) at witness_checkorder+0x578 > _mtx_lock_flags(cfd5c4dc,0,c051cf1e,7f8,cfb28b90,...) at=20 > _mtx_lock_flags+0x78 > vrefcnt(cfd5c414) at vrefcnt+0x20 > null_checkvp(cff5eae0,c050c4a6,215) at null_checkvp+0x56 > null_lock(f02f1a68) at null_lock+0x66 > VOP_LOCK_APV(c054d540,f02f1a68) at VOP_LOCK_APV+0x87 > vn_lock(cff5eae0,1002,cfc60300,cff5eae0,cff5ed04,...) at vn_lock+0xac > nullfs_root(cff76b90,2,f02f1ae0,cfc60300,0,8,0,c05cfca0,0,c051c79c,407) a= t=20 > nullfs_root+0x26 > vfs_domount(cfc60300,cfe3d340,cfe3d130,d,cfe3d3f0,c05817e0,0,c051c79c,2bf= )=20 > at vfs_domount+0x975 > vfs_donmount(cfc60300,d,cfe73080,cfe73080,0,...) at vfs_donmount+0x3f9 > nmount(cfc60300,f02f1d04) at nmount+0x8b > syscall(3b,3b,3b,bf7fe5f5,bf7feea0,...) at syscall+0x25b > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (378, FreeBSD ELF32, nmount), eip =3D 0x280bc0e7, esp =3D=20 > 0xbf7fe5bc, ebp =3D 0xbf7fee38 --- >=20 > This host have nullfs filesystems. Is this can be related to deadlock ? This is harmless, just ignore it. --nmemrqcdn5VTmUEE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFF8XjSC3+MBN1Mb4gRAhGYAJkBhYQHVymZIAHrI+aubM6PM4IAygCeO9iw eb1kKBx+suko9z0MpgFmwmk= =r6v/ -----END PGP SIGNATURE----- --nmemrqcdn5VTmUEE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070309151010.GC73957>