Re: Panic _at_r319733: "mtx_lock() of spin mutex (null) _at_ /usr/src/sys/kern/sys_socket.c:305"

From: David Wolfskill <david_at_catwhisker.org>
Date: Fri, 9 Jun 2017 08:23:55 -0700
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.
> > 
> > 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) _at_ /usr/src/sys/kern/sys_socket.c:305
> > cpuid = 7
> > time = 1497011454
> > KDB: stack backtrace:
> > db_trace_self_wrapper() at 0xffffffff803a461b = db_trace_self_wrapper+0x2b/frame 0xfffffe0c268ff600
> > vpanic() at 0xffffffff80a1f94c = vpanic+0x19c/frame 0xfffffe0c268ff680
> > kassert_panic() at 0xffffffff80a1f7a6 = kassert_panic+0x126/frame 0xfffffe0c268ff6f0
> > __mtx_lock_flags() at 0xffffffff809fedfe = __mtx_lock_flags+0x14e/frame 0xfffffe0c268ff740
> > soo_stat() at 0xffffffff80a8f8f0 = soo_stat+0x60/frame 0xfffffe0c268ff770
>
> 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
-- 
David H. Wolfskill				david_at_catwhisker.org
Looking forward to telling Mr. Trump: "You're fired!"

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

Received on Fri Jun 09 2017 - 13:23:57 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:12 UTC