Date: Mon, 18 Aug 2014 11:41:42 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: panic: pmap active 0xfffff8002d2ae9f8 Message-ID: <20140818084142.GM2737@kib.kiev.ua> In-Reply-To: <295b3f285bffb20608153322d259224a@shatow.net> References: <CAG=rPVe=iNykgxY3OmsSbMjvfL3ap6S9bg3-2fTq-nrNBti_Jg@mail.gmail.com> <53EB868A.1060406@FreeBSD.org> <295b3f285bffb20608153322d259224a@shatow.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--I2AcQh+/kfs26T/w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 15, 2014 at 10:38:25PM -0500, Bryan Drewery wrote: > On 2014-08-13 10:38, Bryan Drewery wrote: > > On 6/24/2014 4:28 PM, Craig Rodrigues wrote: > >> Hi, > >>=20 > >> I have a system running CURRENT at r266925 from May 31. > >>=20 > >> While doing some software builds using poudriere, the system > >> panicked. Unfortunately this system was not configured with > >> swap space, so I cannot do a kernel dump. > >>=20 > >> The system is currently at the ddb prompt. > >> Here is the backtrace: > >>=20 > >>=20 > >> Here is the backtrace from ddb: > >>=20 > >> panic: pmap active 0xfffff8002d2ae9f8 > >> cpuid =3D 5 > >> KDB: stack backtrace: > >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > >> 0xfffffe183958a7d0 > >> kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe183958a880 > >> vpanic() at vpanic+0x126/frame 0xfffffe183958a8c0 > >> kassert_panic() at kassert_panic+0x139/frame 0xfffffe183958a930 > >> pmap_remove_pages() at pmap_remove_pages+0x8c/frame 0xfffffe183958aa20 > >> vmspace_exit() at vmspace_exit+0xa1/frame 0xfffffe183958aa60 > >> exit1() at exit1+0x541/frame 0xfffffe183958aad0 > >> sys_sys_exit() at sys_sys_exit+0xe/frame 0xfffffe183958aae0 > >> amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe183958abf0 > >> Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe183958abf0 > >> --- syscall (1, FreeBSD ELF64, sys_sys_exit), rip - 0x800b195aa, rsp - > >> 0x7ffffffe3e8, rbp =3D 0x7ffffffffe400 > >> KDB: enter: panic > >> [ thread pid 94762 tid 101570 ] > >> Stopped at kdb_enter+0x3e: movq $0.kdb_why > >> db> > >>=20 > >>=20 > >> Is this a known problem? > >> Are there other commands I should type at the ddb prompt? > >> -- > >> Craig > >=20 > > I have run into this as well on r269147: > >=20 > >> panic: pmap active 0xfffff80035f422f8 > >> cpuid =3D 10 > >> KDB: stack backtrace: > >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame=20 > >> 0xfffffe124852b7d0 > >> kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe124852b880 > >> vpanic() at vpanic+0x126/frame 0xfffffe124852b8c0 > >> kassert_panic() at kassert_panic+0x139/frame 0xfffffe124852b930 > >> pmap_remove_pages() at pmap_remove_pages+0x8c/frame 0xfffffe124852ba20 > >> vmspace_exit() at vmspace_exit+0x9c/frame 0xfffffe124852ba60 > >> exit1() at exit1+0x541/frame 0xfffffe124852bad0 > >> sys_sys_exit() at sys_sys_exit+0xe/frame 0xfffffe124852bae0 > >> ia32_syscall() at ia32_syscall+0x270/frame 0xfffffe124852bbf0 > >> Xint0x80_syscall() at Xint0x80_syscall+0x95/frame 0xfffffe124852bbf0 > >> --- syscall (1, FreeBSD ELF32, sys_sys_exit), rip =3D 0x297e386f, rsp = =3D=20 > >> 0xffffd7ac, rbp =3D 0xffffd7b8 --- > >> KDB: enter: panic > >> [ thread pid 85335 tid 101517 ] > >> Stopped at kdb_enter+0x3e: movq $0,kdb_why > >> db> call doadump > >>=20 > >> Dump failed. Partition too small. > >> =3D 0 >=20 > Got it again on recent r269950 while building with poudriere: >=20 > panic: pmap active 0xfffff8113c3c6d78 > cpuid =3D 10 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame=20 > 0xfffffe1248acc7d0 > kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe1248acc880 > vpanic() at vpanic+0x126/frame 0xfffffe1248acc8c0 > kassert_panic() at kassert_panic+0x139/frame 0xfffffe1248acc930 > pmap_remove_pages() at pmap_remove_pages+0x8c/frame 0xfffffe1248acca20 > vmspace_exit() at vmspace_exit+0x9c/frame 0xfffffe1248acca60 > exit1() at exit1+0x541/frame 0xfffffe1248accad0 > sys_sys_exit() at sys_sys_exit+0xe/frame 0xfffffe1248accae0 > amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe1248accbf0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe1248accbf0 > --- syscall (1, FreeBSD ELF64, sys_sys_exit), rip =3D 0x80387fadc, rsp = =3D=20 > 0x7fffffffd4e8, rbp =3D 0x7fffffffd5a0 --- > KDB: enter: panic > [ thread pid 84433 tid 101503 ] > Stopped at kdb_enter+0x3e: movq $0,kdb_why > db> call doadump >=20 > Dump failed. Partition too small. > =3D 0 The interesting information is pmap->pm_active, for pmap address reported by the panic. Easiest way to get the active mask is using kgdb on vmcore. --I2AcQh+/kfs26T/w Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJT8bxGAAoJEJDCuSvBvK1BTe8P/iczyBq1Zz1zUYFXjW8Yybs7 keVhqz7lvDpxNKxYQ6n1IuXeNIUnercYpZbVqB+TkacysSVGYEqg6hPUgEDE/iKO 9rXmqwl/p4Q1//MqyImEtRK97cwU4bc2KSF8boPs4F8+ylUNTjgqVlHggw17++5U 5hOkGJDDGB3gUDaCG5/FYHC80JVy8ZgSBeu+IkRQ3dEfqe/sDudHTYv96X6fHURV yXqZYDemdbvHY72H1vP7tajr73SeuhIUDco1RMv4loM0wlzolbTx4UvEp1janJCy HEoVQZx7Qv2uDh+byAOOEj8yOx3i8pu4COdKSjxiU+oVPcShV8gJae7Fru2C5WuF SIzMMfg7JGc/jbwe7P6qFN8X97DYegVz5OMF5Vvw8xswlaeT0rf49cG9EQSKsGKv rTSX9VpLDMv2Y9gFv1QVscV/wLhcX3BYYSuEKUzZ0SHKPqb/OACx0Bjg7tzi+tby dBJn8NoRE59bHKpsP8uEbl4jlcEZjcAE7n7g5ajGoo0n1iZqwkmGK1BvpoDYBymf GwKVpr64mBbTlViNDvqwn+q++CVgmVZhzP373xTVMOc4p7oBI9gszToZ+YcPv9z7 7+8BITUYqUa//97Vyiy4VwJDxnaXlFJbvOfS880EaofBjyuTS/cNEx4kZ16iI9qm 8CJwaqXjw66YpU0EedhE =+1pQ -----END PGP SIGNATURE----- --I2AcQh+/kfs26T/w--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140818084142.GM2737>