From owner-freebsd-net@FreeBSD.ORG  Wed Sep  2 12:07:12 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 825D91065679
	for <freebsd-net@freebsd.org>; Wed,  2 Sep 2009 12:07:12 +0000 (UTC)
	(envelope-from stef-list@memberwebs.com)
Received: from mail.npubs.com (mail.npubs.com [74.82.45.72])
	by mx1.freebsd.org (Postfix) with ESMTP id 764D68FC19
	for <freebsd-net@freebsd.org>; Wed,  2 Sep 2009 12:07:11 +0000 (UTC)
Resent-Message-Id: <none>
From: Stef Walter <stef-list@memberwebs.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: "freebsd-net@FreeBSD.org" <freebsd-net@freebsd.org>
References: <20090820042016.C8F913039754@mx.npubs.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Resent-Date: Wed,  2 Sep 2009 12:07:12 +0000 (UTC)
Resent-From: stef-list@memberwebs.com
X-Mailman-Approved-At: Wed, 02 Sep 2009 12:20:16 +0000
Subject: Re: ath0: ath_rx_proc: no mbuf!
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: stef@memberwebs.com
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
Date: Wed, 02 Sep 2009 12:07:12 -0000
X-List-Received-Date: Wed, 02 Sep 2009 12:07:12 -0000

Stef Walter wrote:
> A short while ago (perhaps due to a change in traffic), every few hours,
> the wireless interface becomes unresponsive, and I started seeing
> thousands of lines like this in:
> 
> ath0: ath_rx_proc: no mbuf!
> ath0: ath_rx_proc: no mbuf!
> ath0: ath_rx_proc: no mbuf!
> ath0: ath_rx_proc: no mbuf!
> ath0: ath_rx_proc: no mbuf!

For the record. It was a hardware problem.

Cheers,

Stef