OPNsense Forum

Archive => 16.7 Legacy Series => Topic started by: hirschferkel on December 08, 2016, 05:28:42 pm

Title: kernel: ath0: ath_chan_set: concurrent reset! Danger!
Post by: hirschferkel on December 08, 2016, 05:28:42 pm

After trying to change the 802.11 standard from b to na / g / ng the error message will be

Code: [Select]

7:08:34 kernel: ieee80211_new_state_locked: pending RUN -> SCAN transition lost
Dec 8 17:08:34 kernel: ath0_wlan1:
Dec 8 17:01:37 configd.py: [b8af2c4e-a6a6-4023-8153-204cdfc798a6] Reloading filter
Dec 8 17:01:36 configd.py: [5ad2a0b9-630c-4ba4-885f-5d8ffd6bedba] updating dyndns opt2
Dec 8 17:01:33 kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec 8 17:01:32 kernel: ath0: ath_chan_set: concurrent reset! Danger!
Dec 8 17:01:32 kernel: ath0: ath_reset_grablock: warning, recursive reset path!
Dec 8 17:01:32 kernel: ath0: ath_reset_grablock: didn't finish after 10 iterations
This is not repairable with the GUI and i have to reboot with an backup. What can be done?

best, hirschferkel

Title: Re: kernel: ath0: ath_chan_set: concurrent reset! Danger!
Post by: carepack on December 13, 2016, 10:24:32 am

Hi,
I'd similar problems and I've found something in the freebsd forum. I've tested the approach on pfsense and it looks more stable and reliable to me. Maybe it's an approach for opnsense too.

Create the file
/etc/rc.conf.local

with the following content:

Code: [Select]

ifconfig_ath0="ssid speedy.i mode 11g mediaopt hostap channel 2 -bgscan up"
Here is the link to the forum post:
https://forums.freebsd.org/threads/22112/

Maybe it's not exactly what you want, but it helped to get my wlan more stabe and get rid of the stuck kernel messages. At least, the number of message with stuck_beacon became less.

A feedback would be nice!

Title: Re: kernel: ath0: ath_chan_set: concurrent reset! Danger!
Post by: hirschferkel on December 20, 2016, 12:30:16 pm

I wrote to varia.store, where they sell the OPNsense routers and the answered, that they know about the issues with WLAN in the current 16.7 release (especially with virtual WLANs) and problems should be gone with 16.7.7. ... i will wait for that update and see what happens. Otherwise i will test your suggestion.

Best, hirschferkel

Title: Re: kernel: ath0: ath_chan_set: concurrent reset! Danger!
Post by: franco on December 20, 2016, 03:53:41 pm

Hi hirschferkel,

I don't know about 16.7.7. 17.1 is more likely. You could try the beta, ath works a lot better there. This has been confirmed already.

17.1 will be officially out end of January.


Cheers,
Franco