Date: Mon, 20 Nov 2006 17:26:40 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Yoichi Nakayama <yoichi@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: kern/105229: panic in sync_fsync Message-ID: <20061120152640.GH1841@deviant.kiev.zoral.com.ua> In-Reply-To: <87vela6xnm.wl%yoichi@FreeBSD.org> References: <200611062349.kA6NnbCG051817@www.freebsd.org> <20061107192218.GB1624@kobe.laptop> <878ximm418.wl%yoichi@FreeBSD.org> <20061109112035.GA1722@kobe.laptop> <86mz709d7u.wl%yoichi@geiin.org> <87vela6xnm.wl%yoichi@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--1xx5Q0+Cw+ObE54D Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 20, 2006 at 10:43:57PM +0900, Yoichi Nakayama wrote: > At Fri, 10 Nov 2006 12:45:25 +0900, > Yoichi NAKAYAMA wrote: > > At Thu, 9 Nov 2006 13:20:35 +0200, > > Giorgos Keramidas wrote: > > > On 2006-11-08 23:00, Yoichi Nakayama <yoichi@FreeBSD.org> wrote: > > > >At Tue, 7 Nov 2006 21:22:18 +0200, > > > >Giorgos Keramidas wrote: > > > >> Hi NAKAYAMA-san :) > > > >> > > > >> In general, we handle CURRENT problems in the freebsd-current mail= ing > > > >> list, instead of opening problem reports. > > > > > > > > I'm sorry for my mistake. > > >=20 > > > Nothing to worry about :) > > >=20 > > > >> The build from `2006.11.07.05.51.41', as I said seems to work fine. > > > >> > > > >> Can you try re-syncing your source tree to see if a newer commit h= as > > > >> fixed this in CURRENT? > > > > > > > > Thanks for your suggestion. I've already synced it to current > > > > yesterday (after the time vfs_subr.c Revision 1.691 was committed at > > > > Nov 7 19:45:05 2006 UTC), and I'm keeping it running. > > > > > > > > I'll post a report to freebsd-current list after one week trial. > > > > I've met the same problem for some number of times after 2-7 days r= un. > > >=20 > > > Cool! Unfortunately, I don't leave my laptop running for so long. > > > If this is related to staying up several days, I wouldn't notice it > > > easily :) > >=20 > > Then, I got panic at another place. >=20 > With the same kernel (current in Nov 7 2006), I got panic at sync_fsync a= gain: >=20 > panic: mtx_lock() of spin mutex vnode interlock @ /usr/src/sys/kern/vfs_s= ubr.c:2855 > ... > #13 0xc06b131f in panic (fmt=3D0xc0930a10 "mtx_lock() of spin mutex %s @ = %s:%d") > ---Type <return> to continue, or q <return> to quit--- > at /usr/src/sys/kern/kern_shutdown.c:551 > #14 0xc06a85c0 in _mtx_lock_flags (m=3D0xc58593a8, opts=3D0,=20 > file=3D0xc093c091 "/usr/src/sys/kern/vfs_subr.c", line=3D2855) > at /usr/src/sys/kern/kern_mutex.c:131 > #15 0xc0712570 in vfs_msync (mp=3D0xc3d4e538, flags=3D2) > at /usr/src/sys/kern/vfs_subr.c:2855 Please, show the output of the "p *vp" and "p *mp" at this frame. > #16 0xc0712d21 in sync_fsync (ap=3D0x0) at /usr/src/sys/kern/vfs_subr.c:3= 089 > #17 0xc08bafde in VOP_FSYNC_APV (vop=3D0x0, a=3D0xe3c39cb4) at vnode_if.c= :1007 > #18 0xc071094e in sync_vnode (bo=3D0xc3d4b704, td=3D0xc3924c40) at vnode_= if.h:537 > #19 0xc0710bcd in sched_sync () at /usr/src/sys/kern/vfs_subr.c:1691 > #20 0xc069b908 in fork_exit (callout=3D0xc07109dc <sched_sync>, arg=3D0x0= ,=20 > frame=3D0xe3c39d38) at /usr/src/sys/kern/kern_fork.c:834 > #21 0xc08943bc in fork_trampoline () at /usr/src/sys/i386/i386/exception.= s:199 >=20 > Regards, > --=20 > Yoichi NAKAYAMA > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --1xx5Q0+Cw+ObE54D Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFYckvC3+MBN1Mb4gRAl7WAKCuxyz8zDcdQeOcTEbzxF4fQmfsQACdFJpE OlbPjFcuJa/4X5cxOUGyOjw= =aU08 -----END PGP SIGNATURE----- --1xx5Q0+Cw+ObE54D--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061120152640.GH1841>