https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
Hiroki Sato h...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-net@FreeBSD.org |h...@freebsd.org
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
--- Comment #11 from Hiroki Sato h...@freebsd.org ---
Created attachment 151999
-- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=151999action=edit
a patch to fix this panic
This patch should fix the panic. As Bjoern pointed out,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
Hiroki Sato h...@freebsd.org changed:
What|Removed |Added
Status|New |In Progress
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
Bjoern A. Zeeb b...@freebsd.org changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
Bjoern A. Zeeb b...@freebsd.org changed:
What|Removed |Added
CC||b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
Craig Rodrigues rodr...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
--- Comment #6 from Craig Rodrigues rodr...@freebsd.org ---
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:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
--- Comment #7 from Craig Rodrigues rodr...@freebsd.org ---
Created attachment 151803
-- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=151803action=edit
dump2.txt
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
--- Comment #8 from Craig Rodrigues rodr...@freebsd.org ---
Herbert provided a traceback from his kernel panic. This looks like the source
of the problem:
panic: mtx_lock() of destroyed mutex @
