Re: Error in rtw89 using Kernel 7.1.4

Adrodoc <[email protected]>
Newsgroups org.kernel.vger.linux-wireless
Message-ID <CAOQMLZUbZhNhOQyxGXW7YSOU-z6w-4jWqfqVkaeMhdx2kLDrmg@mail.gmail.com>
> SER L1 ("SER catches error: 0x1000") means firmware detect and fix an error already, and notify driver it does (driver no need to do anything). Therefore, I'd suggest to ignore this message if it doesn't bother your daily use.

Ok, that's good to know.

> 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.

I am pretty sure SER L1 (or maybe "firmware failed to ack for leaving
ps mode") is a relevant event, because the connection was not
functioning properly during these 50 seconds.

> More, the disconnection might depend on AP you are connecting, so keep the experiments in the same environments if possible.

I only have one access point and all experiments so far were on the
same computer using the same router.

> Yes, it is worth to try by setting
> iw dev wlan0 set power_save off

1. I'll try disabling power save on the newest kernel now.
2. If that doesn't help I'll try disabling ASPM-related features.
3. If that also doesn't work I'll go back to bisecting the kernel and
will ignore SER L1 from now on.

> The second way is to debug on the latest kernel and apply debug patch to dump more detail needed by internal experts. But it seems like this is still uncertain because of hardware flaw they mentioned.

Is that still an option? I think it might yield results faster. Since
I have to keep a kernel running for about a day to make sure it
doesn't have the disconnect issue, bisecting will take quite some
time.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.