[ath9k-devel] Ath9k in funky state after adding 130 STA interfaces.

[Ben Greear <greearb@candelatech.com>]

This on wireless-testing from Friday, plus a few debugfs patches I posted
recently.

I was running two STA just fine, and then tried to add 128 more.

After that, nothing will authenticate (timed out).

I don't see any obvious errors in the logs, other than DMA
failing to stop after 10ms, but this debugfs information looks
quite suspect:

[root at atom lanforge]# cat /debug/ath9k/phy0/wiphy
primary: phy0 (ACTIVE chan=0 ht=0)
addr: ef:be:ad:de:ef:be
addrmask: ef:be:ad:de:ef:be
rfilt: 0xdeadbfef UCAST MCAST BCAST CONTROL PROM PROBEREQ PHYERR MYBEACON COMP_BAR PHYRADAR MCAST_BCAST_ALL

It seems some sort of race..if I add and configure these interfaces manually,
it seems to work.  It may also be a problem with bringing up the interface
before applying the wifi settings, as that was the last change I made to my
user-space application that manages these interfaces.

I briefly saw the deadbeef when configuring manually..but the single wlan0 seemed
to be associated OK, and when I added another station, the values went back to
normal.

Any ideas what this might indicate?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com