Turris Omnia loses 5GHz WiFI hourly or so

Installing and Using OpenWrt
#1

I am using the latest 19.07 with a CT driver. I have not seen a kernel crash yet, but I do see messages like below at the time when 5GHz goes down. Is there a remedy?

Wed Jul 10 16:49:53 2019 kern.warn kernel: [ 5218.418071] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 3, skipped old beacon                  
Wed Jul 10 16:49:53 2019 kern.warn kernel: [ 5218.443665] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon                     
Wed Jul 10 16:49:53 2019 kern.warn kernel: [ 5218.469266] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 1, skipped old beacon                                          
Wed Jul 10 16:49:53 2019 kern.warn kernel: [ 5218.494868] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 2, skipped old beacon                                           
Wed Jul 10 16:49:53 2019 kern.warn kernel: [ 5218.520466] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 3, skipped old beacon 
Wed Jul 10 16:49:53 2019 kern.warn kernel: [ 5218.536817] ath10k_pci 0000:02:00.0: wmi command 36954 timeout, restarting hardware                                               
Wed Jul 10 16:49:53 2019 kern.warn kernel: [ 5218.546069] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon                     
Wed Jul 10 16:49:54 2019 kern.warn kernel: [ 5218.571666] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 1, skipped old beacon                                          
Wed Jul 10 16:49:54 2019 kern.warn kernel: [ 5218.597261] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 2, skipped old beacon                                           
Wed Jul 10 16:49:54 2019 kern.warn kernel: [ 5218.622866] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 3, skipped old beacon 
Wed Jul 10 16:49:54 2019 kern.warn kernel: [ 5218.648458] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon                  
Wed Jul 10 16:49:54 2019 kern.warn kernel: [ 5218.674059] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 1, skipped old beacon  
Wed Jul 10 16:49:54 2019 kern.warn kernel: [ 5218.699663] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 2, skipped old beacon

Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.377189] ath10k_pci 0000:02:00.0: No VIF found for vdev 3                   
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.382880] ath10k_pci 0000:02:00.0: no vif for vdev_id 3 found                                       
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.398607] ath10k_pci 0000:02:00.0: No VIF found for vdev 3                                                             
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.404305] ath10k_pci 0000:02:00.0: received addba event for invalid vdev_id: 3                                          
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.411746] ath10k_pci 0000:02:00.0: No VIF found for vdev 3                    
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.417418] ath10k_pci 0000:02:00.0: received addba event for invalid vdev_id: 3 
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.424843] ath10k_pci 0000:02:00.0: No VIF found for vdev 3                      
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.430517] ath10k_pci 0000:02:00.0: received addba event for invalid vdev_id: 3
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.439154] ath10k_pci 0000:02:00.0: No VIF found for vdev 3                     
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.444838] ath10k_pci 0000:02:00.0: received addba event for invalid vdev_id: 3
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.452277] ath10k_pci 0000:02:00.0: No VIF found for vdev 3                                     
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.457959] ath10k_pci 0000:02:00.0: received addba event for invalid vdev_id: 3                      
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.466077] ath10k_pci 0000:02:00.0: No VIF found for vdev 3                    
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.471797] ath10k_pci 0000:02:00.0: received addba event for invalid vdev_id: 3                      
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.479588] ath10k_pci 0000:02:00.0: No VIF found for vdev 3                    
Wed Jul 10 17:02:02 2019 kern.warn kernel: [ 5947.485282] ath10k_pci 0000:02:00.0: no vif for vdev_id 3 found                              
Wed Jul 10 17:02:03 2019 kern.warn kernel: [ 5947.786785] ath10k_pci 0000:02:00.0: No VIF found for vdev 2                    
Wed Jul 10 17:02:03 2019 kern.warn kernel: [ 5947.792479] ath10k_pci 0000:02:00.0: no vif for vdev_id 2 found                 
Wed Jul 10 17:02:03 2019 kern.warn kernel: [ 5947.818390] ath10k_pci 0000:02:00.0: No VIF found for vdev 2                     
Wed Jul 10 17:02:03 2019 kern.warn kernel: [ 5947.824085] ath10k_pci 0000:02:00.0: received addba event for invalid vdev_id: 2              
Wed Jul 10 17:02:03 2019 kern.warn kernel: [ 5947.832445] ath10k_pci 0000:02:00.0: No VIF found for vdev 2                    
Wed Jul 10 17:02:03 2019 kern.warn kernel: [ 5947.838148] ath10k_pci 0000:02:00.0: received addba event for invalid vdev_id: 2                                                  
Wed Jul 10 17:02:03 2019 kern.warn kernel: [ 5947.991563] ath10k_pci 0000:02:00.0: No VIF found for vdev 1                                        
Wed Jul 10 17:02:03 2019 kern.warn kernel: [ 5947.997243] ath10k_pci 0000:02:00.0: no vif for vdev_id 1 found
#2

Recent ML thread, and there is a pending CT push in xback staging tree.

#3

Do you happen to know if this will be committed to 19.07? The discussion seems to be evolving around the master branch.

#4

Did you try adjusting driver options as outlined here https://www.candelatech.com/ath10k-10.4.php#config ?

Alternatively might try ath10k-firmware-qca988x and kmod-ath10k instead to see whether it makes a difference.

#5

I only have a half a dozen active clients, so I do not need to adjust that. The other parameters I do not understand. I should not have to adjust anything for my kind of load.