misc/163759: ath(4) "stops working" in hostap mode
Nathan Lay
nsl03 at my.fsu.edu
Mon Jan 2 01:00:24 UTC 2012
>Number: 163759
>Category: misc
>Synopsis: ath(4) "stops working" in hostap mode
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Jan 02 01:00:23 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Nathan Lay
>Release: 9-STABLE
>Organization:
>Environment:
FreeBSD RADIO.LOCAL 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #3: Sat Dec 31 20:52:54 EST 2011 nslay at RADIO.LOCAL:/usr/obj/usr/src/sys/RADIO amd64
>Description:
At an arbitrary time, ath "stops working" while in hostap mode. It vanishes with respect to other wireless clients and it cannot be fixed by bringing the interface up/down or destroying and recreating the interface. Tcpdump confirms that the access point really is no longer visible. Reloading the driver, however, can remedy the problem. The problem device is given below:
ath0: <Atheros 5416> mem 0xfe9f0000-0xfe9fffff irq 16 at device 0.0 on pci1
ath0: AR5418 mac 12.10 RF2133 phy 8.1
Here is how it is configured and used:
create_args_wlan0="wlanmode hostap -bgscan"
ifconfig_wlan0="channel 5:ht/40 ssid Lamp up"
autobridge_bridge0="wlan0 lan0"
It also sits behind pf.
The kernel is not compiled with ATH_ENABLE_11N.
It is also worth mentioning that the aforementioned configuration worked without problems in 8.x.
Other suspicious behavior:
athstats before the problem:
bexmit bmiss
4410 0
10 0
10 0
9 0
athstats after the problem:
bexmit bmiss
52014 0
5 0
4 0
5 0
dmesg frequently reports beacon misses before and after the problem:
ath0: stuck beacon; resetting (bmiss count 4)
Here is the output of athstats after the problem:
352222 data frames received
317354 data frames transmit
113 tx frames with an alternate rate
11861 long on-chip tx retries
755 tx failed 'cuz too many retries
691 stuck beacon conditions
1M current transmit rate
5537 tx frames with no ack marked
309725 tx frames with short preamble
11773 rx failed 'cuz of bad CRC
3053 rx failed 'cuz of PHY err
3053 CCK restart
52218 beacons transmitted
181 periodic calibrations
-0/+0 TDMA slot adjust (usecs, smoothed)
58 rssi of last ack
31 avg recv rssi
-96 rx noise floor
2092 tx frames through raw api
241 cabq frames transmitted
97 cabq xmit overflowed beacon interval
1 spur immunity level
54 ANI increased spur immunity
53 ANI decrease spur immunity
693 ANI enabled OFDM weak signal detect
693 ANI disabled CCK weak signal threshold
13947724 cumulative OFDM phy error count
13047675 cumulative CCK phy error count
902 ANI forced listen time to zero
11860 missing ACK's
21408 bad FCS
24 average rssi (beacons only)
Antenna profile:
[0] tx 316491 rx 23814
[1] tx 0 rx 328408
>How-To-Repeat:
No known way to repeat the problem. However, the following:
options ATH_DEBUG
options AH_DEBUG
options ATH_DIAGAPI
seem to make the problem happen more frequently.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list