mt7981 - mt798x-wmac 18000000.wifi: Message 00005aed timeout #860
Comments
|
@lukasz1992 Any chance your issue and this could be related? #866 cc: @rany2 |
|
@Fail-Safe Crash log looks exactly the same. I compile mt76 on my own. I reverted commit d9dd763 , now I have 0 crashes |
|
You could use this patch from my tree if you don't want to revert it yourself: https://raw.githubusercontent.com/rany2/openwrt/4ad7ed1d5d5b77d32999c9314cc1cec3ee2a9724/package/kernel/mt76/patches/9009-wifi-mt76-mt7915-do-not-use-event-format-to-get-.patch |
|
So with your patch, @rany2, you're able to run |
|
@Fail-Safe I never had to daily drive |
|
After ~1.5 months of tests I can tell that reverting d9dd763 is a working workaround. |
|
@rany2 i noticed when I use here is a relevant part: open stacktraceonly custom change i made on mt76 was this patch by leans OpenWrt: https://github.com/coolsnowwolf/lede/blob/master/package/kernel/mt76/patches/001-allow-vht-on-2g.patch though the crash happened on 5ghz for me and it seems from all my network devices only my Ayaneo Geek 1S is the trouble maker (Intel AX210). by reading this issue about multicast and especially this line: I compile my own openwrt based on test kernel 6.6, here is my fork: https://github.com/xize/openwrt-flint2-testing -edit- @rany2 I have tested this patch, but this doesn't work in my certain topology interestingly I have more multi psk networks mainly with homewizard and aqara devices these seem not to crash the MT76 driver (can be run a week+), but when I use my Ayaneo Geek 1S (Intel AX210) then it crashes, sometimes it does that directly other times it takes some time mainly with p2p udp gta online traffic, if I crashed it a few times it start working for a longer time of period, it is a very confusing issue and im being clueless where I should look, do you have any idea?, I realized multi psk phys all get enabled with allmulticast mode aswell. ^ I also tried playing around with the Intel Ax210 driver if WoWlan or turning SMPS to off would do a change but with no avail. |
|
@nbd168 - what do you think about this? My
Many times, the client is just disconnected but I recently found that one of my SSIDs went down and would not recover without a reboot. I am on a snapshot I built several days ago. |
Do you have an updated revert of that commit? It no longer clearly reverts: |
|
Thanks @lukasz1992 - EDIT: my bad, this applies. |
I am basing on openwrt stable release, but for mt76 I use master. |
|
That's OK. I am not entirely sure what I am seeing is the same issue. See my description here: #860 (comment) |
If using |
|
@degen91 - thanks for the reply. I am not using |
|
@lukasz1992 - the patch you shared does not seem to fix the issue for me. This time wifi did not crash but I found the same output in dmesg: and in logread |
|
I recently started to observe the same issue on my OpenWRT (23.05.2 r23630-842932a63d) So seq id reaches 15 max and start over again In my case it looks like related to some hardware failure |
|
MediaTek recently released a new wifi firmware fixing various bugs: #881 You can try a SNAPSHOT OpenWrt firmware (this includes the latest wifi fw), or you can download the new wifi fw to /lib/firmware/mediatek/ from https://github.com/openwrt/mt76/tree/master/firmware |
Hello, with the most recent version of mt76 in OpenWRT 23.05.2 I have some temporary breaks (every 2-4 weeks) on WiFi - both SSID (2.4GHz and 5GHz disappears). Driver/fw/hw is able to recover itself within a minute.
[559161.263353] mt798x-wmac 18000000.wifi: Message 00005aed (seq 10) timeout
[1563791.313702] mt798x-wmac 18000000.wifi: Message 00005aed (seq 1) timeout
[2326012.477521] mt798x-wmac 18000000.wifi: Message 00005aed (seq 4) timeout
[2326776.176547] mt798x-wmac 18000000.wifi: Message 000026ed (seq 1) timeout
[2326776.183360] mt798x-wmac 18000000.wifi: Message 00005aed (seq 2) timeout
The common thing is message 0x5A, which is GET_MIB_INFO (I'd guess 0x26 request timed out because of the next 0x5A request).
The same problem was reported with mt7915 chip, @rany2 found a workaround to revert d9dd763.
I will try it and report if it helps.
The text was updated successfully, but these errors were encountered: