Date: Thu, 15 Nov 2018 22:55:38 +0200 From: Volodymyr Kostyrko <arcade@b1t.name> To: wireless@FreeBSD.org Subject: Atheros 9220 - losing connectivity Message-ID: <421db909-9c41-15bf-5ee1-b91311185321@b1t.name>
next in thread | raw e-mail | index | archive | help
Hello.
I'm not quite sure what happens so I'll just dump here what I have in
mind so it would be easier to sort out later.
I upgraded from 11-STABLE to 12-STABLE and my card is now working in HT
mode. And that is nice. Currnently it's detected as:
ath0@pci0:4:5:0: class=0x028000 card=0x2093168c chip=0x0029168c
rev=0x01 hdr=0x00
vendor = 'Qualcomm Atheros'
device = 'AR922X Wireless Network Adapter'
class = network
ath0: <Atheros 9220> mem 0xfebf0000-0xfebfffff irq 20 at device 5.0 on pci4
ath0: [HT] enabling HT modes
ath0: [HT] 1 stream STBC receive enabled
ath0: [HT] 1 stream STBC transmit enabled
ath0: [HT] 2 RX streams; 2 TX streams
ath0: Enabling register serialisation
ath0: AR9220 mac 128.2 RF5133 phy 13.0
ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0
# ifconfig wlan1 list chan
Channel 1 : 2412 MHz 11g ht Channel 8 : 2447 MHz 11g ht
Channel 2 : 2417 MHz 11g ht Channel 9 : 2452 MHz 11g ht
Channel 3 : 2422 MHz 11g ht Channel 10 : 2457 MHz 11g ht
Channel 4 : 2427 MHz 11g ht Channel 11 : 2462 MHz 11g ht
Channel 5 : 2432 MHz 11g ht Channel 12 : 2467* MHz 11g ht
Channel 6 : 2437 MHz 11g ht Channel 13 : 2472* MHz 11g ht
Channel 7 : 2442 MHz 11g ht
Debug enabled:
dev.ath.0.hal.force_full_reset=1
dev.ath.0.hal.debug=1
Everyting I see in logs is:
Nov 15 19:45:54 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Nov 15 19:45:57 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Nov 15 19:46:04 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Though this happens all the time.
What changed after going to 12-STABLE:
1. HT works.
2. Devices are losing connection constantly.
Sometimes devices are getting back on the network by themself. Sometimes
this requires interface down/up. That's so fast so that tcp connections
are staying intact. But sometimes putting server interface down/up is
required so the others can talk to it. On the other host I see interface
trying different channels, then hitting correct one, waiting a little
and going back to trying other channels. On correct channel it shows
status: no carrier, just sits there longer.
It also looks like some devices have a good connection while others are
losing connection. There's one device that never gets off.
Thanks for any pointers.
--
Sphinx of black quartz judge my vow.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?421db909-9c41-15bf-5ee1-b91311185321>