mt76
mt76 copied to clipboard
openwrt
mt7615 firmware init failed after soft reboot (reset required?)
@nbd @chunkeey @LorenzoBianconi SoC is IPQ4019.
After a soft reboot, MT7615 no longer works
mt7615e 0000:01:00.0: enabling device (0140 -> 0142)
mt7615e 0000:01:00.0: Firmware is not ready for download
mt7615e: probe of 0000:01:00.0 failed with error -5
I checked the val in mt7615_load_firmware
https://github.com/openwrt/mt76/blob/6f7d0f503d1013f0909fe52075da5d5d500ddca4/mt7615/mcu.c#L519 and it is already 7 (FW_STATE_CR4_RDY)
It seems that either the PCIe driver does not power cycle the PCIe interface after reboot, or the mt76 driver does not warm reset the mt7615 chip.
Update: If I unload the driver manually by rmmod mt7615e, it will work after the reboot
It seems that either the PCIe driver does not power cycle the PCIe interface after reboot, or the mt76 driver does not warm reset the mt7615 chip.
That wouldn't surprise me. A lot of ath10k chips have problems after being PCIe reseted... if done inproperly they are taking down the system with it...
That said, there's also patches like this that might not have trickled down (ye):
https://patchwork.kernel.org/patch/10966623/
So please check if this patch still applies to your case.
@chunkeey The patch has already been backported to 4.19 gregkh/linux@6b71c62ea9dac0e7e0b3a79575b4a2c7033b7cab and it does not help
I have added a script as a workaround on my device that will automatically execute rmmod mt7615e on shutdown/reboot.
Create a file /etc/init.d/mt7615workaround with content:
#!/bin/sh /etc/rc.common
STOP=52
stop() {
rmmod mt7615e
}
Then link it into /etc/rc.d by executing cd /etc/rc.d && ln -s ../init.d/mt7615workaround K52mt7615wa.
Any updates on this? I'm facing a similar problem with a Linksys E8450 aka Belkin ~~AX~~RT3200:
Tue Mar 30 00:01:16 2021 kern.debug kernel: [ 1596.726529] mt7915e 0000:01:00.0: assign IRQ: got 144
Tue Mar 30 00:01:16 2021 kern.debug kernel: [ 1596.731735] mt7915e 0000:01:00.0: enabling bus mastering
Tue Mar 30 00:01:20 2021 kern.err kernel: [ 1600.565394] mt7915e 0000:01:00.0: Firmware is not ready for download
Tue Mar 30 00:01:20 2021 kern.warn kernel: [ 1600.572694] mt7915e: probe of 0000:01:00.0 failed with error -5
Is there any update on this topic ? I am facing this issue on IpTime A8004T device. After first install of kernel and sysupgrade I can configure and use both 2.4 and 5 G radio devices but after reset only 5G radio works. I tried to play with some parameters like channel change, country code change, serialize option on but nothing seems to bring back the device to life. I am using 21.02.0-rc4 (r16256-2d5ee43dc6)
I had the same problem with Totolink A7000R. 2.4Ghz radio didn't even start up. 5GHz was working fine. I've tried (soft)rebooting several times with no result. Finally i did a power cycle and this time 2.4GHz worked. I've followed @tinxx instructions and so far it works, even after rebooting (both software reboot and poweroff).
Many thanks to you, @tinxx, and of course everyone involved in OpenWrt 🎉
EDIT: My apologies. I realize now that I was testing in a virtualized environment. Making it the host responsibility to properly reset the PCIe device. So whether OpenWrt 22.3.1 still has the same issue or not I really can't say
So whether OpenWrt 22.3.1 still has the same issue or not I really can't say
I have a TOTOLINK A7000R router flashed with 22.03.2 r19803-9a599fee93. Was working without issues for 100+ days. Today after upgrade to 22.03.3 the 2.4 GHz wireless went down. Downgrade to 22.03.2 - 2.4 GHz still down. Reboots didnt help, had to poweroff the device and then it worked. So it seems it's still here.
I install 22.3.3 on my Iptime A6ns-M (MT7621 SoC, MT7615E). After install, I can only use 5G radio. System log say "hostapd: Could not set interface wlan1 flags (UP): I/O error". After hard reset, it works but reboot on luci make 2.4 GHz radio fails... It still happened in 22.3.3...
Thank you @tinxx
The script is working on a Totolink A7000R running 22.03.5
