https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
Hiroki Sato changed:
What|Removed |Added
Assignee|freebsd-net@FreeBSD.org |h...@freebsd.org
--
You are receivi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
Hiroki Sato changed:
What|Removed |Added
Status|New |In Progress
--- Comment #12 from Hir
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
--- Comment #11 from Hiroki Sato ---
Created attachment 151999
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=151999&action=edit
a patch to fix this panic
This patch should fix the panic. As Bjoern pointed out, ifnet_departure
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
Bjoern A. Zeeb changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
Bjoern A. Zeeb changed:
What|Removed |Added
CC||b...@freebsd.org
--- Comment #9 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
--- Comment #8 from Craig Rodrigues ---
Herbert provided a traceback from his kernel panic. This looks like the source
of the problem:
panic: mtx_lock() of destroyed mutex @
/usr/src/sys/modules/if_bridge/../../net/if_bridge.c:1814
It lo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
--- Comment #7 from Craig Rodrigues ---
Created attachment 151803
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=151803&action=edit
dump2.txt
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
--- Comment #6 from Craig Rodrigues ---
Herbert found by creating VNET jails and then stopping them, he could reproduce
the problem. Here are the steps he used to reproduce the problem:
/etc/rc.conf:
hostname="beastie.home.lan"
ifconfig_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
Craig Rodrigues changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
