In message <4355AEE3.2000205@errno.com>, Sam Leffler writes:
>
>Again, anectdotal reports are not helpful.  You haven't even identified 
>what hardware you have or what version of the driver you're using. 
>There are known issues with "phantom beacon miss" interrupts on 5212 
>parts operating in station mode that I have workarounds for.  These 
>typically occur during periods of heavy traffic but have also been 
>reported at other times.  When you see a link state transition check 
>what athstats reports and see if the bmiss count is going up.  In lieu 
>of that turn on state transition debugging in the net80211 layer to see 
>what's going.
>

I've posted quite detailed reports in the past, including everything I 
could possibly learn.  I'm limited because, as has been noted several 
times in this discussion, NetBSD doesn't have the commands you're 
looking for.  There is no athstats command, nor wlandebug nor 
80211stats.  Frankly, until your posts I didn't even know they existed 
elsewhere; I don't have time to play much with other operating systems, 
especially on my laptop.

For the record -- my laptop is presently running -current as of 
22 September.  That's the version that's been reasonably happy in my 
house lately.  On the other hand, it's almost certainly the version 
that couldn't acquire a signal at Union Station in Washington, on 9/26.
The machine is a Thinkpad T42 with an IBM a/b/g card; here's the dmesg 
output:

ath0 at pci2 dev 2 function 0
ath0: interrupting at irq 11
ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3

I leave on a trip tomorrow; if the opportunity presents itself, I'll try
a kernel from up-to-the-minute source with David Young's patch.

If there's anything I can tell you, please let me know.

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb