Suggest that you refresh the targets based on UBI fault within the 22.03.4, 21.02.6 trees with builds later than the currently posted r20123 release. Snapshots will automagically see the fix sometime later since the PR had been posted today. The builds from the GIT pull only confirm that the correction has addressed the problem.
Thanks, running well on TP-Link Archer A7! Looking forward to next major release with hopes of seeing more movement towards DSA implementation in ath79
Hello, what exactly do you mean by use "master" - what's that, should I build an image from master branch or do you mean something else? If you've got some manual how to do that, I'd be glad. I don't want to downgrade to 21.02 
So the VLAN issues are finally fixed?
Upgraded a Netgear R7800 and a Buffalo WZR-HP-AG300H from 22.03.3 to 22.03.4; sysupgrade keeping config in both cases. All seems normal.
The units' configuration is described here.
Happy to report an 'Attended Sysupgrade' (keeping settings) for TP-Link c2600
22.03.3 => 22.03.4 OK
There are numerous ath10k_pci entries in the logs that didn't exist prior to 22.03.4 though:
syslog:
these occur directly after a:
did not acknowledge authentication response,
disassociated,
deauthenticated due to inactivity,
AP-STA-DISCONNECTED,
authenticated, or
associated (aid 1)
hostapd event.
kern.info kernel: [55106.051510] ath10k_pci 0000:01:00.0: mac flush vdev 0 drop 0 queues 0x1 ar->paused: 0x0 arvif->paused: 0x0
corresponding kernel log entry:
[55106.051510] ath10k_pci 0000:01:00.0: mac flush vdev 0 drop 0 queues 0x1 ar->paused: 0x0 arvif->paused: 0x
Are they just information logs?
2 Likes
He means with master the main development branch that is named "master" in git. See https://git.openwrt.org/?p=openwrt/openwrt.git;a=summary
Development snapshots are made from master.
22.03 and 21.02 are rather stable released branches with mostly static code based on the original branching moment.
Ps. "master" main soon be renamed as "main".
5 Likes
All working fine on Askey RT4230W REV6 (RAC2V1K) 
1 Like
for any non-v22 release, the VLAN issues of mvebu (Linksys WRT, Turris…) are fixed/non-relevant:
- snapshot releases have the fix
- Linksys WRT Divested community build is based on main/snapshot and has the fix: (https://forum.openwrt.org/t/divested-wrt-no-nonsense-hardened-builds-for-linksys-wrt-series).
- Turris Omnia official release is based on main/snapshot and has the fix
- upcoming OpenWRT v23 for all mvebu will have the fix
- OpenWRT v21.x does not have the issue, so it does not need the fix
VLAN issues of mvebu will remain unfixed in any v22.x forever:
- ongoing no more v22 build releases for mvebu
- no backports to any future v22 maintenance release
6 Likes
Updated AVM Fritzbox 4040 using Attended SysUpgrade without problems.
Many thanks to the team for this software.
1 Like
fwiw, I installed 22.03.4 onto my 'spare' Hub One as a quick test this morning.
I can confirm the bootloop bug has been fixed. Hub takes about 50 seconds from switching on to blue power light appearing. Previously, it used to take 'several' minutes.
1 Like
Updated (sysupgrade) my Netgear GS308T and my Nanopi R4S - - no problems - runs fine
1 Like
I updated 2x R7800 and a RT-AC68U (which I just use as managed switch) from previous stable. All without issues.
Thanks devs!
TP-LINK TD-W8970 successfully updated. 
Many thanks to all the devs.
1 Like
Plusnet Hub One successfully updated, retaining settings, acting as a wireless repeater.
Update went quicker than I expected.
Many thanks.
I've updated two Netgear WAX202, an Asus RT-AC87U and a Fritzbox 7360 v1, all working great, thank you so much guys!
Upgrade of netgear R6220 (mt7621) and 3700v2 (ath79 generic).
Reporting two successful sysupgrades with settings:
- Belkin RT3200: 22.03.3 to 22.03.4
- D-Link DAP-X1860: 1-2 month(s) old snapshot to 22.03.4
Both used for close to a day without any issues. Thank you for all the hard work!
My rockchip pro 64 keeps failing constantly after 4 tries. I'm reverting to 22.03.3 because I dont have time to troubleshoot this. good luck.