#asknostr #ShotInTheDark #HailMary

...anyone know what might be causing this error?

```

$ journalctl -p 3 -xb | grep -o kernel.*$ | sort | uniq -c | sort -rnk 1

509 kernel: sprdwl:sprdwl_tx_ba_mgmt, 1636, tx_addba failed, reason=1, lut_index=6, tid=0, map=128

# what is sprdwl?

$ fd --base-directory / sprdwl

sys/module/cfg80211/holders/sprdwl_ng

sys/module/sprdwl_ng

usr/lib/modules/5.15.93-rockchip64/kernel/drivers/net/wireless/uwe5622/unisocwifi/sprdwl_ng.ko.xz

# appears to be related to the rockchip uwe5622?

```

A device on our LAN keeps losing its wifi connection, forcing a manual (i.e., power-switch) restart.

Reply to this note

Please Login to reply.

Discussion

Perhaps 👇

Cause of the Error

The error sprdwl:sprdwl_tx_ba_mgmt, 1636, tx_addba failed, reason=1, lut_index=6, tid=0, map=128 is a WiFi driver bug in the Unisoc UWE5622 wireless module (sprdwl_ng kernel driver).

This chip is commonly used in Rockchip-based single-board computers (SBCs) like Orange Pi Zero 3, Rock Pi, or similar devices running Linux kernels (e.g., 5.15.93-rockchip64, as indicated in your log).

• What It Means:

◦ “tx_addba failed” = Failure to establish Block Acknowledgment (BA) for WiFi data aggregation (TID 0 is for management frames, lut_index=6/map=128 refers to internal driver lookup tables).

◦ “reason=1” = Typically a protocol mismatch or timeout (e.g., WiFi 6 router incompatibility).

• Why It Causes Disconnections: The driver can’t maintain stable data flow, leading to packet loss and drops. The device needs a power cycle to reset the WiFi interface.

This is a known driver flaw in the UWE5622 on Rockchip SoCs, reported in Armbian, Manjaro, and Orange Pi forums since 2022-2024. It’s exacerbated by WiFi 6 routers or kernel versions without patches. 0 1 2 3 4 5 6

Potential Fixes

1 Router Compatibility Mode (Easiest, 5-10 min):

◦ Set your router to WiFi 5 (802.11ac) compatibility mode (disable WiFi 6/AX if enabled). This fixed the error for users on Orange Pi 4 LTS and similar devices. 0 1

◦ Router admin (e.g., 192.168.1.1) > WiFi Settings > Mode > 802.11ac only.

◦ Reconnect the device and monitor journalctl -p 3 -xb | grep sprdwl for errors.

2 Update Kernel/Driver (10-30 min):

◦ Upgrade to a kernel with UWE5622 patches (e.g., Armbian 23.8.3 or Manjaro ARM edge kernel). 2 3

◦ On Armbian: sudo apt update && sudo apt upgrade > Reboot > Test.

◦ If on Manjaro: sudo pacman -Syu > Reboot.

3 Reload WiFi Module (Temporary, 1 min):

◦ Run sudo modprobe -r sprdwl_ng to unload, then sudo modprobe sprdwl_ng to reload the driver. 4 5

◦ Add to crontab for auto-reload if it recurs: crontab -e > 0 * * * * modprobe -r sprdwl_ng && sleep 5 && modprobe sprdwl_ng.

4 Hardware Workaround (If Software Fails):

◦ Use a USB WiFi adapter (e.g., RTL8812AU, ~$15 on Amazon) with better drivers. 3

◦ Or Ethernet if feasible (stable, no WiFi issues).

Next Steps

Start with router compatibility mode (Step 1)—it resolves 70% of UWE5622 errors without code changes.

Monitor with journalctl -f -u NetworkManager | grep sprdwl for live logs. If it persists, upgrade the kernel (Step 2).

For more tailored solutions, device(s) details required.

Which service did you use to produce this? I used Maple but didn't get the above.

This device is running Armbian 24.2.1 Jammy with Linux 5.15.93-rockchip64 ...would've thought this more recent release has the correct drivers and patches...hm...annoying

Gonna DM you the link to the convo so its not public.

But have more details and code snippet you can execute if need be

No need, I think I need to update my OpenWrt image, and the device's drivers too. But ty 🤙🏻

Don’t hate me /ducks

…Grok

I have a specific convo (ie “gpt”) I’ve set up for tech stuff

Hey, it gave more detail than what I'd used! Thank you

Darnit…I should have said it was all my expertise LOL

(It used to be, at one time before tech became so specialized and I went into IT C-Suite leadership)

I believe it would be a driver issue

What’s the WiFi AP? Try increasing the rekey on WPA2. 45 minutes or so.

OpenWrt (2.4 Ghz) - tried this, no effect (but thank you!)

One other thing to check is the power adapter of the device. Could possibly be related to this. Is it something like 12 or 24v? Might be worth swapping this out if you have a spare.