From owner-freebsd-stable@FreeBSD.ORG Wed Nov 29 17:05:00 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 B007416A4CE for ; Wed, 29 Nov 2006 17:05:00 +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 1970A43DC8 for ; Wed, 29 Nov 2006 16:57:09 +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 kATGv1Co020111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Nov 2006 08:57:02 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <456DBBDD.8020808@errno.com> Date: Wed, 29 Nov 2006 08:57:01 -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:05:00 -0000 Lamont Granquist wrote: > > and ath_intr() is getting called all the time but status & HAL_INT_TX > isn't true so the task isn't getting enqueued. this is a 5 second stutter: > > Nov 28 21:39:48 warez kernel: ath_tx_proc_q0123: 1 > Nov 28 21:39:48 warez kernel: ath_intr: status 0x1010000 > Nov 28 21:39:48 warez kernel: ath_intr: status 0x1000009 > Nov 28 21:39:48 warez kernel: ath_intr: status 0x1010000 > Nov 28 21:39:48 warez kernel: ath_intr: status 0x1000009 > Nov 28 21:39:48 warez kernel: ath_intr: status 0x1010000 <...stuff truncated...> Using timestamps from syslog isn't going to give you any useful information since the data may be delayed getting to syslogd. Is there some reason you are not just sniffing the air? Assuming packets are being deferred because the medium is busy you might see a reason. Otherwise it appears (though it's impossible to tell from what you've shown so far) that the packets are handed to the h/w in a timely fashion. Sam