On Sun, Jun 10, 2007 at 10:36:48PM -0400, Allen Briggs wrote:
> On Sat, Jun 09, 2007 at 02:43:52PM -0500, David Young wrote:
> > Sorry, my bad.  Looks like I introduced a new bug as I repaired another.
> 
> I tried the patch, and it does seem to help some, but I still
> see significant timeouts with the driver:
> Jun 10 21:34:04 caer /netbsd: ath0: device timeout
> Jun 10 21:35:32 caer ntpd[163]: kernel time sync status change 2001
> Jun 10 21:40:59 caer /netbsd: ath0: device timeout
> Jun 10 21:46:28 caer /netbsd: ath0: device timeout
> Jun 10 21:52:44 caer last message repeated 9 times
> Jun 10 22:06:01 caer last message repeated 7 times
> Jun 10 22:13:05 caer last message repeated 7 times
> Jun 10 22:25:25 caer last message repeated 12 times
> 
> And the interactive sessions would work OK for a bit and then hang.

Could you have exhausted mbufs?  Is OACTIVE set?

Does ath0 share the PCI bus with any other device?  Does it share an
interrupt?  Does pcictl(8) indicate any PCI bus errors on the ath0?
When the net stalls, is ath0 still interrupting at all?  Does it
interrupt non-stop?

If you enable a bunch of net80211 and ath debugging, does any event
correlate with the stalls?

Dave

-- 
David Young             OJC Technologies
dyoung@ojctech.com      Urbana, IL * (217) 278-3933 ext 24