BT Homehub 5A drops 5Ghz Wifi- need help with logread

Installing and Using OpenWrt
1

Hi,

Could I get some help interpreting these error messages please and whether they're related?
I'm going to try the newer firmware but wanted to check I understood what's happening first. Way out of my depth here but willing to learn.

Symptom:
5Gz wireless stops working (can't detect it from various machines). It's a remote site used once a week so I'm not 100% sure if there's some pattern to it dropping but I think days
Is there something I can run on the router to find out when it happends
Only a reboot seems to solve it (rather than restarting wireless in gui)

Info:
Model: BT Home Hub 5A
Architecture: xRX200 rev 1.2
Firmware Version: OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.228.31946-f64b152)
Kernel Version: 4.9.120

Possible causes/ solutions:
Upgrade firmware: use ath10k-ct
Jumping Channel - how to diagnose? Channel 36
Similar problem, different errors:No answer

Logread

Mon Jun  3 10:46:38 2019 kern.warn kernel: [195311.966586] ath10k_pci 0000:02:00.0: failed to send pdev bss chan info request
Mon Jun  3 10:46:41 2019 kern.warn kernel: [195315.038497] ath10k_pci 0000:02:00.0: failed to set beacon mode for vdev 0: -11
Mon Jun  3 10:46:44 2019 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Mon Jun  3 10:46:44 2019 kern.warn kernel: [195318.110441] ath10k_pci 0000:02:00.0: failed to set dtim period for vdev 0: -11
Mon Jun  3 10:46:47 2019 kern.warn kernel: [195321.182345] ath10k_pci 0000:02:00.0: failed to recalculate rts/cts prot for vdev 0: -11
Mon Jun  3 10:46:51 2019 kern.warn kernel: [195324.254257] ath10k_pci 0000:02:00.0: failed to set cts protection for vdev 0: -11
Mon Jun  3 10:46:54 2019 kern.warn kernel: [195327.326210] ath10k_pci 0000:02:00.0: failed to set preamble for vdev 0: -11
Mon Jun  3 10:47:03 2019 kern.warn kernel: [195336.541911] ath10k_pci 0000:02:00.0: failed to send pdev bss chan info request
Mon Jun  3 10:47:06 2019 kern.warn kernel: [195339.613869] ath10k_pci 0000:02:00.0: failed to set beacon mode for vdev 0: -11
Mon Jun  3 10:47:09 2019 kern.warn kernel: [195342.685744] ath10k_pci 0000:02:00.0: failed to set dtim period for vdev 0: -11
Mon Jun  3 10:47:12 2019 kern.warn kernel: [195345.757659] ath10k_pci 0000:02:00.0: failed to recalculate rts/cts prot for vdev 0: -11
Mon Jun  3 10:47:15 2019 kern.warn kernel: [195348.829559] ath10k_pci 0000:02:00.0: failed to set cts protection for vdev 0: -11
Mon Jun  3 10:47:18 2019 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5

Edit: formatting logs

2

First you should upgrade to 18.06.2. During that time ath10k was developed considerably. Trunk builds could also be tried but I don't recommend that for a remote location.

Channel 36 is a non-DFS channel, it should not "jump".

If there is a wifi STA that is supposed to be connected continuously, you could use the watchcat package to initiate a reboot if it fails to ping that station, (presumably due to a wifi driver crash).

2 Likes
3

Thanks mk24

I've done the upgrade so will see how it goes.

I'm slightly hampered by a misbehaving switch that needs to be manually rebooted (only sometime) when the router is - that's next on the list. But it's a good plan as I had it cron rebooting until that switch problem reared it's head. Thank you.

Our of interest, are you using one of these? Is the wireless going down just one of those things I need to accept.
Does it sound right that it requireda full reboot, rather than restarting the wireless?