[BUG] arm: wlcore: wl18xx: connection timeout after resuming from suspend

[BUG] arm: wlcore: wl18xx: connection timeout after resuming from suspend

[petter]

Hi,

When I bumped from Linux 6.6 to 6.9 or later, I have issues with wifi 
after resuming from suspend on my am335x (Beagle Bone Black wireless) 
board.

When the wifi starts up it just repeats with

[ 183.118816] PM: suspend entry (deep)
[ 183.128244] Filesystems sync: 0.005 seconds
[ 183.158165] Freezing user space processes
[ 183.167546] Freezing user space processes completed (elapsed 0.005 
seconds) [ 183.174835] OOM killer disabled.
[ 183.178082] Freezing remaining freezable tasks [ 183.184998] Freezing 
remaining freezable tasks completed (elapsed 0.002 seconds)
[ 183.192636] printk: Suspending console(s) (use no_console_suspend to 
debug) [ 183.206858] wlan0: deauthenticating from d8:07:b6:83:ae:56 by 
local choice (Reason: 3=DEAUTH_LEAVING) [ 183.293875] wlcore: down [ 
183.296231] wlcore: down
[ 183.444907] Disabling non-boot CPUs ...
[ 183.444975] pm33xx pm33xx: PM: Successfully put all powerdomains to 
target state
[ 183.444975] PM: Wakeup source UART
[ 184.159782] wlcore: PHY firmware version: Rev 8.2.0.0.243 [ 
184.262260] wlcore: firmware booted (Rev 8.9.0.0.83) [ 184.408702] OOM 
killer enabled.
[ 184.412231] Restarting tasks ... done.
[ 184.441020] random: crng reseeded on system resumption
[ 184.708905] wlan0: authenticate with d8:07:b6:83:ad:be
[ 184.865164] wlan0: send auth to d8:07:b6:83:ad:be (try 1/3)
...
[ 184.865164] wlan0: send auth to d8:07:b6:83:ad:be (try 2/3)
...
[ 184.865164] wlan0: send auth to d8:07:b6:83:ad:be (try 3/3)
..
timeout...

then repeats.. Only way to make it work again is to restart the board. 
This works perfectly fine in Linux 6.6.. Any ideas what might have 
changed in later kernels that might affect the wifi after rtcwake usage?

Some tries to bisect the issues points to

5797b1c18919 workqueue: Implement system-wide nr_active enforcement for 
unbound workqueues

But that might just be due to some timing issues caused by changed 
behavior in workqueue of the driver?

Any suggestions for how to troubleshoot this further is welcomed.

BR Petter