Date: Wed, 29 Nov 2006 08:57:01 -0800 From: Sam Leffler <sam@errno.com> To: Lamont Granquist <lamont@scriptkiddie.org> Cc: freebsd-stable@freebsd.org Subject: Re: ath0 issue Message-ID: <456DBBDD.8020808@errno.com> In-Reply-To: <Pine.GSO.4.60.0611282144040.6950@sploit.scriptkiddie.org> References: <Pine.GSO.4.60.0611112035320.27030@sploit.scriptkiddie.org> <Pine.GSO.4.60.0611121126390.29168@sploit.scriptkiddie.org> <45578B48.1090704@errno.com> <Pine.GSO.4.60.0611121455590.29754@sploit.scriptkiddie.org> <455BD2BF.3050802@errno.com> <Pine.GSO.4.60.0611282038060.6773@sploit.scriptkiddie.org> <Pine.GSO.4.60.0611282144040.6950@sploit.scriptkiddie.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?456DBBDD.8020808>