Date: Sat, 4 Aug 2007 14:01:54 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Dmitry Morozovsky <marck@rinet.ru> Cc: kib@freebsd.org, current@freebsd.org, howard0su@gmail.com Subject: Re: contemporary -current panic: locking against myself Message-ID: <20070804120154.GS37984@garage.freebsd.pl> In-Reply-To: <20070804154621.R84869@woozle.rinet.ru> References: <20070802155317.X50347@woozle.rinet.ru> <20070803102019.GG37984@garage.freebsd.pl> <20070803164108.C569@woozle.rinet.ru> <20070804094047.V8449@woozle.rinet.ru> <20070804154621.R84869@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--cbsCxbAnPLQXdgdB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 04, 2007 at 03:48:23PM +0400, Dmitry Morozovsky wrote: > Bad news: after increasing swap to 16G (I had also increase maxswzone to = 128M)=20 > it panics: >=20 > panic: lockmgr: locking against myself > cpuid =3D 1 > KDB: enter: panic > [thread pid 93730 tid 100142 ] > Stopped at kdb_enter+0x32: leave > db> wh > Tracing pid 93730 tid 100142 td 0xc65fc660 > kdb_enter(c066f95e,1,c066dfa3,e6d279cc,1,...) at kdb_enter+0x32 > panic(c066dfa3,e6d279dc,c0559ca7,e6d27ac0,c848d220,...) at panic+0x124 > _lockmgr(c848d278,3002,c848d2a8,c65fc660,c0675df6,...) at _lockmgr+0x401 > vop_stdlock(e6d27a5c,c65fc660,3002,c848d220,e6d27a80,...) at vop_stdlock+= 0x40 > VOP_LOCK1_APV(c68a38a0,e6d27a5c,e6d27bc0,1,c6e3b110,...) at VOP_LOCK1_APV= +0x46 > _vn_lock(c848d220,3002,c65fc660,c0675df6,7f3,...) at _vn_lock+0x166 > vget(c848d220,1000,c65fc660,0,e6d27b98,...) at vget+0x114 > vm_object_reference(cefd57f8,e6d27b30,c063faad,c0c71000,e381f000,...) at= =20 > vm_object_reference+0x12a > kern_execve(c65fc660,e6d27c5c,0,282053cc,28205480,e381f000,e381f000,e381f= 065,e381f54e,e385f000,3fab2,9,1f)=20 > at kern_execve+0x31a > execve(c65fc660,e6d27cfc,c,c65fc660,e6d27d2c,...) at execve+0x4c > syscall(e6d27d38) at syscall+0x345 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (59, FreeBSD ELF32, execve), eip =3D 0x28146a47, esp =3D 0xbf= bfe76c,=20 > ebp =3D 0xbfbfe788 --- > db> show lockedvnods > Locked vnodes >=20 > 0xc848d220: tag tmpfs, type VREG > usecount 1, writecount 0, refcount 4 mountedhere 0 > flags (VI_OWEINACT) > v_object 0xcefd57f8 ref 1 pages 57 > lock type tmpfs: EXCL (count 1) by thread 0xc65fc660 (pid 93730) wit= h 1=20 > pending > tag VT_TMPFS, tmpfs_node 0xd091d5c8, flags 0x0, links 1 > mode 0755, owner 0, group 0, size 664544, status 0x0 Yeah, kib@ fixes might be more in order to fix this problem, but at least my patch confirms that you have VI_OWEINACT flag on this vnode. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --cbsCxbAnPLQXdgdB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFGtGqyForvXbEpPzQRAsApAJ9KLmcrl9/2vOLhvvxzy8WCp9VjwACgjCPX j4kAMWYW9RiHota3IpQxpqA= =M9ya -----END PGP SIGNATURE----- --cbsCxbAnPLQXdgdB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070804120154.GS37984>