"Collecting data..." freezes on most pages (invalid wifi settings)

Installing and Using OpenWrt
1

Hi Lede-Community,

I have reinstalled LEDE on my Router and I have this strange behaviour.

On most pages (wireless, overview, realtime graphics) it only shows "Collecting data...". But there is no data coming.

However, it is working on the "Interface" page.

When I look into the syslog I have these errors multiple times:
[ 6304.857689] do_page_fault(): sending SIGSEGV to luci for invalid read access from xxxxxx
[ 6304.866145] epc = xxxxxx in libiwinfo.so[xxxxxx+19000]
[ 6304.871735] ra = xxxxxx in libiwinfo.so[xxxxxx+19000]

I have removed Luci completely and reinstalled it but without success.

Can anyone help?

Tom

2

Please provide device information.

3

TP-Link Archer C7 v2
LEDE Reboot 17.01.4 r3560-79f57e422d / LuCI lede-17.01 branch (git-17.290.79498-d3f0685)
Tried different browsers, os, devices, desktop, mobile

4

Well, that libiwinfo is the wifi information query libraryand it seems to crash. Not a LuCI component. But LuCI uses it to fetct wifi data.

Maybe you have an invalid wifi config or misbehaving wifi hardware.
You might try disabling wifi to see if that helps.

5

yes that did the trick.
With disabled wifi it's working.
I will now reconfigure the wifi interfaces and try again.

1 Like
6

Hi hnyman,

this is interesting: This bug comes back after I added the first wifi (2.4 or 5 ghz).

But without wifi setup I got this syslog error (but the frontend looks fine):

Wed Mar 28 23:05:31 2018 daemon.err uhttpd[7969]: /usr/lib/lua/luci/dispatcher.lua:460: Failed to execute call dispatcher target for entry '/admin/network/wireless_status'.
Wed Mar 28 23:05:31 2018 daemon.err uhttpd[7969]: The called action terminated with an exception:
Wed Mar 28 23:05:31 2018 daemon.err uhttpd[7969]: /usr/lib/lua/luci/controller/admin/network.lua:332: attempt to index local 'devs' (a nil value)
Wed Mar 28 23:05:31 2018 daemon.err uhttpd[7969]: stack traceback:
Wed Mar 28 23:05:31 2018 daemon.err uhttpd[7969]: 	[C]: in function 'assert'
Wed Mar 28 23:05:31 2018 daemon.err uhttpd[7969]: 	/usr/lib/lua/luci/dispatcher.lua:460: in function 'dispatch'
Wed Mar 28 23:05:31 2018 daemon.err uhttpd[7969]: 	/usr/lib/lua/luci/dispatcher.lua:141: in function </usr/lib/lua/luci/dispatcher.lua:140>
7

SSH in to the router and run the following...

cat /etc/config/wireless

Note: Make sure to obscure the "option key" value(s) in the wireless config results before posting.

While you're in SSH, run the following...

dmesg | grep 'warn\|err'

...to see if there are other issues going on.

8

cat /etc/config/wireless (not much in there. I deleted the networks)

config wifi-device 'radio0'
	option type 'mac80211'
	option hwmode '11a'
	option path 'pci0000:01/0000:01:00.0'
	option htmode 'VHT80'
	option country 'US'
	option channel '116' 
	
	config wifi-device 'radio1'
	option type 'mac80211'
	option channel '11'
	option hwmode '11g'
	option path 'platform/qca955x_wmac'
	option htmode 'HT20'
	option country 'US'

After 1st wifi setup, the following rows are added:

config wifi-iface 'default_radio0'
	option device 'radio0'
	option mode 'ap'
	option encryption 'psk2'
	option ssid 'xxxxxx'
	option key 'xxxxx'
	option network 'lan'

dmesg | grep 'warn|err'

[   46.486797] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
[   46.639456] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2
[   53.401765] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
9

This is a DFS channel that is reserved for radar.

https://www.wi-fi.org/knowledge-center/faq/what-is-dynamic-frequency-selection-dfs

You should be using channels 36-48 or 149-165.

Regarding the dmesg output, I have the same router and get the first and third messages consistently. There seems to be no impact on performance or stability.

10

Some general recommendations (some you are already using) -

2.4 Ghz -

Take channel selection off auto and use either channel 1, 6, or 11.

Set channel width to HT20.

Transmit power can be set up to 25 (in the US).

5 Ghz -

Change the channel to one in the higher range that doesn't require DFS, In the US, I recommend starting at 153.

Set channel width to VHT80 (if router is 802.11ac).

Transmit power can be set up to 30 (in the US).

Both -

Set encryption to WPA2-PSK and AES.

In helping you select a channel, I would also recommend Lizard Systems free WiFi Scanner to see what wireless traffic in your area looks like…

https://lizardsystems.com/wi-fi-scanner