Bug 193512 - ath0: bb hang detected (0x1), resetting for AR9287
Summary: ath0: bb hang detected (0x1), resetting for AR9287
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: CURRENT
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-wireless (Nobody)
URL:
Keywords:
Depends on:
Blocks: 277512
  Show dependency treegraph
 
Reported: 2014-09-10 09:41 UTC by Artyom
Modified: 2024-03-05 20:14 UTC (History)
7 users (show)

See Also:


Attachments
ath0 got stuck log (93.31 KB, text/plain)
2022-02-26 11:17 UTC, Robert Clausecker
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Artyom 2014-09-10 09:41:00 UTC
Sometime I receive this message on one of access point:
ath0: bb hang detected (0x1), resetting
After that connection restored only if I turn off wifi by hard button and turn on again.

ath0: <Atheros 9287> mem 0xe0500000-0xe050ffff irq 18 at device 0.0 on pci10
ath0: [HT] enabling HT modes
ath0: [HT] enabling short-GI in 20MHz mode
ath0: [HT] 1 stream STBC receive enabled
ath0: [HT] 1 stream STBC transmit enabled
ath0: [HT] 2 RX streams; 2 TX streams
ath0: AR9287 mac 384.2 RF5133 phy 15.15
ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0
Comment 1 Bane Ivosev 2014-12-02 16:33:21 UTC
i also have the same problem on fujitsu lifebook e751 notebook.

ath0@pci0:10:0:0:       class=0x028000 card=0x158f10cf chip=0x002e168c rev=0x01 hdr=0x00
    vendor     = 'Atheros Communications Inc.'
    device     = 'AR9287 Wireless Network Adapter (PCI-Express)'
    class      = network
Comment 2 Bane Ivosev 2014-12-02 16:36:54 UTC
i forgot .... 10.1-release.
Comment 3 heikki 2018-11-25 17:56:02 UTC
This also happens on Acer Aspire One, Intel Atom N280, Atheros 9285.

i386, 11.2-RELEASE (freebsd-update few days ago).
Comment 4 iasen.kostov 2019-09-20 15:49:03 UTC
Same here
FreeBSD 12.0-RELEASE-p10 GENERIC  amd64

Sep 20 18:30:51 HeadBanG kernel: ath0: bb hang detected (0x4), resetting
Sep 20 18:31:20 HeadBanG syslogd: last message repeated 13 times
Sep 20 18:33:22 HeadBanG syslogd: last message repeated 80 times
Sep 20 18:43:22 HeadBanG syslogd: last message repeated 514 times

ath0: <Atheros 9285> mem 0xd4700000-0xd470ffff irq 19 at device 0.0 on pci5
[ath] AR9285E_20 detected; using XE TX gain tables
[ath] AR9285 Main LNA config: LNA1
[ath] AR9285 Alt LNA config: LNA2
[ath] LNA diversity disabled, Diversity disabled
ath0: [HT] enabling HT modes
ath0: [HT] 1 stream STBC receive enabled
ath0: [HT] 1 RX streams; 1 TX streams
ath0: AR9285 mac 192.2 RF5133 phy 14.0
ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0
Comment 5 Robert Clausecker freebsd_committer freebsd_triage 2022-02-22 00:22:44 UTC
I'm also affected by this issue.
Comment 6 Bjoern A. Zeeb freebsd_committer freebsd_triage 2022-02-22 08:28:14 UTC
Has anyone been able to confirm this on CURRENT (14) or on a stable/13 (or at least 13.0-RELEASE)?
Comment 7 Robert Clausecker freebsd_committer freebsd_triage 2022-02-22 09:08:57 UTC
(In reply to Bjoern A. Zeeb from comment #6)

It happens to me on FreeBSD 13.0-RELEASE-p4.  The affected device is

ath0@pci0:3:0:0:	class=0x028000 rev=0x01 hdr=0x00 vendor=0x168c device=0x002a subvendor=0x103c subdevice=0x3041
    vendor     = 'Qualcomm Atheros'
    device     = 'AR928X Wireless Network Adapter (PCI-Express)'
    class      = network

I some times get a lot of these:

ath0: bb hang detected (0x4), resetting
ath0: bb hang detected (0x4), resetting
ath0: bb hang detected (0x4), resetting

or stuff like this:

ath0: ath_rate_tx_complete: ts_rate=11 ts_finaltsi=0, final_rix=0
ath0: bad series0 hwrate 0xb, tries 1 ts_status 0x0
ath0: ath_rate_tx_complete: ts_rate=11 ts_finaltsi=0, final_rix=0
ath0: bad series0 hwrate 0xb, tries 1 ts_status 0x0
wlan0: link state changed to DOWN
wlan0: link state changed to UP
ath0: ath_rate_tx_complete: ts_rate=27 ts_finaltsi=0, final_rix=0
ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0
ath0: ath_rate_tx_complete: ts_rate=27 ts_finaltsi=0, final_rix=0
ath0: bad series0 hwrate 0x1b, tries 1 ts_status 0x0

The connection usually comes back after a minute or so.
Comment 8 Bjoern A. Zeeb freebsd_committer freebsd_triage 2022-02-24 21:22:11 UTC
I had a very quick glance at ath; can you add:

wlandebug_wlan0="+rate"

to your /etc/rc.conf ?  That should add some extra logging which might be helpful for looking into this.
Comment 9 Robert Clausecker freebsd_committer freebsd_triage 2022-02-26 11:17:22 UTC
Created attachment 232117 [details]
ath0 got stuck log

See attached file for a dmesg log of this phenomenon happening.

One other thing I forgot to mention is that on my system, I have to put the system into suspend and then wake it back up for WLAN to work.  Kind of strange.
Comment 10 Nuno Teixeira freebsd_committer freebsd_triage 2022-10-01 18:47:28 UTC
(In reply to Bjoern A. Zeeb from comment #6)

same on main-n258315-42dc8696df5
---
ath0@pci0:2:0:0:        class=0x028000 rev=0x01 hdr=0x00 vendor=0x168c device=0x002b subvendor=0x105b subdevice=0xe017
    vendor     = 'Qualcomm Atheros'
    device     = 'AR9285 Wireless Network Adapter (PCI-Express)'
    class      = network
---
Comment 11 bermudi 2024-02-29 18:33:06 UTC
I can report same issue on an old Toshiba NB200 using FreeBSD-14.0-i386

`ath0: bb hang detected (0x1), resetting` every couple of minutes - connection seems fine.

sometimes the system boots and ath0 seems unresponsive. No message when that happens.

```
ath0@pci0:3:0:0:        class=0x028000 rev=0x01 hdr=0x00 vendor=0x168c device=0x002b subvendor=0x144f subdevice=0x7159
    vendor     = 'Qualcomm Atheros'
    device     = 'AR9285 Wireless Network Adapter (PCI-Express)'
    class      = network
```