ath0: ath_reset: unable to reset hardware; hal status 3
Kai Lockwood
kailockwood at gmail.com
Fri Feb 2 00:59:09 UTC 2007
Hello,
I am having the same type of trouble with a Dynex card. I mearly
receive 'ath0: Device timeout' on the main console screen.
> I take it you tried ifconfig'ing the interface down and up?
I have. The card does not appear to reset itself. While the card is up, it
just rotates across the chanels.
> The output of athstats at the point where things are wedged might be
> useful.
# /usr/local/bin/athstats
84874 data frames received
53228 data frames transmit
2228 tx frames with an alternate rate
15357 long on-chip tx retries
560 tx failed 'cuz too many retries
98877 mib overflow interrupts
11M current transmit rate
860 watchdog timeouts
85 beacon miss interrupts
612 tx management frames
1602 tx frames discarded prior to association
496 tx frames with no ack marked
21148 rx failed 'cuz of bad CRC
361 rx failed 'cuz of PHY err
96 OFDM restart
265 CCK restart
13422 periodic calibrations
10 rssi of last ack
-95 rx noise floor
18 phantom beacon misses
1 rx failed 'cuz frame too large
1 switched default/rx antenna
Antenna profile:
[1] tx 51420 rx 1829072
[2] tx 403 rx 116
#
> Also verify if only tx is wedged (e.g. athstats 1 will show you
> if you're receiving frames).
input output altrate short long xretry crcerr crypt phyerr rssi
rate
84874 53228 2228 0 15357 560 21148 0 361 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
0 0 0 0 0 0 0 0 0 0 11M
The above snippet repeats verbatium regardless of traffic.
> Best suggestion I can make is to use a
> different model card.
I can't. Is there someway to look into this issue deeper?
Thanks,
Kai Lockwood
More information about the freebsd-stable
mailing list