Bug 215079 - ath(4) (Qualcomm AR9227) stuck beacon after running a while
Summary: ath(4) (Qualcomm AR9227) stuck beacon after running a while
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: 11.0-STABLE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-wireless (Nobody)
URL:
Keywords: crash, needs-qa
Depends on:
Blocks:
 
Reported: 2016-12-05 19:57 UTC by c.kworr
Modified: 2023-04-14 22:38 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description c.kworr 2016-12-05 19:57:24 UTC
Hello.

Dec  5 03:36:49 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:37:39 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:38:03 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:38:11 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:38:11 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:38:26 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:42:29 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)

hw.ath.bstuck: 4
hw.ath.txbuf_mgmt: 32
hw.ath.txbuf: 200
hw.ath.rxbuf: 40
hw.ath.anical: 100
hw.ath.resetcal: 1200
hw.ath.shortcal: 100
hw.ath.longcal: 30
wlan0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether c0:4a:00:eb:4c:17
        inet6 fe80::c24a:ff:feeb:4c17%wlan0 prefixlen 64 scopeid 0x4
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
        status: running
        ssid 42 channel 1 (2412 MHz 11g) bssid c0:4a:00:eb:4c:17
        regdomain 32924 country CN indoor ecm authmode OPEN -wps -tsn
        privacy OFF deftxkey UNDEF powersavemode OFF powersavesleep 100
        txpower 20 txpowmax 50.0 -dotd rtsthreshold 2346 fragthreshold 2346
        bmiss 7
        11a     ucast NONE    mgmt  6 Mb/s mcast  6 Mb/s maxretry 6
        11b     ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
        11g     ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
        turboA  ucast NONE    mgmt  6 Mb/s mcast  6 Mb/s maxretry 6
        turboG  ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
        sturbo  ucast NONE    mgmt  6 Mb/s mcast  6 Mb/s maxretry 6
        11na    ucast NONE    mgmt 12 MCS  mcast 12 MCS  maxretry 6
        11ng    ucast NONE    mgmt  2 MCS  mcast  2 MCS  maxretry 6
        half    ucast NONE    mgmt  3 Mb/s mcast  3 Mb/s maxretry 6
        quarter ucast NONE    mgmt  1 Mb/s mcast  1 Mb/s maxretry 6
        scanvalid 60 -bgscan bgscanintvl 300 bgscanidle 250
        roam:11a     rssi    7dBm rate 12 Mb/s
        roam:11b     rssi    7dBm rate  1 Mb/s
        roam:11g     rssi    7dBm rate  5 Mb/s
        roam:turboA  rssi    7dBm rate 12 Mb/s
        roam:turboG  rssi    7dBm rate 12 Mb/s
        roam:sturbo  rssi    7dBm rate 12 Mb/s
        roam:11na    rssi    7dBm  MCS  1
        roam:11ng    rssi    7dBm  MCS  1
        roam:half    rssi    7dBm rate  6 Mb/s
        roam:quarter rssi    7dBm rate  3 Mb/s
        -pureg protmode CTS -ht -htcompat -ampdu ampdulimit 64k
        ampdudensity 8 -amsdu -shortgi htprotmode RTSCTS -puren smps -rifs
        -stbc wme burst -dwds -hidessid apbridge dtimperiod 1 doth -dfs inact
        bintval 100
        AC_BE cwmin  4 cwmax  6 aifs  3 txopLimit   0 -acm ack
              cwmin  4 cwmax 10 aifs  3 txopLimit   0 -acm
        AC_BK cwmin  4 cwmax 10 aifs  7 txopLimit   0 -acm ack
              cwmin  4 cwmax 10 aifs  7 txopLimit   0 -acm
        AC_VI cwmin  3 cwmax  4 aifs  1 txopLimit  94 -acm ack
              cwmin  3 cwmax  4 aifs  2 txopLimit  94 -acm
        AC_VO cwmin  2 cwmax  3 aifs  1 txopLimit  47 -acm ack
              cwmin  2 cwmax  3 aifs  2 txopLimit  47 -acm
        groups: wlan

Would be happy to provide more info/testing if needed.
Comment 1 Adrian Chadd freebsd_committer freebsd_triage 2016-12-05 21:04:49 UTC
Try:

sysctl dev.ath.0.hal.force_full_reset=1

and then see if it gets stuck less.



-adrian
Comment 2 c.kworr 2016-12-06 04:59:36 UTC
Added to /etc/sysctl.conf and rebooted (just in case). Not that much difference yet.

Dec  6 06:54:45 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:54:50 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:55:02 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:55:07 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:55:09 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:55:17 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:55:18 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:55:45 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:55:47 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:55:48 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:56:09 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:56:13 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:56:17 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  6 06:56:25 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Comment 3 Adrian Chadd freebsd_committer freebsd_triage 2016-12-06 05:02:08 UTC
It'll happen from time to time depending upon RF conditions. As long as it doesn't go deaf over time then we're okay.
Comment 4 c.kworr 2017-03-31 16:45:15 UTC
Oh, and a panic:

Unread portion of the kernel message buffer:
ath0: stuck beacon; resetting (bmiss count 4)
panic: ath_legacy_tx_dma_restart: Q3: called with PUTRUNNING=1

cpuid = 1
KDB: stack backtrace:
#0 0xffffffff803a7507 at kdb_backtrace+0x67
#1 0xffffffff80368d26 at vpanic+0x186
#2 0xffffffff80368b96 at kassert_panic+0x126
#3 0xffffffff816e7f02 at ath_legacy_tx_dma_restart+0xb2
#4 0xffffffff816d8366 at ath_reset+0x4a6
#5 0xffffffff816d398c at ath_bstuck_proc+0x9c
#6 0xffffffff803b8c1c at taskqueue_run_locked+0x13c
#7 0xffffffff803b9958 at taskqueue_thread_loop+0x88
#8 0xffffffff80332ef4 at fork_exit+0x84
#9 0xffffffff805de1ee at fork_trampoline+0xe
Comment 5 sledz 2022-03-09 20:27:45 UTC
Is there anybody working on this problem?

There are several other issues that appear to describe the same problem, e.g.: #179709, #178491, #171598, #155100

An it still exists. I'm currently watching it on FreeBSD 13.0-STABLE amd64.
Comment 6 sledz 2022-03-09 20:29:50 UTC
Here are the right references: bug #179709, bug #178491, bug #171598, bug #155100
Comment 7 Graham Perrin freebsd_committer freebsd_triage 2022-10-17 12:18:16 UTC
Keyword: 

    crash

– in lieu of summary line prefix: 

    [panic]

* bulk change for the keyword
* summary lines may be edited manually (not in bulk). 

Keyword descriptions and search interface: 

    <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>
Comment 8 Graham Perrin freebsd_committer freebsd_triage 2022-12-29 13:43:10 UTC
Triage: 

* status and summary line tags edited according to 
  <https://wiki.freebsd.org/Bugzilla>

* links – can freebsd-wireless@ tell whether there's any duplication?