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#4046 - UniFI 6 LR 5 GHz doesn't always come up #9035

Open
openwrt-bot opened this issue Sep 19, 2021 · 12 comments
Open

FS#4046 - UniFI 6 LR 5 GHz doesn't always come up #9035

openwrt-bot opened this issue Sep 19, 2021 · 12 comments
Labels
flyspray release/21.02

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented Sep 19, 2021

kroeckx:

I upgraded my UniFI 6 LR from 21.02-rc4 to 21.02, and the 5 GHz didn't come up

The log contained:

[ 82.530766] procd: - init -
[ 82.693561] urngd: v1.0.2 started.
[ 82.693573] kmodloader: loading kernel modules from /etc/modules.d/*
[ 82.715949] Loading modules backported from Linux version v5.10.42-0-g65859eca4dff
[ 82.721972] random: crng init done
[ 82.723533] Backport generated by backports.git v5.10.42-1-0-gbee5c545
[ 82.726920] random: 6 urandom warning(s) missed due to ratelimiting
[ 82.758353] xt_time: kernel timezone is -0000
[ 82.825175] mtk-spi-nor 11014000.spi: dma read timeout.
[ 82.832591] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 82.860179] mt7915e 0000:01:00.0: assign IRQ: got 130
[ 82.865298] pci 0000:00:00.0: enabling bus mastering
[ 82.870276] mt7915e 0000:01:00.0: enabling device (0000 -> 0002)
[ 82.876353] mt7915e 0000:01:00.0: enabling bus mastering
[ 82.910736] mt7622-wmac 18000000.wmac: HW/SW Version: 0x8a108a10, Build Time: 20190801210006a
[ 82.910736]
[ 82.958342] mt7915e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20201105222230a
[ 82.958342]
[ 83.083169] mt7622-wmac 18000000.wmac: N9 Firmware Version: 2.0, Build Time: 20200131180931
[ 83.103528] mt7915e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20201105222304
[ 83.152087] mt7915e 0000:01:00.0: WA Firmware Version: DEV_000000, Build Time: 20201105222323
[ 83.270498] mtk-spi-nor 11014000.spi: dma read timeout.
[ 83.276046] mt7915e: probe of 0000:01:00.0 failed with error -110
[ 83.289668] PPP generic driver version 2.4.2
[ 83.294505] NET: Registered protocol family 24
[ 83.302489] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 85.403795] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode
[ 85.412217] mtk_soc_eth 1b100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control off

I then rebooted, and it did come up, the log now showed:

[ 6.916314] procd: - init -
[ 7.066192] kmodloader: loading kernel modules from /etc/modules.d/*
[ 7.080571] urngd: v1.0.2 started.
[ 7.088294] Loading modules backported from Linux version v5.10.42-0-g65859eca4dff
[ 7.095887] Backport generated by backports.git v5.10.42-1-0-gbee5c545
[ 7.108576] random: crng init done
[ 7.112008] random: 6 urandom warning(s) missed due to ratelimiting
[ 7.120977] xt_time: kernel timezone is -0000
[ 7.198829] mtk-spi-nor 11014000.spi: dma read timeout.
[ 7.206369] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 7.238726] mt7915e 0000:01:00.0: assign IRQ: got 130
[ 7.243838] pci 0000:00:00.0: enabling bus mastering
[ 7.248816] mt7915e 0000:01:00.0: enabling device (0000 -> 0002)
[ 7.254907] mt7915e 0000:01:00.0: enabling bus mastering
[ 7.285262] mt7622-wmac 18000000.wmac: HW/SW Version: 0x8a108a10, Build Time: 20190801210006a
[ 7.285262]
[ 7.346831] mt7915e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20201105222230a
[ 7.346831]
[ 7.436626] mt7622-wmac 18000000.wmac: N9 Firmware Version: 2.0, Build Time: 20200131180931
[ 7.532980] mt7915e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20201105222304
[ 7.583152] mt7915e 0000:01:00.0: WA Firmware Version: DEV_000000, Build Time: 20201105222323
[ 7.710630] PPP generic driver version 2.4.2
[ 7.716260] NET: Registered protocol family 24
[ 7.724504] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 9.395937] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode
[ 9.404503] mtk_soc_eth 1b100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control off

@aparcar aparcar added the release/21.02 label Feb 22, 2022
@kroeckx
Copy link
Contributor

@kroeckx kroeckx commented Mar 1, 2022

I can still reproduce this using 21.02.2.

@kroeckx
Copy link
Contributor

@kroeckx kroeckx commented Mar 1, 2022

One of my boots with a problem contained:

[    7.070026] kmodloader: loading kernel modules from /etc/modules.d/*
[    7.083817] urngd: v1.0.2 started.
[    7.091805] Loading modules backported from Linux version v5.10.85-0-ge4f2aee6612e
[    7.099404] Backport generated by backports.git v5.10.85-1-0-gf988973f
[    7.111530] crng init done
[    7.114270] random: 6 urandom warning(s) missed due to ratelimiting
[    7.124089] xt_time: kernel timezone is -0000
[    7.214092] mtk-spi-nor 11014000.spi: dma read timeout.
[    7.219335] mt7622-wmac 18000000.wmac: reading EEPROM from mtd factory failed: -110
[    7.229844] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[    7.257832] mt7915e 0000:01:00.0: assign IRQ: got 130
[    7.262952] pci 0000:00:00.0: enabling bus mastering
[    7.267929] mt7915e 0000:01:00.0: enabling device (0000 -> 0002)
[    7.274014] mt7915e 0000:01:00.0: enabling bus mastering
[    7.356798] mt7622-wmac 18000000.wmac: HW/SW Version: 0x8a108a10, Build Time: 20190801210006a
[    7.356798] 
[    7.373057] mt7915e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20201105222230a
[    7.373057] 
[    7.521368] mt7622-wmac 18000000.wmac: N9 Firmware Version: 2.0, Build Time: 20200131180931
[    7.572143] mt7915e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20201105222304
[    7.620694] mt7915e 0000:01:00.0: WA Firmware Version: DEV_000000, Build Time: 20201105222323
[    7.739280] mtk-spi-nor 11014000.spi: dma read timeout.
[    7.744518] mt7915e 0000:01:00.0: reading EEPROM from mtd factory failed: -110
[    7.752065] mt7915e: probe of 0000:01:00.0 failed with error -110
[    7.765806] PPP generic driver version 2.4.2
[    7.770700] NET: Registered protocol family 24
[    7.779656] kmodloader: done loading kernel modules from /etc/modules.d/*
[    8.343512] mtk-spi-nor 11014000.spi: dma read timeout.
[    8.348759] jffs2: error: (1273) check_node_data: can not read 2136 bytes from 0x015d176c, error code: -110.
[    8.358602] jffs2: error: (1273) check_tn_node: check_node_data() returned error: -110.
[    8.375164] mtk-spi-nor 11014000.spi: dma read timeout.
[    8.380394] jffs2: error: (1273) check_node_data: can not read 2148 bytes from 0x015fbdc0, error code: -110.
[    8.390219] jffs2: error: (1273) check_tn_node: check_node_data() returned error: -110.
[    8.456779] mtk-spi-nor 11014000.spi: dma read timeout.
[    8.462038] jffs2: error: (1273) check_node_data: can not read 2144 bytes from 0x0167a460, error code: -110.
[    8.471911] jffs2: error: (1273) check_tn_node: check_node_data() returned error: -110.
[    8.519978] mtk-spi-nor 11014000.spi: dma read timeout.
[    8.525266] jffs2: error: (1273) check_node_data: can not read 2149 bytes from 0x016b9f54, error code: -110.
[    8.535122] jffs2: error: (1273) check_tn_node: check_node_data() returned error: -110.
[    8.547125] mtk-spi-nor 11014000.spi: dma read timeout.
[    8.552399] jffs2: error: (1273) check_node_data: can not read 2154 bytes from 0x016ca940, error code: -110.
[    8.562246] jffs2: error: (1273) check_tn_node: check_node_data() returned error: -110.
[    8.571518] mtk-spi-nor 11014000.spi: dma read timeout.
[    8.576770] jffs2: error: (1273) check_node_data: can not read 2142 bytes from 0x016c6278, error code: -110.
[    8.586611] jffs2: error: (1273) check_tn_node: check_node_data() returned error: -110.
[    8.596088] mtk-spi-nor 11014000.spi: dma read timeout.
[    8.601369] jffs2: error: (1273) check_node_data: can not read 2140 bytes from 0x016c107c, error code: -110.
[    8.611243] jffs2: error: (1273) check_tn_node: check_node_data() returned error: -110.
[    9.839679] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode

One where the wifi comes up has:

[    7.063085] kmodloader: loading kernel modules from /etc/modules.d/*
[    7.076985] urngd: v1.0.2 started.
[    7.085556] Loading modules backported from Linux version v5.10.85-0-ge4f2aee6612e
[    7.093145] Backport generated by backports.git v5.10.85-1-0-gf988973f
[    7.103952] crng init done
[    7.106692] random: 6 urandom warning(s) missed due to ratelimiting
[    7.122685] xt_time: kernel timezone is -0000
[    7.229454] mtk-spi-nor 11014000.spi: dma read timeout.
[    7.234720] mt7622-wmac 18000000.wmac: reading EEPROM from mtd factory failed: -110
[    7.244853] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[    7.272833] mt7915e 0000:01:00.0: assign IRQ: got 130
[    7.277975] pci 0000:00:00.0: enabling bus mastering
[    7.282982] mt7915e 0000:01:00.0: enabling device (0000 -> 0002)
[    7.289080] mt7915e 0000:01:00.0: enabling bus mastering
[    7.345357] mt7622-wmac 18000000.wmac: HW/SW Version: 0x8a108a10, Build Time: 20190801210006a
[    7.345357] 
[    7.395597] mt7915e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20201105222230a
[    7.395597] 
[    7.423620] mt7622-wmac 18000000.wmac: N9 Firmware Version: 2.0, Build Time: 20200131180931
[    7.593295] mt7915e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20201105222304
[    7.643045] mt7915e 0000:01:00.0: WA Firmware Version: DEV_000000, Build Time: 20201105222323
[    7.773729] PPP generic driver version 2.4.2
[    7.779208] NET: Registered protocol family 24
[    7.790732] kmodloader: done loading kernel modules from /etc/modules.d/*
[    9.860033] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode

The difference that I see is that on a failed boot, it always contained:

[    7.752065] mt7915e: probe of 0000:01:00.0 failed with error -110

There are various others errors in the log related to dma read timeout. I'm not sure if they are related or not.

Those lines look like an error, but they show up in both a good and bad boot:

[    7.229454] mtk-spi-nor 11014000.spi: dma read timeout.
[    7.234720] mt7622-wmac 18000000.wmac: reading EEPROM from mtd factory failed: -110

I can reproduce this about 75% of the time.

@aep
Copy link
Contributor

@aep aep commented Mar 10, 2022

does that mean 21.02-rc4 works? unfortunately i cant compile that git tag. got a hash that is known to work?

btw. i can work around the issue with a cold boot. unplugging the cable and plugging it back in makes it work fine.

@kroeckx
Copy link
Contributor

@kroeckx kroeckx commented Mar 10, 2022

@chris-palmer99
Copy link

@chris-palmer99 chris-palmer99 commented Mar 11, 2022

Same problems here on an Unify 6 LR installed yesterday with 21.02.2. Booting results in either:

  • Working correctly
  • 5Ghz radio flagged as "generic" (and not working)
  • 5Ghz radio working for the first listed SSID only, but with subsequent ones marked "disabled" (and can't be enabled).

(I also have a Unify 6 Lite on 21.02.2 which doesn't have this problem.)

@julianrichen
Copy link

@julianrichen julianrichen commented Mar 11, 2022

I have the Unifi Wifi 6 Long Range.

I ran into this issue as well but I think I resolved it since I have 5Ghz working fine. When I checked the wireless config uci show wireless or cat /etc/config/wireless I found I was missing some options for config wifi-device 'radio1'. Namely the option country. I wasn't sure what it was suppose to be so I went to add via the GUI and I got some errors about out of array index issues but was able to save.

Maybe you can add the country (I did US - United States) and it'll work for you? You can find it under:

Network > Wireless > Find SSID > Edit > Advanced Settings (tab) > Country Code

Here are all the steps I took to get to that point. I'm 99.99% sure it's that since if I undo it, it stops working, and re-adding fixes it. But maybe this can help others troubleshoot:

  1. See the 5Ghz SSID as Disabled, radio1 shows as Generic
  2. Remove 5GhZ SSID, see it returned to MediaTek MT7915E 802.11nacax
  3. Add a new 5Ghz SSID, see SSID goes back to Disabled and radio1 goes back to Generic
  4. Delete the 5Ghz SSID
  5. Edit /etc/config/wireless
  6. Save a copy of the 5Ghz SSID and radio1 for reference
config wifi-device 'radio1'
	option type 'mac80211'
	option path '1a143000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
	option band '5g'
	option cell_density '0'
	option channel '52'
	option htmode 'HE80'
	option country 'US'

config wifi-iface 'wifinet1'
	option device 'radio1'
	option mode 'ap'
	option encryption 'psk2'
	option network 'lan'
	option key 'XXXXXXXXX'
	option ssid 'XXXXXXXXX'
  1. Delete those config items
  2. Restart wireless service to rebuild it (/etc/init.d/network restart or service network restart)
  3. Check that radio1 gets re-added
  4. Notice some of the options no longer exist (naemly country and a few others)
  5. Went to edit the config in GUI and got the array index error mentioned before, seemingly because it was trying to load in all the options but they didn't exist int he config
  6. Had to add back some of the options above (except I didn't know about the country one) and then it made it work, not sure which ones are required to not break the GUI
  7. Got back to the GUI, re-add missing country code: Network > Wireless > Find SSID > Edit > Advanced Settings (tab) > Country Code
  8. 5Ghz SSID now connects, radio1 shows MediaTek MT7915E 802.11nacax

If it helps others to compare:

# cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'platform/18000000.wmac'
	option band '2g'
	option htmode 'HT20'
	option cell_density '0'
	option channel '1'

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

config wifi-device 'radio1'
	option type 'mac80211'
	option path '1a143000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
	option band '5g'
	option cell_density '0'
	option channel '52'
	option htmode 'HE80'
	option country 'US'

config wifi-iface 'wifinet1'
	option device 'radio1'
	option mode 'ap'
	option encryption 'psk2'
	option network 'lan'
	option key 'XXXXXXXXX'
	option ssid 'XXXXXXXXX'
# uci show wireless
wireless.radio0=wifi-device
wireless.radio0.type='mac80211'
wireless.radio0.path='platform/18000000.wmac'
wireless.radio0.band='2g'
wireless.radio0.htmode='HT20'
wireless.radio0.cell_density='0'
wireless.radio0.channel='1'
wireless.default_radio0=wifi-iface
wireless.default_radio0.device='radio0'
wireless.default_radio0.network='lan'
wireless.default_radio0.mode='ap'
wireless.default_radio0.encryption='psk2'
wireless.default_radio0.key='XXXXXXXXX'
wireless.default_radio0.ssid='XXXXXXXXX'
wireless.radio1=wifi-device
wireless.radio1.type='mac80211'
wireless.radio1.path='1a143000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
wireless.radio1.band='5g'
wireless.radio1.cell_density='0'
wireless.radio1.channel='52'
wireless.radio1.htmode='HE80'
wireless.radio1.country='US'
wireless.wifinet1=wifi-iface
wireless.wifinet1.device='radio1'
wireless.wifinet1.mode='ap'
wireless.wifinet1.encryption='psk2'
wireless.wifinet1.network='lan'
wireless.wifinet1.key='XXXXXXXXX'
wireless.wifinet1.ssid='XXXXXXXXX'

@kroeckx
Copy link
Contributor

@kroeckx kroeckx commented Mar 11, 2022

But does it properly come up every time you reboot the device?

@julianrichen
Copy link

@julianrichen julianrichen commented Mar 12, 2022

I've rebooted ~8 since doing that to either test some changes or to move the AP to another location and it's held. Maybe I'm lucky but prior to that 5Ghz wouldn't work.

Maybe my issue was a different issue with the same symptoms.

@tustars
Copy link

@tustars tustars commented Apr 17, 2022

The workaround does not work for me.
I remove config wifi-device 'radio1' and config wifi-iface 'default_radio1' including options but they do not reappear when I run /etc/init.d/network restart nor when I run service network restart.

@HolgerHees
Copy link

@HolgerHees HolgerHees commented Apr 17, 2022

I have the same issues too with my new Unifi 6 LR.

currently I have to restart my wifi twice per day, because all clients (~20) are losing their connection. I guess this is not related to this ticket, but If I try to restart my wifi with "wifi down" and "wifi up", many times the kernel crashes and after my AP is rebooting I have the symptoms described before.

with log messages like
jffs2: error: (1273) check_tn_node: check_node_data() returned error: -110.
mtk-spi-nor 11014000.spi: dma read timeout.

and the second radio is shown as generic

also a "rmmod mt7915e" followed by a "modprobe mt7915e" dows not help. Radio device is not responding. Only an additional reboot helps most of the time.

@manliebert
Copy link

@manliebert manliebert commented Apr 18, 2022

I brought openwrt 21.02.2 on a new UniFi6LR yesterday morning and I am facing the same issues.
On 36 of 88 reboots the kernel has trouble on getting the wifi up.

I now use this script as workaround that reboots if the mt7915e probe fails:

root@UniFi6LR:~# cat fix.sh
if dmesg | grep -q "mt7915e: probe of 0000:01:00.0 failed with error -110"; then
    sleep 60
    echo "$(date) Going to reboot because of wlan problems"
    reboot
else
    sleep 60
    echo "$(date) Wlan looks ok"
fi
root@UniFi6LR:~# cat /etc/rc.local
# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.
/root/fix.sh | tee -a /root/fix.log &
exit 0

For me this is fine for now, when its only happening on a power loss.
Till now, the connection of ~10 clients seems to be stable.

@HolgerHees
Copy link

@HolgerHees HolgerHees commented Apr 18, 2022

I check the github repo for this driver and it looks like the current driver was in a very early stage. A lot of additional work happens for this driver and I'm looking forward when this will be available in the official openwrt version

https://github.com/openwrt/mt76/commits/master/mt7915

b.s.w. my original problem (clients losing connections) was related to my IoT devices which was always disconnect from wifi before they was going to sleep for 5 minutes. Means I had 30 connects and disconnects per hour. After I refactored this devices, to stay always connected, my problem was gone now since 36 hours (fingers crossed :-)) Looks like it is also related somehow to this driver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray release/21.02
Projects
None yet
Development

No branches or pull requests

9 participants