Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#2650 - r7800 19.07-rc2 unable to change channel for AC #7531

Open
openwrt-bot opened this issue Dec 3, 2019 · 5 comments
Open

FS#2650 - r7800 19.07-rc2 unable to change channel for AC #7531

openwrt-bot opened this issue Dec 3, 2019 · 5 comments
Labels
flyspray release/19.07

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented Dec 3, 2019

kaxa:

  • Device problem occurs on - Linux r7800 4.14.156 #0 SMP Sat Nov 30 15:52:33 2019 armv7l GNU/Linux
  • Software versions of OpenWrt/LEDE release - 19.07-rc2

in Luci when change channel number change actually never gets committed, when do manually in /etc/config/wireless and then reboot router comes up with 5GHz network disabled, after changing back to default channel 36 5GHz network is usable again.

please provide steps to collect log

in dmesg only:

(wlan0) entered blocking state (wlan0) entered disabled state
@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Dec 8, 2019

adrianschmutzler:

Is regulatory domain set (correctly)?

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Dec 9, 2019

kaxa:

default settings:

root@r7800:~# iw reg get
global
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 71000 @ 2160), (N/A, 40), (N/A)

phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 71000 @ 2160), (N/A, 40), (N/A)

phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 71000 @ 2160), (N/A, 40), (N/A)

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Dec 9, 2019

pepe2k:

@vadim please be more specific and at least provide what channel number and HT settings are you trying to use - not all combinations are possible and correct.

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Dec 9, 2019

kaxa:

all default setting:
mode - AC
channel - 36
HT - 80MHz
are working just fine.

when I channel change in luci change get rollbacked after shoort wireless blackout.

this was found in dmesg during such change in luci:

[529385.947125] device wlan0 left promiscuous mode
[529385.947344] br-lan: port 2(wlan0) entered disabled state
[529386.039002] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[529386.039133] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[529386.045081] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[529392.481779] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
[529392.481813] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
[529392.563672] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
[529392.564519] ath10k_pci 0000:01:00.0: wmi print 'free: 81784 iram: 23220 sram: 14440'
[529392.917985] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[529392.918315] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[529392.931400] br-lan: port 2(wlan0) entered blocking state
[529392.934181] br-lan: port 2(wlan0) entered disabled state
[529392.939791] device wlan0 entered promiscuous mode
[529392.986891] device wlan0 left promiscuous mode
[529392.987142] br-lan: port 2(wlan0) entered disabled state
[529393.067758] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[529409.513363] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
[529409.513397] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
[529409.595257] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
[529409.596122] ath10k_pci 0000:01:00.0: wmi print 'free: 81784 iram: 23220 sram: 14440'
[529409.949858] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[529409.950158] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[529409.963198] br-lan: port 2(wlan0) entered blocking state
[529409.966053] br-lan: port 2(wlan0) entered disabled state
[529409.971646] device wlan0 entered promiscuous mode
[529410.016992] device wlan0 left promiscuous mode
[529410.017253] br-lan: port 2(wlan0) entered disabled state
[529410.097743] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[529422.376453] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
[529422.376486] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
[529422.458424] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
[529422.459281] ath10k_pci 0000:01:00.0: wmi print 'free: 81784 iram: 23220 sram: 14440'
[529422.827011] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[529422.827300] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[529422.844188] br-lan: port 2(wlan0) entered blocking state
[529422.844245] br-lan: port 2(wlan0) entered disabled state
[529422.849178] device wlan0 entered promiscuous mode
[529423.509679] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[529423.510037] br-lan: port 2(wlan0) entered blocking state
[529423.515135] br-lan: port 2(wlan0) entered forwarding state

If /etc/config/wireless is edited manually and router rebooted then AC wireless gets disabled.

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Jan 13, 2020

bjonglez:

This indeed looks like a regulatory / DFS issue.

Please select the right country, and tell us which channel you try to use.

If you try to use a DFS channel, it's normal that it gets disabled on boot.

@aparcar aparcar added the release/19.07 label Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray release/19.07
Projects
None yet
Development

No branches or pull requests

2 participants