From owner-freebsd-net@freebsd.org  Thu Sep  7 07:01:16 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9CE98E0C11C
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Thu,  7 Sep 2017 07:01:16 +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 mx1.freebsd.org (Postfix) with ESMTPS id 761E881599
 for <freebsd-net@FreeBSD.org>; Thu,  7 Sep 2017 07:01:16 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v8771GxJ059376
 for <freebsd-net@FreeBSD.org>; Thu, 7 Sep 2017 07:01:16 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 221845] bridge0 causes kernel panic on BBB using usb wifi in
 hostap mode (RT3071)
Date: Thu, 07 Sep 2017 07:01:16 +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: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: russ.haley@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-221845-2472-pF0nELhTmZ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221845-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-221845-2472@https.bugs.freebsd.org/bugzilla/>
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.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 07:01:16 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221845

--- Comment #3 from Russell Haley <russ.haley@gmail.com> ---
I've been following the code through and wound up at sys/arm/ti/cpsw/if_cps=
w.c.
cpsw_intr_rx is defined on line 1554. The function uses a macro called
CPSW_RX_LOCK which is defined on line 349. The macro contains an assert on a
transmit lock (tx.lock). I theorise the statement on line 350 is causing my
exception? I also wonder if the lock being held between lines 1561 and 1570=
 is
causing the delay in the bridge interface that is causing the original post=
ers'
slow throughput. Is it necessary to hold the lock until after the cpsw_writ=
e_4
on line 1569 or could it be performed outside the lock?

--=20
You are receiving this mail because:
You are the assignee for the bug.=