From owner-freebsd-wireless@FreeBSD.ORG  Fri Mar 20 05:15:30 2015
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E8D53CB
 for <freebsd-wireless@FreeBSD.org>; Fri, 20 Mar 2015 05:15:30 +0000 (UTC)
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 CE44AAE
 for <freebsd-wireless@FreeBSD.org>; Fri, 20 Mar 2015 05:15:30 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2K5FUbH058033
 for <freebsd-wireless@FreeBSD.org>; Fri, 20 Mar 2015 05:15:30 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-wireless@FreeBSD.org
Subject: [Bug 198298] [ath] ath_edma_rxbuf_alloc()/ath_edma_rxfifo_alloc()
 causes system lockup when RX buffers are exausted
Date: Fri, 20 Mar 2015 05:15:31 +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: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: adrian@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-198298-21060-D2HcIw7t5m@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198298-21060@https.bugs.freebsd.org/bugzilla/>
References: <bug-198298-21060@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Mar 2015 05:15:31 -0000

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

--- Comment #2 from Adrian Chadd <adrian@freebsd.org> ---
I don't know why it's locking up your system - maybe this condition is causing
an interrupt storm from ath(4) and I'm not handling it right.

The EDMA NICs try to be smart, and I'm tempted to rip out the smart bits and
replace it with not-smart bits:

* the interrupt handler pulls out completed descriptors, pushes in fresh ones,
and puts the completed descriptors into a pending queue
* .. and then schedules a taskqueue.

* Then when the RX taskqueue runs, it handles RX of each packet and returns
now-free descriptors to the hardware.

It's possible that something is making that taskqueue not run and the RX path
runs out of descriptors.

Now, as to why .. hm. I'd like to figure that out.

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