Date: Mon, 4 Nov 2013 18:27:31 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: (r257598) panic: Assertion tmp->tm_pages_used == 0 failed at /usr/src/sys/modules/tmpfs/../../fs/tmpfs/tmpfs_vfsops.c:316 Message-ID: <20131104162731.GQ59496@kib.kiev.ua> In-Reply-To: <5277B0A5.5010506@FreeBSD.org> References: <5277B0A5.5010506@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--8kevPEUzql0NoPNs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 04, 2013 at 08:35:17AM -0600, Bryan Drewery wrote: > 11.0-CURRENT #87 r257598 >=20 > During a poudriere build. >=20 > It creates a tmpfs, builds a port in a jail using that tmpfs and then > removes the tmpfs and recreate the tmpfs before building the next port. >=20 > > panic: Assertion tmp->tm_pages_used =3D=3D 0 failed at /usr/src/sys/mod= ules/tmpfs/../../fs/tmpfs/tmpfs_vfsops.c:316 > > cpuid =3D 9 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe124= 7ee57a0 > > kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe1247ee5850 > > vpanic() at vpanic+0x126/frame 0xfffffe1247ee5890 > > kassert_panic() at kassert_panic+0x136/frame 0xfffffe1247ee5900 > > tmpfs_unmount() at tmpfs_unmount+0x163/frame 0xfffffe1247ee5930 > > dounmount() at dounmount+0x41f/frame 0xfffffe1247ee59b0 > > sys_unmount() at sys_unmount+0x356/frame 0xfffffe1247ee5ae0 > > amd64_syscall() at amd64_syscall+0x265/frame 0xfffffe1247ee5bf0 > > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe1247ee5bf0 > > --- syscall (22, FreeBSD ELF64, sys_unmount), rip =3D 0x8008a02fa, rsp = =3D 0x7fffffffd198, rbp =3D 0x7fffffffd2b0 --- > > Uptime: 44m40s >=20 > > (kgdb) #0 doadump (textdump=3D1) at pcpu.h:219 > > #1 0xffffffff808bcf87 in kern_reboot (howto=3D260) > > at /usr/src/sys/kern/kern_shutdown.c:447 > > #2 0xffffffff808bd495 in vpanic (fmt=3D<value optimized out>, > > ap=3D<value optimized out>) at /usr/src/sys/kern/kern_shutdown.c:754 > > #3 0xffffffff808bd326 in kassert_panic (fmt=3D<value optimized out>) > > at /usr/src/sys/kern/kern_shutdown.c:642 > > #4 0xffffffff81e159d3 in tmpfs_unmount (mp=3D0xfffff810502cd660, > > mntflags=3D<value optimized out>) > > at /usr/src/sys/modules/tmpfs/../../fs/tmpfs/tmpfs_vfsops.c:316 > > #5 0xffffffff8095e1af in dounmount (mp=3D0xfffff810502cd660, flags=3D1= 34742016, > > td=3D0xfffff8013d57a490) at /usr/src/sys/kern/vfs_mount.c:1324 > > #6 0xffffffff8095dd66 in sys_unmount (td=3D0xfffff8013d57a490, > > uap=3D0xfffffe1247ee5b80) at /usr/src/sys/kern/vfs_mount.c:1212 > > #7 0xffffffff80cb7d75 in amd64_syscall (td=3D0xfffff8013d57a490, trace= d=3D0) > > at subr_syscall.c:134 > > #8 0xffffffff80c9c90b in Xfast_syscall () > > at /usr/src/sys/amd64/amd64/exception.S:391 > > #9 0x00000008008a02fa in ?? () Do you have core ? I want to see the struct tmpfs_mount content for the tmpfs mount point which caused the panic. --8kevPEUzql0NoPNs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJSd8ryAAoJEJDCuSvBvK1Bk64P/1OHyBeIehbnQrNSRew/C1u1 oOAQv55DzA+VNN+CjByahMi+tDCANDDLx4VRLWPJGrdbgi/XzYY9o6Xla+4RM/Dy 5HFOB2tB0z8Mo+YHp9qGu9sMexoZSw+lMV+LkrEa+/ZlE0/XnO03AFZePMOsUKVe 94p1QZqFfc6U/tjiBpgqZOYXGfydb/BrxJKFfW3UhBB7iRjLc4zXsNiBTuJalI/x 8qy/Ez7TvAmIuZB3Ci8fk3mQ1ZRwo3x/1m7DkNuJSYgzkx24Ft6b372/zojfjFPX hPulWqIGtHdYSrHcxCCswS9UYpFb6+FI97FG2m7i+RFNsgqfCKMGGf6vtPcXQTvs iq2wuz2yvekVb9qlzfgzIT+9KxPd8d0VKocpSFPpJt3QAtejbNvxxucDXETlbnDj tA7nxdMYxmCvm1JaddChUMR0IwB5k4S/O5yUqupQyejAohtW4kn93bvN6ArRhsDP z4NaBc2Ia/ipco5NwQndFFhM9Dqf3fldGGCGREmBmJd5P7AD9sc7kCvTrsks3AZt VVlEitudv0EBKZ1pfAOej/yf2o9s1bootF1zb7NFHIGOSgqCtH6afiFZIppmS7CX fDnWFRPqGWKJAxozUH102iAVU3Lzn/YW5RwgUV3hBveB9ef3zQ85qmt/TIcoKUzo 2gBsfAnDQG6seIpZ4a1y =gfm3 -----END PGP SIGNATURE----- --8kevPEUzql0NoPNs--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131104162731.GQ59496>