misuzu
July 9, 2024, 12:12am
388
Were the latest commits (for proprietary driver) being included for the snapshot builds? (MT6000 4.6.* /4.7) Like this one:
https://git01.mediatek.com/plugins/gitiles/openwrt/feeds/mtk-openwrt-feeds/+/cdb203f394f43f4f73f277b33f286448198ae0e8
1 Like
Thanks. We'll make a check.
1 Like
ywp
July 9, 2024, 2:01am
390
I didn't repeat the problem
ywp:
cat /proc/oui-tertf/term
Can I take a look at this?
You can send it to me privately
thank you
does the Beryl AX op24 firmware include this patch that fixes the unicast crash?
opened 03:47PM - 20 May 24 UTC
I already made a comment on #866, but I don't think this is related.
I'm expe… riencing crashes with multi-psk on MT7981.
- when connecting to the network using the main WPA2 PSK, everything is stable.
- when connecting to the network using a secondary WPA2 PSK, if station doesn't move to another ap_vlan everything is stable.
- when connecting to the network using any of the secondary PSKs, if a station moves to a secondary ap_vlan, everything works until a station starts sending traffic to the AP
- then the chip hangs, and a combination of 00005aed and 000026ed timeouts happens
When using OpenWrt snapshot without any patches to the mt76 driver, the chip completely restarts on it's own and the wifi network appears in a couple of seconds. All clients including ones connected via the main PSK get disconnected.
Then I tried [rany2/openwrt@18cc739](https://github.com/rany2/openwrt/commit/18cc739263004d4846991c9afbc6ba45c39293a1) patch and 0x5a messages stop appearing but the chip still hangs, the driver shows 0x26 timeout and restarts.
I then tried to compile the [rany2/openwrt](https://github.com/rany2/openwrt) fork and since it applies a bunch of [patches](https://github.com/rany2/openwrt/tree/main/package/kernel/mt76/patches), when the chip hangs, it manages to recover without disconnecting clients, but shows the following:
```
[ 447.275349] mt798x-wmac 18000000.wifi: send message 000130ed timeout, try again(1).
[ 447.283349] mt798x-wmac 18000000.wifi:
[ 447.283349] phy0 L1 SER recovery completed.
[ 447.821897] mt798x-wmac 18000000.wifi: phy0 SER recovery state: 0x00000004
[ 447.828811] mt798x-wmac 18000000.wifi:
[ 447.828811] phy0 L1 SER recovery start.
[ 447.837695] mt798x-wmac 18000000.wifi: phy0 SER recovery state: 0x00000008
[ 447.854270] mt798x-wmac 18000000.wifi: phy0 SER recovery state: 0x00000010
[ 447.861219] mt798x-wmac 18000000.wifi: phy0 SER recovery state: 0x00000020
[ 447.868360] mt798x-wmac 18000000.wifi:
[ 447.868360] phy0 L1 SER recovery completed.
```
I'm assuming that 0x00130ed is message type 0x30 MCU_EXT_CMD_GET_TX_STAT.
The same setup works on MT7613, MT7612, MT7615, MT7603, client optimized MT7921k (n, ac, ax), and appears to not hang even on MT7975 (Asus RT-AX53U) even though it uses the same mt7915e module.
So I'm assuming that this is a firmware bug, so I tried all five firmware versions published on [mtk-feeds](https://git01.mediatek.com/plugins/gitiles/openwrt/feeds/mtk-openwrt-feeds/), and it's similar with all, but the crashes don't happen as often with the latest firmware.
Additionally, I assumed that this is related to GTK (as it is different ) so I applied a patch similar to this [mt7615 workaround from a few years back](https://github.com/openwrt/mt76/issues/494#issuecomment-772675193), but it didn't do anything.
If possible, can someone explain to me what's the difference between stations connected to the main AP interface vs ones connected to AP_VLAN interface? The GTK is different, but why would it cause it to crash the firmware?
Renato
July 9, 2024, 10:07am
392
I'm the only one with this problem?
alzhao
July 9, 2024, 10:20am
393
What problem?
It is hard to read such a long post.
1 Like
Renato
July 9, 2024, 11:02am
394
alzhao:
What problem?
That one I answered on the previous message.
Here is:
Firmware: 4.6.2 Release 1 (28/06/2024)
Device: GL-MT6000 (Flint 2)
My Google Pixel 7 started to disconnect automatically on the DHCP Release Time, not extending the lease time (720 minutes).
Connected:
Sat Jul 6 21:22:15 2024 daemon.info dnsmasq-dhcp[9873]: DHCPREQUEST(br-lan) 192.168.6.171 46:cb:ad:0c:e8:ef
Sat Jul 6 21:22:15 2024 daemon.info dnsmasq-dhcp[9873]: DHCPACK(br-lan) 192.168.6.171 46:cb:ad:0c:e8:ef Pixel-7
After 50% of the Lease Time, Pixel 7 sent another DHCP request.
At thi…
Version 4.7 is still in alpha ......
The 4.6 op24 release was previously paused for a while in order to quickly fix bugs. it has now been resumed.
5 Likes
alzhao
July 10, 2024, 4:24am
396
I tested my iphone, changed dhcp release to 2 minutes and test. Don't have such problem.
Maybe you can change the dhcp lease shorter to do more testing.
6hours may be too long so that other factors interfere.
misuzu
July 10, 2024, 12:05pm
397
pesa1234's build includes a lot of fixes that could lessen the bugs and headache for you guys. please check it
1 Like
Interesting.
I'm finally running flint 2 with 4.6.2 as my main router again.
Should be a smooth experience now that I've ironed out VPN shenanigans.
Renato
July 11, 2024, 8:29am
399
Hi,
Is there any reason for the Beta and Snapshots were been removed?
Eddited: I guess it's because the 4.6.2 was moved to the Stable now.
1 Like
Can you point me to the new build for berly ax please. There is nothing new in the download center.
@thomasm 4.6.2 is available in software center. It is dated 6-28-2024. This is the latest stable version.
fch
July 11, 2024, 2:06pm
402
Not for my router, apparently the S1300 is very low priority.
I mean the Native OpenWrt 24 version. Not the stable one.
@thomasm Ah, ok, so unrelated to the 4.6 versions in this thread.
I don't know much about that model, but it shows as discontinued on the gl-inet website. Generally devices fall into maintenance updates and may not get feature updates. Thus, I would not hold my breath for anything in the 4.x branch or newer.
Renato
July 12, 2024, 8:25am
406
Tested the 2 minutes lease time (by 1 hour); OK
Tested the 30 minutes lease time (by 4 hours); OK
Tested the 120 minutes lease time (by 12 hours). I found one disconnection at midnight.
It renew the lease time some times, but then, it disconnects:
Fri Jul 12 00:46:31 2024 kern.warn kernel: [928837.462225] 7986@C08L2,ap_peer_disassoc_action() 3645: ASSOC - 1 receive DIS-ASSOC request
Fri Jul 12 00:46:31 2024 kern.warn kernel: [928837.470641] 7986@C01L2,wifi_sys_disconn_act() 1002: wdev_idx=2
Fri Jul 12 00:46:31 2024 kern.notice kernel: [928837.476889] 7986@C08L3,hw_ctrl_flow_v2_disconnt_act() 172: wdev_idx=2
Fri Jul 12 00:46:31 2024 kern.warn kernel: [928837.483990] 7986@C13L2,MacTableDeleteEntry() 1938: Del Sta:cb:ad:0c:e8:ef
Try to disable the option "Auto-connect" on the wif-fi settings on your phone, so when it disconnect you will see easier.
if it helps I have 2 pixel phones. 6 Pro and 4a but I'm not seeing the issue you described.