Date: Wed, 08 Jan 2020 09:43:24 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 219901] [Panic] [if_bridge] panic when destroying interface on bridge over time Message-ID: <bug-219901-7501-HDIaNNPbyW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219901-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-219901-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219901 O. Hartmann <ohartmann@walstatt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ohartmann@walstatt.org --- Comment #3 from O. Hartmann <ohartmann@walstatt.org> --- The problem is also still persistent in CURRENT (13.0-CURRENT FreeBSD 13.0-CURRENT #26 r356437: Tue Jan 7 07:19:34 CET 2020 amd64) and it can be reliably triggered by stopping vnet jails, where the epair is member of a bridge device. Also, these PRs seem to be related to this almost two years old bug: PR 238= 326 and probably this one year old bug PR 234985. Is anybody investigating this issue? It is also affecting 12.1-RELENG and 12-STABLE systems and it seems the larger the number of jails hosted is, the more likely is the failure . In our case, we crash one large server with a couple of Intel 350T2 NICs and ~ 10 -12 jails one EVERY shutdown of the sys= tem or stopping jails via "service jail stop" and it takes one or two attempts = to crash the box by randomly select a jail and stop it via "service jail stop $name", $name is the jailname to be stopped. The only secure way to reboot the server is to issue "reboot". --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219901-7501-HDIaNNPbyW>