From owner-freebsd-net@freebsd.org Sun Apr 28 21:30:14 2019 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B265D158A833 for ; Sun, 28 Apr 2019 21:30:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 439BE7686F for ; Sun, 28 Apr 2019 21:30:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 04E12158A832; Sun, 28 Apr 2019 21:30:14 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5078158A831 for ; Sun, 28 Apr 2019 21:30:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 726857686D for ; Sun, 28 Apr 2019 21:30:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 99166125E9 for ; Sun, 28 Apr 2019 21:30:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x3SLUCK5029727 for ; Sun, 28 Apr 2019 21:30:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3SLUCQs029726 for net@FreeBSD.org; Sun, 28 Apr 2019 21:30:12 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 200319] Bridge+CARP crashes/freezes Date: Sun, 28 Apr 2019 21:29:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: osharoiko@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? mfc-stable12? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Apr 2019 21:30:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200319 Oleg Sharoyko changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |osharoiko@gmail.com --- Comment #15 from Oleg Sharoyko --- 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.=