Date: Sat, 18 May 2019 05:35:06 -0700 From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Subject: Panic after update from r347896 to r347950: panic: insanity vmem 0xffffffff81d7c840 Message-ID: <20190518123506.GX79998@albert.catwhisker.org>
next in thread | raw e-mail | index | archive | help
--00Xftji29zlN/ZGB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable This was fairly late in the transition from single- to multi-user mode: the NICs had been probed; em0 was determined (correctly) to have no link, but the wireless NIC (wlan0) hadn't associated to the AP yet. I have placed copies of the dump and a couple of screenshots in http://www.catwhisker.org/~david/FreeBSD/head/r347950/ Just before the panic message, there's: =2E....overwrapped tags 0xffffffff81d7cc70: 0 0, 5(cursor) 0xfffff800040086c8: fffffe0c1052c000 8000000, 3(free) and then we get to: panic: insanity vmem 0xffffffff81d7c840 Unread portion of the kernel message buffer: __curthread () at /usr/src/sys/amd64/include/pcpu.h:246 246 __asm("movq %%gs:%P1,%0" : "=3Dr" (td) : "n" (OFFSETOF_CURT= HREAD)); (kgdb) #0 __curthread () at /usr/src/sys/amd64/include/pcpu.h:246 #1 doadump (textdump=3D0) at /usr/src/sys/kern/kern_shutdown.c:383 #2 0xffffffff8049884b in db_dump (dummy=3D<optimized out>,=20 dummy2=3D<optimized out>, dummy3=3D<unavailable>, dummy4=3D<unavailable= >) at /usr/src/sys/ddb/db_command.c:574 #3 0xffffffff80498619 in db_command (last_cmdp=3D<optimized out>,=20 cmd_table=3D<optimized out>, dopager=3D1) at /usr/src/sys/ddb/db_comman= d.c:481 #4 0xffffffff80498394 in db_command_loop () at /usr/src/sys/ddb/db_command.c:534 #5 0xffffffff8049b53f in db_trap (type=3D<optimized out>, code=3D<optimize= d out>) at /usr/src/sys/ddb/db_main.c:252 #6 0xffffffff80bc9acc in kdb_trap (type=3D3, code=3D0, tf=3D<optimized out= >) at /usr/src/sys/kern/subr_kdb.c:692 #7 0xffffffff80fde7d1 in trap (frame=3D0xfffffe0c185ab810) at /usr/src/sys/amd64/amd64/trap.c:619 #8 <signal handler called> #9 kdb_enter (why=3D0xffffffff81252ef5 "panic", msg=3D<optimized out>) at /usr/src/sys/kern/subr_kdb.c:479 #10 0xffffffff80b80c5a in vpanic (fmt=3D<optimized out>, ap=3D<optimized ou= t>) at /usr/src/sys/kern/kern_shutdown.c:885 #11 0xffffffff80b809d3 in panic ( fmt=3D0xffffffff81c75d38 <cnputs_mtx> "\226\216!\201\377\377\377\377") at /usr/src/sys/kern/kern_shutdown.c:823 #12 0xffffffff80be7fd3 in vmem_check ( vm=3D0xffffffff81d7c840 <transient_arena_storage>) at /usr/src/sys/kern/subr_vmem.c:1766 #13 vmem_periodic (unused=3D<optimized out>, pending=3D<optimized out>) at /usr/src/sys/kern/subr_vmem.c:768 #14 0xffffffff80bdcd8c in taskqueue_run_locked (queue=3D0xfffff80009e33500) at /usr/src/sys/kern/subr_taskqueue.c:467 #15 0xffffffff80bddd08 in taskqueue_thread_loop (arg=3D<optimized out>) at /usr/src/sys/kern/subr_taskqueue.c:773 #16 0xffffffff80b40044 in fork_exit ( callout=3D0xffffffff80bddc80 <taskqueue_thread_loop>,=20 arg=3D0xffffffff81e95000 <taskqueue_thread>, frame=3D0xfffffe0c185abac0) at /usr/src/sys/kern/kern_fork.c:1058 #17 <signal handler called> (kgdb)=20 [that last copy/pasted from core.txt.1]. I noticed nothing peculiar while (briefly) running r347896 (built yesterday evening & smoke-tested: booted to multi-user mode; wlan0 associated to the expected AP at the time; X11 (xdm) came up, and I was able to login, ssh to home -- the usual stuff). The above link should be functional (but slow -- residential ADSL); it has: albert(11.3-P)[8] ls -lT total 42849 -rw-r--r-- 1 david wheel 301534 May 18 05:18:26 2019 console_0.jpg -rw-r--r-- 1 david wheel 311923 May 18 05:18:26 2019 console_1.jpg -rw-r--r-- 1 david staff 156926 May 18 05:07:13 2019 core.txt.1 -rw-r--r-- 1 david staff 37080 May 18 05:07:13 2019 core.txt.1.gz -rw-r--r-- 1 david staff 56590336 May 18 05:23:15 2019 vmcore.1.gz albert(11.3-P)[9]=20 Peace, david --=20 David H. Wolfskill david@catwhisker.org One wonders just who benefits from Trump's trade war with China. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --00Xftji29zlN/ZGB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE4owz2QxMJyaxAefyQLJg+bY2PckFAlzf+/pfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUy OEMzM0Q5MEM0QzI3MjZCMTAxRTdGMjQwQjI2MEY5QjYzNjNEQzkACgkQQLJg+bY2 PckxTQf+N8gWDxcB53SMJhubhQlj+7dvDhxN7ucBMpGjTZqnd9LEjJmCRrbmBYtu KiHQEAZkydGB8Uk3rXeRTHxwlqN+yqHKvTrBpHmtwq5EArKBWiyX6scQQR+wY+Mf 9ZC8SezGT3lDbW+OF8eNbt6kIa4uypEJ7/c3wqU8LWdhOBwJFhqm7kfX+a7iXbOG II5tucqGY1sPx+gsq+iB1jrHBAGxfD3HHGi8S1EJv17ET+8jhnzDprtj7VDZE63w Uzq/oNe1rT7VXXpGyWniG9Jbl0cJGQBYfOyDmlGaH5b/vnPE/aVURS/+IwIaQDMA srb556TYkjtmMvnhUV091tcExwx9rg== =lURI -----END PGP SIGNATURE----- --00Xftji29zlN/ZGB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190518123506.GX79998>