Date: Wed, 11 Apr 2018 13:02:28 -0400 From: Mark Johnston <markj@FreeBSD.org> To: David Wolfskill <david@catwhisker.org>, current@freebsd.org Cc: shurd@FreeBSD.org Subject: Re: panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/net/iflib.c:3716 Message-ID: <20180411170228.GB43015@raichu> In-Reply-To: <20180411113958.GE1134@albert.catwhisker.org> References: <20180411113958.GE1134@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 11, 2018 at 04:39:58AM -0700, David Wolfskill wrote: > This was running: > > FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #156 r332399M/332400:1200061: Wed Apr 11 04:17:45 PDT 2018 root@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 > > during boot, after updating from: > > FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #155 r332354M/332357:1200061: Tue Apr 10 04:00:41 PDT 2018 root@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 > > (My build machine, which uses an re((4) NIC, did not encounter the issue.) > > It appears that r332389 is implicated. I'm seeing this too, under bhyve with e1000 emulation. Reverting r332389 fixes the problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180411170228.GB43015>