From owner-freebsd-stable@FreeBSD.ORG Wed Nov 29 17:01:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4BB8816A4CA for ; Wed, 29 Nov 2006 17:01:09 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7D8D43DAF for ; Wed, 29 Nov 2006 16:54:24 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id kATGrimG020085 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Nov 2006 08:53:47 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <456DBB18.3090603@errno.com> Date: Wed, 29 Nov 2006 08:53:44 -0800 From: Sam Leffler User-Agent: Thunderbird 1.5.0.7 (X11/20060920) MIME-Version: 1.0 To: Lamont Granquist References: <45578B48.1090704@errno.com> <455BD2BF.3050802@errno.com> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: ath0 issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2006 17:01:09 -0000 Lamont Granquist wrote: > > > On Wed, 15 Nov 2006, Sam Leffler wrote: >> Snapshots are rarely useful; try running athstats 1 and correlate what >> you see with pauses. Another possible reason for deferred operation is >> something else in the system blocking the taskq threads; that's a bit >> trickier to diagnose. > > I threw in some printf()'s in the beginning of ath_start() and > ath_tx_proc_q0123() and see this: > > Nov 28 20:27:41 warez kernel: ath_tx_proc_q0123: 1 > Nov 28 20:27:41 warez kernel: ath_start > Nov 28 20:27:41 warez kernel: ath_start > Nov 28 20:27:41 warez kernel: ath_tx_proc_q0123: 1 > Nov 28 20:27:41 warez kernel: ath_start > Nov 28 20:27:45 warez last message repeated 13 times > Nov 28 20:27:45 warez kernel: ath_tx_proc_q0123: 1 > Nov 28 20:27:45 warez kernel: ath_start > Nov 28 20:27:45 warez kernel: ath_tx_proc_q0123: 1 > Nov 28 20:27:45 warez kernel: ath_start > Nov 28 20:27:45 warez kernel: ath_start > > this was during a time where i was pinging across this interface so that > every second it should have been transmitting at least one packet. the > 4 second stutter there where ath_tx_proc_q0123 wasn't being called > correllates with actual stutters in packet transmission. > > if i understand this, that's the taskq associated with transmission? > > TASK_INIT(&sc->sc_txtask, 0, ath_tx_proc_q0123, sc); > > No, that's the task q that reaps completed tx descriptors. You can't infer anything about when packets were transmitted from this. Sam