panic: Lock PFil shared rmlock not read locked @ /usr/src/sys/net/pfil.c:116 prior to r326363

[Ryan Stone]

Please update to r326376 or later.  That will likely fix you issue.

On Sun, Dec 3, 2017 at 6:49 PM, Dave Cottlehuber <dch at skunkwerks.at> wrote:
> I'm seeing this repeatedly in the last ~ 2 weeks,  present in r326363
> and typically panics 1-15m post boot since this weekend's update.  I'm
> currently bisecting my way back; it looks like its not in r325755, but I
> can't be sure for a few more hours.
>
> https://s3.amazonaws.com/uploads.hipchat.com/8784/2508819/MGim1y8pQt1o1xK/IMG_2698.JPG
>
> # uname -a
> FreeBSD wintermute.skunkwerks.at 12.0-CURRENT FreeBSD 12.0-CURRENT #2
> r326363+fcb3a5a8a12d(master): Wed Nov 29 11:37:17 UTC 2017
> root at wintermute:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
>
> # dmesg
>
> https://gist.github.com/dch/68dd6f8d44dd76c558908e71dc3e1f87#file-dmesg-log
> + other logs in same gist
>
> Suggestions how to get from X to debugger would help, as would setting
> up serial console over ipmi - this is a supermicro motherboard.
>
> A+
> Dave
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"