OpenWrt 22.03.4 service release

Upgraded TP-Link Archer C7 v2 to 22.03.4 via luci. Things mostly seem to be ok, except I now see this entry in syslog every few minutes:

ath10k_pci 0000:00:00.0: mac flush vdev 0 drop 0 queues 0x1 ar->paused: 0x0 arvif->paused: 0x0

I'm seeing the same on a TP-Link Archer C7 v4

kern.info kernel: [49696.489344] ath10k_pci 0000:00:00.0: mac flush vdev 0 drop 0 queues 0x1 ar->paused: 0x0 arvif->paused: 0x0

Wow this update :laughing:

One device got corrupted - I kept settings when I was asked and it looked like update was success... Only when I started digging did I see my wifi was miss configured entirely - wrong channel selected , maximum output power reduced to 20mw and can't be increased ( yes , I did check and the country is set to correct location )

Sometimes it would lock me out of luci too... Kept saying wrong password when I tried connecting , had to close browser entirely and reset ssh tunnel ( page refresh didn't work )

The other device ended with broken luci... I thought it was a smart idea to NOT keep any settings , but it failed to clear settings properly during update...

Instead of router using default 192.168.1.1 for lan it was using 192.168.10.1 ( I set it to this on the previous version ) , but luci couldn't be reached at all on that address either ( Had to use reset button on the router )

Both devices are mt7621...

Same R7800

Two days ago I have updated two Archer C7 V5 without any problem. Everything is working without any issue so far. Thanks OpenWrt

„A man needs a name“ (quoting Jaqen H'ghar).
The device maintainers might then have a chance to take a look at it. The chip platform name does not help.

1 Like

Is there an ongoing rebuild of 22.03.4 packages? The x86-64 image builder is currently failing to download the libopenssl1 package.

1 Like

Nice quote.

Still no support for the WRT3200ACM?

5 Likes

I have upgraded ASUS Lyra (MAP-AC2200) from a former snapshot to 22.03.4. It booted after the upgrade, so it is not affected by the mentioned kernel regression. I have not tested the general functionallity other than logged into Luci.

For you and others who have mentioned this, does it really never subside? Dozens an hour indefinitely?

Is it preceded by lines similar to this thread?

If so, the last message seems to point to "rekeying," whatever that implies.

It never goes away completely. It does "subside" somewhat during periods of lower network activity. You can see this log snapshot/graph from Papertrail showing instances of the log message over the past 48 hours - the period when the house is mostly asleep has the lowest incidence.

ETA: Also, it is not preceded by the lines you mentioned, nor does it occur in conjunction with any other log entries.

2 Likes

@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?

Papertrail's free plan: https://www.papertrail.com/

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.