Date: Fri, 9 Jun 2017 08:23:55 -0700 From: David Wolfskill <david@catwhisker.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: current@freebsd.org, glebius@freebsd.org Subject: Re: Panic @r319733: "mtx_lock() of spin mutex (null) @ /usr/src/sys/kern/sys_socket.c:305" Message-ID: <20170609152355.GZ1180@albert.catwhisker.org> In-Reply-To: <20170609135517.GA2088@kib.kiev.ua> References: <20170609125715.GP1180@albert.catwhisker.org> <20170609135517.GA2088@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
--NnUDYhz5zoqA1Riz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 09, 2017 at 04:55:17PM +0300, Konstantin Belousov wrote: > On Fri, Jun 09, 2017 at 05:57:15AM -0700, David Wolfskill wrote: > > Build machine updated from r319689 to r319733 OK; smoke test was > > uneventful. > >=20 > > Laptop updated similarly, but smoke test was a little more "interesting= ". > >=20 > > 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. > >=20 > > 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.) > >=20 > > I get the impression that something (ini hald) was trying to use > > the freebsd11 version of stat(), and Something Bad happened: > >=20 > > 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= +0x2b/frame 0xfffffe0c268ff600 > > vpanic() at 0xffffffff80a1f94c =3D vpanic+0x19c/frame 0xfffffe0c268ff680 > > kassert_panic() at 0xffffffff80a1f7a6 =3D kassert_panic+0x126/frame 0xf= ffffe0c268ff6f0 > > __mtx_lock_flags() at 0xffffffff809fedfe =3D __mtx_lock_flags+0x14e/fra= me 0xfffffe0c268ff740 > > soo_stat() at 0xffffffff80a8f8f0 =3D soo_stat+0x60/frame 0xfffffe0c268f= f770 > > The main suspect is r319722. > Try reverting it or downgrading before it (the later might be simple due > to the patch size). > .... It was easy enough for me to use "svn diff -c r319722" & "svn patch --reverse-diff" to effectively revert r319722. I re-ran the build after that, and a subsequent reboot allowed me to "sudo service hald onestart" (which whined a bit about dbus not being enabled but started it anyway), after which I was able to start xdm -- so that seems to have been successful. Perhaps I'll chat with Gleb a bit later today. :-) (Our cubes are adjacent.) Thanks, Konstantin! :-) 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. --NnUDYhz5zoqA1Riz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZOr2LXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XlnkH/3kcm1elZsj/DQXCIwSXFEpb zbKbIUnqnuI+HFKf5c57SiCqduu4d5W/n3idGElOsquT10wSZzwTCYiHKSG/ytj8 jO51X1cfA+7LIJGSQCiFnHjbyYw6awo6Hvlh7i4wO6NQmEwMYffBgDvHt6zHSfd+ 2br24fBBzWihn+XtJd3HU50n394vyz/TKLl/9Idj1lhQMSPC5pJxxofnUKQGpQVF qeFoDVuwEcH157qc8BV/QygHThooay2/WhPzTmCiPsfXgGUPAHxpGvnvOUaOo/VU RrRC6YKenSohNRYmKULoRwuEdpqDh5kiYqRfuOfoLjgUg6MUNp9Lj9Fzq5PFOKA= =PoRa -----END PGP SIGNATURE----- --NnUDYhz5zoqA1Riz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170609152355.GZ1180>