Date: Mon, 20 Mar 2017 11:17:52 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217606] Bridge stops working after some days Message-ID: <bug-217606-2472-GIwoxQh2tA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217606-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-217606-2472@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=3D217606 Fabian Keil <fk@fabiankeil.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fk@fabiankeil.de --- Comment #13 from Fabian Keil <fk@fabiankeil.de> --- There's a uma-related regression in FreeBSD 11 that can result in somewhat similar symptoms. For details see #209680. You could check the vmstat -z output and try the patch: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209680#c2 which reverts some of the problematic commits (only in the tcp code, though). Apparently some of the other uma-consumers are affected as well: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209680#c10 and I'm wondering if if_bridge is one of them. You could try if it makes a difference if you let if_bridge set the UMA_ZONE_NOFREE flag and preallocate a couple of items. >From your report it isn't obvious to me that your problem is uma-related so if you have other leads you may want to investigate them first. --=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-217606-2472-GIwoxQh2tA>