Date: Sun, 28 Apr 2019 21:29:29 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 200319] Bridge+CARP crashes/freezes Message-ID: <bug-200319-7501-zmy80VP6SC@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-200319-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-200319-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=3D200319 Oleg Sharoyko <osharoiko@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |osharoiko@gmail.com --- Comment #15 from Oleg Sharoyko <osharoiko@gmail.com> --- Hello, I can reliably reproduce this problem on three systems running 12.0 and 11.= 2. To reproduce it one needs to send a non negligible amount of traffic towards the system under test so I cannot provide the exact script but I hope my instructions are clear and I=E2=80=99m happy to provide as much details as = I can. To reproduce a problem configure the system in the following way: ifconfig ue0 up # Or any other ethernet interface that you have in the syst= em ifconfig bridge0 create ifconfig bridge0 addm ue0 ifconfig bridge0 inet 192.168.0.111/24 vhid 1 advskew 100 pass mekmitasdigo= at pkg install iperf3 iperf3 -s >From some other machine send traffic towards system under test: iperf3 -c 192.168.0.111 -u -t 120 -Z -b 100m=20 In all of my tests this resulted in immediate (within 2 seconds) lockup of = the network stack on the target system. Excluding bridge interface from the pic= ture and configuring CARP directly on top of ue0 (also tested with rl0) eliminat= es the problem. I will try to look more into this problem but I'm not familiar with locking= in the kernel. Are there any documents/exmaples/kernel options which can help = find where deadlock happens? Also, https://reviews.freebsd.org/D3133 had no attention for over a year. B= ut looks like it has been applied in pfSense and works there (https://redmine.pfsense.org/issues/8056) is that something woth looking in= to? Kind regards, Oleg --=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-200319-7501-zmy80VP6SC>