From adrian.chadd@gmail.com  Mon Jul 30 00:40:41 2012
Return-Path: <adrian.chadd@gmail.com>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id DD8B4106566B;
	Mon, 30 Jul 2012 00:40:41 +0000 (UTC)
	(envelope-from adrian.chadd@gmail.com)
Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54])
	by mx1.freebsd.org (Postfix) with ESMTP id AAE6C8FC0A;
	Mon, 30 Jul 2012 00:40:41 +0000 (UTC)
Received: by pbbro2 with SMTP id ro2so9286403pbb.13
        for <multiple recipients>; Sun, 29 Jul 2012 17:40:41 -0700 (PDT)
Received: by 10.68.218.7 with SMTP id pc7mr30581839pbc.88.1343608841484; Sun,
 29 Jul 2012 17:40:41 -0700 (PDT)
Received: by 10.68.66.136 with HTTP; Sun, 29 Jul 2012 17:40:41 -0700 (PDT)
Message-Id: <CAJ-Vmon45n4EtD4T2Esru+Ver-LWEXC=CnrZCfsxPKBQ6JUe9w@mail.gmail.com>
Date: Sun, 29 Jul 2012 17:40:41 -0700
From: Adrian Chadd <adrian@freebsd.org>
Sender: adrian.chadd@gmail.com
To: "Lev A. Serebryakov" <lev@freebsd.org>
Cc: FreeBSD-gnats-submit@freebsd.org
In-Reply-To: <20120729104830.5CD8D4AC32@onlyone.friendlyhosting.spb.ru>
Subject: Re: [ath] Atheros 9220 device timeouts.
References: <20120729104830.5CD8D4AC32@onlyone.friendlyhosting.spb.ru>

>Number:         170265
>Category:       kern
>Synopsis:       Re: [ath] Atheros 9220 device timeouts.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-wireless
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jul 30 00:50:10 UTC 2012
>Closed-Date:    Mon Jul 30 02:11:41 UTC 2012
>Last-Modified:  Mon Jul 30 02:11:41 UTC 2012
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 On 29 July 2012 03:48, Lev A. Serebryakov <lev@freebsd.org> wrote:
 
 > Jul 29 00:01:32 gateway kernel: ath0: stuck beacon; resetting (bmiss count 4)
 > Jul 29 00:02:07 gateway kernel: ath0: device timeout
 > Jul 29 00:52:30 gateway kernel: ath0: device timeout
 > Jul 29 01:43:21 gateway kernel: ath0: device timeout
 > Jul 29 01:54:30 gateway kernel: ath0: device timeout
 > Jul 29 02:04:55 gateway kernel: ath0: device timeout
 > Jul 29 02:29:00 gateway kernel: ath0: device timeout
 > Jul 29 03:00:52 gateway kernel: ath0: device timeout
 > Jul 29 03:04:49 gateway kernel: ath0: device timeout
 > Jul 29 03:09:55 gateway kernel: ath0: device timeout
 > Jul 29 03:10:52 gateway kernel: ath0: device timeout
 
 Hm, I bet this is because the TX ath_buf pool is exhausted. And it's
 exhausted because..
 
 > Jul 29 03:39:54 gateway kernel: ath0: ath_tx_tid_drain: node 0xc4a30000: bf=0xc34f6690: addbaw=0, dobaw=0, seqno=398, retry=0
 > Jul 29 03:39:54 gateway kernel: ath0: ath_tx_tid_drain: node 0xc4a30000: bf=0xc34f6690: tid txq_depth=491 hwq_depth=0, bar_wait=0
 > Jul 29 03:39:54 gateway kernel: ath0: ath_tx_tid_drain: node 0xc4a30000: tid 0: txq_depth=1, txq_aggr_depth=0, sched=0, paused=-1, hwq_depth=0, incomp=0, baw_head=15, baw_tail=15 txa_start=398, ni_txseqs=906
 
 If I had to guess, your client went away / to sleep (but didn't tell
 the AP about it) so the software queue gets filled up. That exhausts
 the mbufs.
 
 The "device timeout" here is a side-effect. The allocation is failing
 but the watchdog is getting tickled. It shouldn't be.
 
 
 
 Adrian
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: linimon 
State-Changed-When: Mon Jul 30 02:10:53 UTC 2012 
State-Changed-Why:  
Misfiled followup to kern/170254; content migrated. 


Responsible-Changed-From-To: gnats-admin->freebsd-wireless 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Mon Jul 30 02:10:53 UTC 2012 
Responsible-Changed-Why:  

http://www.freebsd.org/cgi/query-pr.cgi?pr=170265 
>Unformatted:
