Re: ath0: ath_reset: unable to reset hardware; hal status 3

Henrik Brix Andersen wrote:
Hi all,

I have noticed a problem when using ath(4) as an 802.11g access point
with hostapd(8) and WPA2-PSK CCMP.

The following problem seems to only occur when a Microsoft Windows XP
STA connects to the AP in 802.11g mode, my FreeeBSD STAs doesn't seem
to trigger this:

Jan 28 11:21:07 osgiliath kernel: ath0: stuck beacon; resetting (bmiss count 4)
Jan 28 11:21:07 osgiliath kernel: ath0: ath_reset: unable to reset hardware; hal status 3
Jan 28 11:21:25 osgiliath kernel: ath0: device timeout
Jan 28 11:21:25 osgiliath kernel: ath0: stuck beacon; resetting (bmiss count 4)
Jan 28 11:21:25 osgiliath kernel: ath0: ath_reset: unable to reset hardware; hal status 3
Jan 28 11:21:37 osgiliath kernel: ath0: device timeout
Jan 28 11:21:38 osgiliath kernel: ath0: stuck beacon; resetting (bmiss count 4)
Jan 28 11:21:38 osgiliath kernel: ath0: ath_reset: unable to reset hardware; hal status 3
Jan 28 11:21:46 osgiliath kernel: ath0: device timeout

This is FreeBSD RELENG_6 (nanoBSD) as of yesterday with the new
ath_hal(4) running on a Soekris net4801-50:

ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath0: <Atheros 5212> mem 0xa0010000-0xa001ffff irq 11 at device 14.0 on pci0
ath0: Ethernet address: 00:05:4e:42:e8:7c
ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3

The same problem occured with version 0.9.17.2 of ath_hal(4).

I have increased the RX/TX buffers in ath(4) as shown in this snippet
from my kernel configuration:

device ath
device ath_hal
device ath_rate_sample

options ATH_RXBUF=80
options ATH_TXBUF=200

The only way I can get the AP running again after the above messages
to syslog is to reboot it. The problem doesn't seem to occur in
802.11b mode nor in 802.11g mode with only FreeBSD STAs.

Any help in debugging this will be appreciated.

I take it you tried ifconfig'ing the interface down and up?

The output of athstats at the point where things are wedged might be
useful. Also verify if only tx is wedged (e.g. athstats 1 will show you
if you're receiving frames).

The fact that the card cannot be reset seems to imply the mac is somehow
locked up. I vaguely recall some h/w issues like this on older cards
(and you are using a rather old card) but nothing that wasn't handled by
doing a reset operation. Best suggestion I can make is to use a
different model card.

Sam
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"