@aparcar please include https://github.com/openwrt/openwrt/issues/11821 into Known Issues. I just entered a bootloop after upgrading from 22.03.2
Getting error. Network is working fine. In 22.03.3, this spam could be stopped with ethtool -K eth0.10 rx off. This doesn't work anymore.
Wed Apr 19 02:02:36 2023 kern.err kernel: [22855.435101] eth0.10: hw csum failure
Wed Apr 19 02:02:36 2023 kern.err kernel: [22855.438727] skb len=24 headroom=188 headlen=24 tailroom=1964
Wed Apr 19 02:02:36 2023 kern.err kernel: [22855.438727] mac=(134,14) net=(148,40) trans=188
Wed Apr 19 02:02:36 2023 kern.err kernel: [22855.438727] shinfo(txflags=0 nr_frags=0 gso(size=0 type=0 segs=0))
Wed Apr 19 02:02:36 2023 kern.err kernel: [22855.438727] csum(0xffff8911 ip_summed=2 complete_sw=0 valid=0 level=0)
Wed Apr 19 02:02:36 2023 kern.err kernel: [22855.438727] hash(0x0 sw=0 l4=0) proto=0x86dd pkttype=2 iif=8
Wed Apr 19 02:02:36 2023 kern.err kernel: [22855.468158] dev name=eth0.10 feat=0x0000000040005021
Wed Apr 19 02:02:36 2023 kern.err kernel: [22855.473141] skb headroom: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Wed Apr 19 02:02:36 2023 kern.err kernel: [22855.480800] skb headroom: 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Wed Apr 19 02:02:36 2023 kern.err kernel: [22855.488453] skb headroom: 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Wed Apr 19 02:02:36 2023 kern.err kernel: [22855.496102] skb headroom: 00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I get the following, after more than 24 hours uptime (xx:xx:xx:xx:xx:xx) is the same randomized MAC address in all cases):
Wed Apr 19 12:44:48 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Wed Apr 19 12:44:48 2023 daemon.notice hostapd: wlan0: STA-OPMODE-N_SS-CHANGED xx:xx:xx:xx:xx:xx 1
Wed Apr 19 12:44:48 2023 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Wed Apr 19 12:44:48 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx
Wed Apr 19 12:44:48 2023 daemon.notice hostapd: wlan1: Prune association for xx:xx:xx:xx:xx:xx
Wed Apr 19 12:44:48 2023 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Wed Apr 19 12:44:48 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Wed Apr 19 12:44:48 2023 daemon.info hostapd: wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 4)
Wed Apr 19 12:44:48 2023 daemon.notice hostapd: wlan1: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx
Wed Apr 19 12:44:48 2023 daemon.notice hostapd: wlan0: Prune association for xx:xx:xx:xx:xx:xx
Wed Apr 19 12:44:48 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Wed Apr 19 12:44:50 2023 kern.info kernel: [151808.290544] ath10k_pci 0000:00:00.0: mac flush vdev 0 drop 0 queues 0x1 ar->paused: 0x0 arvif->paused: 0x0
Wed Apr 19 12:45:18 2023 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Apr 19 12:47:21 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Wed Apr 19 12:47:21 2023 daemon.notice hostapd: wlan0: STA-OPMODE-N_SS-CHANGED xx:xx:xx:xx:xx:xx 1
Wed Apr 19 12:47:21 2023 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Wed Apr 19 12:47:21 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx
Wed Apr 19 12:47:21 2023 daemon.notice hostapd: wlan1: Prune association for xx:xx:xx:xx:xx:xx
Wed Apr 19 12:47:21 2023 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Wed Apr 19 12:47:51 2023 daemon.info hostapd: wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Apr 19 12:51:05 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Wed Apr 19 12:51:05 2023 daemon.info hostapd: wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 4)
Wed Apr 19 12:51:05 2023 daemon.notice hostapd: wlan1: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx
Wed Apr 19 12:51:05 2023 daemon.notice hostapd: wlan0: Prune association for xx:xx:xx:xx:xx:xx
Wed Apr 19 12:51:05 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Wed Apr 19 12:51:07 2023 kern.info kernel: [152185.703852] ath10k_pci 0000:00:00.0: mac flush vdev 0 drop 0 queues 0x1 ar->paused: 0x0 arvif->paused: 0x0
Wed Apr 19 12:51:35 2023 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Apr 19 12:52:39 2023 daemon.warn odhcpd[1904]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Wed Apr 19 12:52:52 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Wed Apr 19 12:52:52 2023 daemon.notice hostapd: wlan0: STA-OPMODE-N_SS-CHANGED xx:xx:xx:xx:xx:xx 1
Wed Apr 19 12:52:52 2023 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Wed Apr 19 12:52:52 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx
Wed Apr 19 12:52:52 2023 daemon.notice hostapd: wlan1: Prune association for xx:xx:xx:xx:xx:xx
Wed Apr 19 12:52:52 2023 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Wed Apr 19 12:53:06 2023 user.info : luci: accepted login on / for root from <somewhere>
Wed Apr 19 12:53:22 2023 daemon.info hostapd: wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Upgraded a Xiaomi ax3200 and a Xiaomi r3g v1. Everything works great!
Got the same issue.
x86-64 image builder is broken.
Downloading file:packages/Packages
Updated list of available packages in /home/aparcar/asu/worker1/cache/22.03.3/x86/64/build_dir/target-x86_64_musl/root-x86/../../../../../../../../../../../home/aparcar/asu/worker1/cache/22.03.3/x86/64/dl/imagebuilder
Downloading file:packages/Packages.sig
Signature check failed.
Remove wrong Signature file.
What log visualization tool is that?
Just noticed that I'm also getting this since the upgrade on Archer A7 v5, it just didn't really stand out in the Syslog (which is crowded with dnsmasq notices). My syslog holds about a day full of messages currently, with only one instance of the kernel warning retained (out of ~50 in the kernel log since boot). There is some key-associated events, but messages deviate from the linked thread quite significantly.
Also, the same preceding system log messages about fa:xxxxxx show up multiple times without being followed by the kernel warning...
Wed Apr 19 22:37:47 2023 daemon.info hostapd: wlan1: STA fa:xxxxxx IEEE 802.11: authenticated
Wed Apr 19 22:37:47 2023 daemon.info hostapd: wlan1: STA fa:xxxxxx IEEE 802.11: associated (aid 4)
Wed Apr 19 22:37:47 2023 daemon.notice hostapd: wlan0: Prune association for fa:xxxxxx
Wed Apr 19 22:37:47 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED fa:xxxxxx
Wed Apr 19 22:37:47 2023 daemon.notice hostapd: wlan1: AP-STA-CONNECTED fa:xxxxxx
Wed Apr 19 22:37:47 2023 daemon.info hostapd: wlan1: STA fa:xxxxxx WPA: pairwise key handshake completed (RSN)
Wed Apr 19 22:37:47 2023 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED fa:xxxxxx
Wed Apr 19 22:37:54 2023 kern.warn kernel: [361389.009204] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
Wed Apr 19 22:37:54 2023 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
1 Like
Is anyone using a raspberry pi 4 as a router on a stick? I suspect it has something to do with that as that is the only thing special about eth0.10.
So the mainline kernels 6.2.12, 6.1.25, 5.15.108, 5.10.178, 5.4.241, 4.14 have removed the offending code to the prior state before the whole UBI issue cropped up, so the localized Openwrt patch can either stay as disclosed at kernel.org or it reverts back to the mainline builds without the change. Either way, the 21.x, 22.x, snapshots, and future 23.x built on these kernels or later addresses the fault.
2 Likes
Ye I'm running it on Raspberry Pi 4B No issues at all.
(see my earlier post)
Cudy WR2100 update without problems. But lost wifi 2ghz after some days. Reboot required.
I upgraded my E8450 safely via sysupgrade, but my openclash [v0.45.112-beta] (https://github.com/vernesong/OpenClash/releases/tag/v0.45.112-beta) appears to be gone and requires reinstallation? I guess all the dependencies would require reinstallation too.
Thats not an issue, just sysupgrade works differently than you expected: any custom applications (opkg or custom uploaded files) need to be reinstalled manually after a sysupgrade. Sysupgrade only preserves config files of certain defined OpenWRT config folders.
You could alternatively create a custom firmware file via „attended sysupgrade“, this will on top preserve any custom software packages that came from opkg sources.
Since you were responding to another post that was due to an UBI issue: note that the „UBI“ problem that is mentioned in this thread a couple of times without much context is a different story. It is related to a bug in the Linux kernels used in OpenWRT 21.02.6 and 22.03.4: a faulty UBI code patch had made it into those Linux kernels.
UBI is used as flash filesystem on some (not all) OpenWRT devices, the bug prevents some of these devices from properly booting.
Looks like another OpenWRT update is in discussion to solve that.
3 Likes
Is there an upshot, or at least an attempt at one, on the excessive logging for various Archer C7 models as mentioned above? After a week, I figure someone must have figured out something about it. I have a v2 that I'm holding off doing for now just in case.
1 Like
Many thanks. Is there any cheat sheet in creating this "attended sysupgrade" firmware file? Is it difficult? Reinstalling those dependencies and the openclash ipk is not too bad. I was surprised to see though the main setup within openclash itself seems to be still there, incl. the various subscriptions.
OpenWrt FW 22.03.4 update on a Swissonic Professional Router 2 MKII with internal Totolink X5000R board went smooth from the previous FW 22.03.3, thanks for this.
Nevertheless, may that is down to my own fault, but all the previous additional ports were not recognized after flashing to the new version and I had to reinstall all of them manually afterwards.
Luckily all my individual config files, were still present and usable right afterwards.
All these packages have been missing after the FW update:
luci-theme-openwrt
curl
wget-ssl
tcpdump
bridge
luci-proto-relay
adblock
luci-app-adblock
luci-i18n-adblock-en
smartDNS
luci-app-smartdns
luci-app-dcwapd
dcstad
dcwapd
wifischedule
luci-i18n-wifischedule-en
luci-app-ntpc
DNSmasq
kmod-ipvlan
kmod-macvlan
kmod-sched-act-vlan
As I say, this is may my own fault not being to familiar with updating my router, since this was my 1st time.
Would be nice to make it more clear how to take care about on how to include any installed ports right with the update, or at least mark this individual installed packages as due for update instead of ignoring them.
Apart from that I'm very happy with the new release, thanks a bunch. 
Hello aparcar,
I have yet to see any official stance or communication about this, but we still do not have a announcement e-mail for this release yet. The openwrt-announce Archives still shows no activity since January.
https://lists.openwrt.org/pipermail/openwrt-announce/
And it is now eight days since the release of 22.03.4.
Can this please be corrected sooner than later?
I would think that seeing as how there are eleven security vulnerabilities fixed that this would be a very important release for users to know about. Had I not causally checked the OpenWRT web site wondering if there had been an update, I would have missed this. Undoubtedly there are OpenWRT users who rely on the annoucement e-mail and do not know about this new release.
You are a bit off topic here, but I'll send you in the right direction. Most functions and features in OpenWRT have a documentation page, including what you are asking about. And yes, all that documentation can be overwhelming to look and sift through when you are just starting to use and learn OpenWRT. I recommend searching for only what you need in the moment to correct your issue. It keeps the overwhelm of information down.
The start documentation page has a search feature and field within it. Searching for the following string will bring it right up:
attended sysupgrade
Another good way of finding what you need is to use a your favorite internet search engine and use the search string:
openwrt <topic of interest, or issue>
In this specific example, it would be:
openwrt attended sysupgrade
As user Pico said, this is normal and expected behavior from sysupgrade, though admittedly confusing for new users that don't expect this. Attenended sysupgrade will preserve all those user installed packages and dependencies. And yes, it is easy and saves a lot of time and effort. Though it won't help you until the next stable release. You'll have to manually install all the extra packages for this release since you already used sysupgrade.
I also recommend you keep a saved list of all the user installed packages you need in a text file with a space between each name. This will save you in this particular circumstance, and also if for some reason you need to make a fresh image install. The advantage being that you already know exactly what you need to install, and if you SSH into OpenWRT, you can quickly install multiple software packages with one command via the opkg command. Copying and pasting that list of user installed packages into the Terminal after the correct opkg command is very quick.
While I love using a good graphical user interface (GUI), LuCI does not have a way to install multiple software packages at once.
If you have further questions about this, please create a new support post in correct area of the forum.
2 Likes
Duplicate:
Maybe https://downloads.openwrt.org/releases/22.03.4/targets/mvebu/cortexa9/marvell_a385-db-ap-squashfs-sysupgrade.bin would work for WRT3200ACM? It is the same processor model and target. Does anyone know?