ath0: device timeout on 9.0-STABLE
Michal Vančo
mvanco at di-vision.sk
Wed Jan 25 08:13:29 UTC 2012
Hi,
thanks for your response.
Though there is one more thing. Is my adapter supposed to work in 5GHz band? I'm sure it works in windows and linux. Trying to switch to a different SSID (5GHz one) on the same AP, wlan0 stay unassociated (status: no carrier):
# ifconfig wlan0
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:19:7e:52:1c:c4
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier
ssid "XXX (5 GHz)" channel 36 (5180 MHz 11a)
regdomain ETSI2 country SK indoor ecm authmode WPA2/802.11i
privacy ON deftxkey UNDEF txpower 17 bmiss 7 mcastrate 6 mgmtrate 6
scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7
roam:rate 12 wme burst roaming MANUAL
# /usr/src/tools/tools/ath/athstats/athstats -i ath0
3245 data frames received
1102 data frames transmit
652 mib overflow interrupts
6M current transmit rate
116 rx failed 'cuz of bad CRC
46 rx failed 'cuz of PHY err
46 CCK restart
-0/+0 TDMA slot adjust (usecs, smoothed)
23 rssi of last ack
25 avg recv rssi
-96 rx noise floor
1102 tx frames through raw api
1 spur immunity level
1 first step level
14 ANI increased spur immunity
889 ANI enabled OFDM weak signal detect
889 ANI disabled CCK weak signal threshold
10 ANI increased first step level
180060 cumulative OFDM phy error count
1709 cumulative CCK phy error count
113 bad FCS
25 average rssi (beacons only)
32 average rssi (all rx'd frames)
23 average rssi (ACKs only)
Antenna profile:
[0] tx 1056 rx 200
[1] tx 0 rx 3045
With these messages in dmesg:
ar5212StopDmaReceive: dma failed to stop in 10ms
AR_CR=0x00000024
AR_DIAG_SW=0x42000020
ar5212StopDmaReceive: dma failed to stop in 10ms
AR_CR=0x00000024
AR_DIAG_SW=0x42000020
Michal
On 25.1.2012, at 8:52, Adrian Chadd wrote:
> Hi,
>
> The LED stuff may be a bit broken for 9.0. I'll try to fix it up and backport the GPIO and LED fixes.
>
>
> Adrian
>
> On 24 January 2012 23:51, Michal Vančo <mvanco at di-vision.sk> wrote:
> Adrian,
>
> believe or not … it simply started to work. I just left my thinkpad turned off during the night and now when I booted, almost everything works as expected:
>
> # ifconfig wlan0
> wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> ether 00:19:7e:52:1c:c4
> inet 192.168.0.17 netmask 0xffffff00 broadcast 192.168.0.255
> nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g
> status: associated
> ssid XXX channel 9 (2452 MHz 11g) bssid 10:9a:dd:88:2a:5d
> regdomain ETSI2 country SK indoor ecm authmode WPA2/802.11i
> privacy ON deftxkey UNDEF AES-CCM 3:128-bit txpower 30 bmiss 7
> scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7
> roam:rate 5 protmode CTS wme burst roaming MANUAL
>
> # /usr/src/tools/tools/ath/athstats/athstats -i ath0
> 4228 data frames received
> 818 data frames transmit
> 3 tx frames with an alternate rate
> 126 long on-chip tx retries
> 29480 mib overflow interrupts
> 24M current transmit rate
> 730 tx frames with short preamble
> 210 rx failed 'cuz of bad CRC
> 18 rx failed 'cuz of PHY err
> 18 CCK restart
> 10 periodic calibrations
> -0/+0 TDMA slot adjust (usecs, smoothed)
> 37 rssi of last ack
> 37 avg recv rssi
> -96 rx noise floor
> 90 tx frames through raw api
> 1 spur immunity level
> 1 first step level
> 9 ANI increased spur immunity
> 2 ANI decrease spur immunity
> 103 ANI enabled OFDM weak signal detect
> 4 ANI disabled OFDM weak signal detect
> 102 ANI disabled CCK weak signal threshold
> 3 ANI increased first step level
> 7392282 cumulative OFDM phy error count
> 34526 cumulative CCK phy error count
> 20 ANI forced listen time to zero
> 126 missing ACK's
> 291 bad FCS
> 2928 beacons received
> 39 average rssi (beacons only)
> 37 average rssi (all rx'd frames)
> 37 average rssi (ACKs only)
> Antenna profile:
> [0] tx 817 rx 65
> [1] tx 0 rx 4163
>
> I say "almost" because that small WiFi-LED doesn't blink as it should. Is there any way to fix this? I see these sysctls:
>
> dev.ath.0.softled: 0
> dev.ath.0.ledpin: 0
> dev.ath.0.ledon: 0
> dev.ath.0.ledidle: 2700
>
> but I'm lost with them :)
>
> regards
> michal
>
> On 25.1.2012, at 4:46, Adrian Chadd wrote:
>
> > Sure, can you please:
> >
> > * compile with the following options:
> >
> > options ATH_DEBUG
> > options AH_DEBUG
> > options ATH_DIAGAPI
> >
> > * compile /usr/src/sys/tools/tools/ath/athstats/
> >
> > * run athstats -i ath0 and email them to me + freebsd-wireless at freebsd.org
> >
> > Thanks!
> >
> >
> >
> > Adrian
> >
> >
> > On 24 January 2012 04:01, Michal Vančo <mvanco at di-vision.sk> wrote:
> > Hi there,
> >
> > I've installed 9.0-STABLE (also tried on 9.0-RELEASE) on my Thinkpad T60 and I'm not able to use WiFi. Kernel is GENERIC.
> >
> > pciconf -lv:
> > ath0 at pci0:3:0:0: class=0x028000 card=0x0033168c chip=0x0024168c rev=0x01 hdr=0x00
> > vendor = 'Atheros Communications Inc.'
> > device = 'AR5008 Wireless Network Adapter'
> > class = network
> >
> > relevant part of rc.conf:
> > wlans_ath0="wlan0"
> > create_args_wlan0="country SK"
> > ifconfig_wlan0="WPA DHCP"
> >
> > and wpa_supplicant.conf:
> > ctrl_interface=/var/run/wpa_supplicant
> >
> > network={
> > ssid="XXX"
> > psk="XXX"
> > }
> >
> > dmesg just fills with "ath0: device timeout" messages and wifi just doesn't work.
> >
> > any clue?
> >
> > regards
> > michal
> >
> > _______________________________________________
> > freebsd-stable at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
> >
>
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>
More information about the freebsd-wireless
mailing list