RE: Error in rtw89 using Kernel 7.1.4

Adrodoc <[email protected]> wrote:
> Continuing to use 6.6.9-arch1-1 was a good idea. I did get an error
> today: https://github.com/user-attachments/files/30747862/2026-08-05.15.51.12.6.6.9-arch1-1.log

This is also a SER L1 " SER catches error: 0x1000".

> Unlike errors on other kernel version I didn't notice the disconnect
> here. I just saw this error in the log by accident afterwards. I was
> in a zoom call during the error, so I would have expected to notice
> any disconnects. Maybe the recovery is much faster in this kernel
> version?

Even it does recovery very fast. I expect you still can see the log
if connection happened. 

> 
> The output looks very similar, so I believe this is the same error,
> but I am not 100% sure. For example the message "firmware failed to
> ack for leaving ps mode" is not present here, but maybe that message
> was added to the driver code later.
> 
> Also interesting: there was no message like "wlan0: disassociated" or
> "wlan0: authenticate" after the error. Maybe there was just no
> disconnect despite the error, which would explain why I did not notice
> a problem until I randomly looked at the log.

I'd summarize the cases you met:

1. SER L1
   It is just a notification from firmware to driver, so we'd ignore this.

2. "firmware failed to ack for leaving ps mode"
   Please try to disable power save parameters mentioned by previous mail.

3. disconnection
   I think this is major problem you want to fix. If so, bisect kernel
   to address this.

   By the way, the first log you shared shows that disconnection happened
   after SER L1 about 50 seconds. SER L1 seems not a related event.
   More, the disconnection might depend on AP you are connecting, so 
   keep the experiments in the same environments if possible.

Ping-Ke