Date: Fri, 9 Jun 2017 05:57:15 -0700 From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Subject: Panic @r319733: "mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/sys_socket.c:305" Message-ID: <20170609125715.GP1180@albert.catwhisker.org>
next in thread | raw e-mail | index | archive | help
--55BQxs/tzKPczcTk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Build machine updated from r319689 to r319733 OK; smoke test was uneventful. Laptop updated similarly, but smoke test was a little more "interesting". Turns out that laptop gets to multi-user mode OK... if I disable starting xdm, devd, and hald. But then, issuing "service hald onestart" generates the panic in question -- at r319733. At r319689, xdm & friends worked fine. I have placed copies of the /var/crash/*.6 files in <http://www.catwhisker.org/~david/FreeBSD/head/hald/>; -- along with gzipped copies, as well. (It's residential DSL in the US, so there's not a huge amount of bandwidth.) I get the impression that something (ini hald) was trying to use the freebsd11 version of stat(), and Something Bad happened: panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/sys_socket.c:305 cpuid =3D 7 time =3D 1497011454 KDB: stack backtrace: db_trace_self_wrapper() at 0xffffffff803a461b =3D db_trace_self_wrapper+0x2= b/frame 0xfffffe0c268ff600 vpanic() at 0xffffffff80a1f94c =3D vpanic+0x19c/frame 0xfffffe0c268ff680 kassert_panic() at 0xffffffff80a1f7a6 =3D kassert_panic+0x126/frame 0xfffff= e0c268ff6f0 __mtx_lock_flags() at 0xffffffff809fedfe =3D __mtx_lock_flags+0x14e/frame 0= xfffffe0c268ff740 soo_stat() at 0xffffffff80a8f8f0 =3D soo_stat+0x60/frame 0xfffffe0c268ff770 kern_fstat() at 0xffffffff809cb378 =3D kern_fstat+0xa8/frame 0xfffffe0c268f= f7c0 freebsd11_fstat() at 0xffffffff809cb28d =3D freebsd11_fstat+0x1d/frame 0xff= fffe0c268ff930 amd64_syscall() at 0xffffffff80e31fb4 =3D amd64_syscall+0x5a4/frame 0xfffff= e0c268ffab0 Xfast_syscall() at 0xffffffff80e12eab =3D Xfast_syscall+0xfb/frame 0xfffffe= 0c268ffab0 --- syscall (189, FreeBSD ELF64, freebsd11_fstat), rip =3D 0x801b4973a, rsp= =3D 0x7fffffffe988, rbp =3D 0x7fffffffea20 --- KDB: enter: panic Note: the hald in question was built under FreeBSD stable/11 (as are all my ports); I noted the existence of, and installed, ports/misc/compat11s before (re-)creating the crash. (And yes, the ports that have kernel modules get the kernel modules rebuilt on head every time I rebuild the kernel on head.) With the caveat that I actually use the laptop in my day-to-day activities, I'm happy to try various combinations of patching, testing, and reporting results. Peace, david --=20 David H. Wolfskill david@catwhisker.org Looking forward to telling Mr. Trump: "You're fired!" See http://www.catwhisker.org/~david/publickey.gpg for my public key. --55BQxs/tzKPczcTk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZOpsrXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XkoEH/RCqu5LTiwnqD6BDaQMnpf1x oAL+KcqsY6D5Nv0cGXapRW9BjxEv5DoiQLcU07HZDYaf2X/F25AzaRw88vzQJ4cQ bW/l8auPa12F5HBPvVhohcsEOn/qKcuHTZ+f2mCPtVzSkj4MGKQDoTT71mz3S7vt 4B3JuN5ph/iha4A4rwzBaCkL/UwQV9yUQd9Oy2MyAqEVbihOx0K44LfYPhIMFgM2 3Y03uMHrRIwMlOLs+q5B6Sef3bKklvnZszon4qJs+yBWSXSpRI+r0Sza2apYQvgz QB66yXsYP6JwkCG2PFD1BkAx0wP+ajxMNwflyKmNWLbYs5o1oaqSC919EIqSfzw= =zH80 -----END PGP SIGNATURE----- --55BQxs/tzKPczcTk--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170609125715.GP1180>