Date: Thu, 07 May 2015 10:09:49 -0500 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Johan Schuijt-Li <johan@300.nl>, freebsd-stable@freebsd.org Subject: Re: panic: pmap active 0xfffff8001b7154b8 Message-ID: <554B803D.2020506@FreeBSD.org> In-Reply-To: <554B7F5D.3050805@FreeBSD.org> References: <C8964592-7239-4988-AA80-D3634143A5C4@300.nl> <554B7F5D.3050805@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 5/7/2015 10:06 AM, Bryan Drewery wrote: > On 5/7/2015 7:08 AM, Johan Schuijt-Li wrote: >> Hi, >> >> We’ve been seeing (seemingly) random reboots on 10.1-RELEASE virtual machines (KVM virtualisation) on our production servers. In an attempt to determine what was causing this we’ve switched to running a kernel with INVARIANTS enabled. This resulted for us in the following panic: >> >> Unread portion of the kernel message buffer: >> panic: pmap active 0xfffff8001b7154b8 >> cpuid = 3 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe03dd1493a0 >> kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe03dd149450 >> vpanic() at vpanic+0x126/frame 0xfffffe03dd149490 >> kassert_panic() at kassert_panic+0x139/frame 0xfffffe03dd149500 >> pmap_remove_pages() at pmap_remove_pages+0x8c/frame 0xfffffe03dd1495f0 >> exec_new_vmspace() at exec_new_vmspace+0x16a/frame 0xfffffe03dd149650 >> exec_elf64_imgact() at exec_elf64_imgact+0x658/frame 0xfffffe03dd149720 >> kern_execve() at kern_execve+0x5e4/frame 0xfffffe03dd149a80 >> sys_execve() at sys_execve+0x37/frame 0xfffffe03dd149ae0 >> amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe03dd149bf0 >> Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe03dd149bf0 >> --- syscall (59, FreeBSD ELF64, sys_execve), rip = 0x80158af1a, rsp = 0x7fffffffac38, rbp = 0x7fffffffad40 --- >> >> >> I’ve only come across one other report here (without result unfortunate): >> https://lists.freebsd.org/pipermail/freebsd-current/2014-June/050827.html <https://lists.freebsd.org/pipermail/freebsd-current/2014-June/050827.html>; >> > > I looked around for the conclusion of that thread but could not find it. Found it. https://svnweb.freebsd.org/base?view=revision&revision=271000 This fix is in 10.1-RELEASE, so yours must be a little different. -- Regards, Bryan Drewery [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJVS4A9AAoJEDXXcbtuRpfPTR0H/3IXL3w28XcJy/eCgERBSPSU x2KatZ7Gt2vk3atIWdF9sKFsN7KvmM3m442Z/+4WVvIrNzhxuO/UVLfx7FTA2Nwt JfPuPTtnDYlTWApPM525+vAH8Cim7MVuvuNGzzF+lu9yx8z0y3+VGn6LJvbFPvdn P3otCXOA46wDwGDgl2FPT7CU9rEa/SfiWzuu5+pnIb0YxDL+LWUSkf7SHTm0ABvv YF3PlxYBzEthtUpV/J+ZM/32m+UOxsjo7yCdAUIrrYPIdBqCQClAnScGurVAHREp vdwRPOwgUv445FuNm8JJP3CYk1tw86S015htRUV9lYT+GkS0SY+c3u6k6eLttvU= =L9t2 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?554B803D.2020506>