Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Apr 2008 22:06:16 +0200
From:      Henrik Brix Andersen <brix@FreeBSD.org>
To:        freebsd-current@freebsd.org
Subject:   Re: HEADSUP: 802.11 vap support merged
Message-ID:  <20080422200616.GA44541@tirith.brixandersen.dk>
In-Reply-To: <480D6667.4020509@errno.com>
References:  <480D6667.4020509@errno.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--zhXaljGHf11kAtnf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Apr 21, 2008 at 09:15:35PM -0700, Sam Leffler wrote:
> 1. remove wlan_scan_* references (config files, loader.conf, etc.)
> 2. update your rc.conf files with something like
>
> vaps_ath0="wlan0"
> ifconfig_wlan0="WPA DHCP"

Great - Thank you for working on this :)

However, after having upgraded my ThinkPad X60s to todays -current and
performed the above changes, this appears in my dmesg at boot time:

ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath0: <Atheros 5212> mem 0xedf00000-0xedf0ffff irq 17 at device 0.0 on pci3
ath0: [ITHREAD]
ath0: WARNING: using obsoleted if_watchdog interface
ath0: mac 10.3 phy 6.1 radio 10.2
...
wlan0: Ethernet address: 00:19:7d:8c:0f:75
ath0: ath_chan_set: unable to reset channel 13 (2472 Mhz, flags 0x680 hal flags 0xc0), hal status 12
ath0: ath_chan_set: unable to reset channel 34 (5170 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 38 (5190 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 42 (5210 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 46 (5230 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 12 (2467 Mhz, flags 0x680 hal flags 0xc0), hal status 12
ath0: ath_chan_set: unable to reset channel 14 (2484 Mhz, flags 0x2a0 hal flags 0xa0), hal status 12
ath0: ath_chan_set: unable to reset channel 100 (5500 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 104 (5520 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 108 (5540 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 112 (5560 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 116 (5580 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 120 (5600 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 124 (5620 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 128 (5640 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 132 (5660 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 136 (5680 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_chan_set: unable to reset channel 140 (5700 Mhz, flags 0x340 hal flags 0x140), hal status 12
ath0: ath_reset: unable to reset hardware; hal status 12
...

The above list of channels which can not be reset re-appers
periodically, I assume in connection with background scan. They also
appear during regular scans, e.g. when wpa_supplicant scans for a
suitable AP. Whenever the messages appears, the connection to the
currently associated AP dies (although it still appears to be
associated according to ifconfig).

The periodic messages disappears when bgscan is disabled on wlan0.

Below is the list of channels supported by my card:

# ifconfig wlan0 list chan
Channel   1 : 2412  Mhz 11g          Channel  48 : 5240* Mhz 11a
Channel   2 : 2417  Mhz 11g          Channel  52 : 5260* Mhz 11a
Channel   3 : 2422  Mhz 11g          Channel  56 : 5280* Mhz 11a
Channel   4 : 2427  Mhz 11g          Channel  60 : 5300* Mhz 11a
Channel   5 : 2432  Mhz 11g          Channel  64 : 5320* Mhz 11a
Channel   6 : 2437  Mhz 11g          Channel 100 : 5500* Mhz 11a
Channel   7 : 2442  Mhz 11g          Channel 104 : 5520* Mhz 11a
Channel   8 : 2447  Mhz 11g          Channel 108 : 5540* Mhz 11a
Channel   9 : 2452  Mhz 11g          Channel 112 : 5560* Mhz 11a
Channel  10 : 2457  Mhz 11g          Channel 116 : 5580* Mhz 11a
Channel  11 : 2462  Mhz 11g          Channel 120 : 5600* Mhz 11a
Channel  12 : 2467* Mhz 11g          Channel 124 : 5620* Mhz 11a
Channel  13 : 2472* Mhz 11g          Channel 128 : 5640* Mhz 11a
Channel  14 : 2484* Mhz 11b          Channel 132 : 5660* Mhz 11a
Channel  34 : 5170* Mhz 11a          Channel 136 : 5680* Mhz 11a
Channel  36 : 5180* Mhz 11a          Channel 140 : 5700* Mhz 11a
Channel  38 : 5190* Mhz 11a          Channel 149 : 5745* Mhz 11a
Channel  40 : 5200* Mhz 11a          Channel 153 : 5765* Mhz 11a
Channel  42 : 5210* Mhz 11a          Channel 157 : 5785* Mhz 11a
Channel  44 : 5220* Mhz 11a          Channel 161 : 5805* Mhz 11a
Channel  46 : 5230* Mhz 11a          Channel 165 : 5825* Mhz 11a

Brix
--
Henrik Brix Andersen <brix@FreeBSD.org>

--zhXaljGHf11kAtnf
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (FreeBSD)
Comment: GnuPG signed

iEYEARECAAYFAkgORTgACgkQv+Q4flTiePjqEgCfcJtAQloWfsCg8sAoPzQeXw9z
w6MAmQFkdacwLV5aul34nbXwPH/DBusJ
=5Ct0
-----END PGP SIGNATURE-----

--zhXaljGHf11kAtnf--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080422200616.GA44541>