From: Ping-Ke Shih <pkshih@realtek.com>
To: Adrodoc <adrodoc55@googlemail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: Error in rtw89 using Kernel 7.1.4
Date: Tue, 11 Aug 2026 01:48:45 +0000 [thread overview]
Message-ID: <c52840cf65464f659635eec6fcd6de12@realtek.com> (raw)
In-Reply-To: <CAOQMLZUbZhNhOQyxGXW7YSOU-z6w-4jWqfqVkaeMhdx2kLDrmg@mail.gmail.com>
Adrodoc <adrodoc55@googlemail.com> wrote:
> > 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.
For later experiments (such as kernel 6.6.9), did you also confirm this after
SER happened? Maybe, you can a ping with timestamp in background:
ping 8.8.8.8 | while read dt; do echo "$(date '+%Y-%m-%d %H:%M:%S') - $dt"; done
> > 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.
The path to debug SER dump is longer, because I personally don't understand
the numbers, so I will need internal experts to help analyzing your feedback.
Since RTL8852AE is earlier chip, the progress will be slower. So be patient
if we choose this way.
Personally I prefer to bisect kernel first (though it takes time too).
If the cause isn't from driver side, let's move to debug SER dump.
next prev parent reply other threads:[~2026-08-11 1:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 14:35 Error in rtw89 using Kernel 7.1.4 Adrodoc
2026-07-28 0:50 ` Ping-Ke Shih
2026-07-28 1:07 ` Ping-Ke Shih
2026-07-28 9:22 ` Adrodoc
2026-07-28 17:55 ` Adrodoc
2026-07-29 0:35 ` Ping-Ke Shih
2026-07-29 8:50 ` Adrodoc
2026-07-29 8:59 ` Adrodoc
2026-08-04 17:12 ` Adrodoc
2026-08-05 1:35 ` Ping-Ke Shih
2026-08-05 8:43 ` Adrodoc
2026-08-05 14:30 ` Adrodoc
2026-08-10 5:36 ` Ping-Ke Shih
2026-08-10 9:50 ` Adrodoc
2026-08-11 1:48 ` Ping-Ke Shih [this message]
2026-08-10 4:01 ` Ping-Ke Shih
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c52840cf65464f659635eec6fcd6de12@realtek.com \
--to=pkshih@realtek.com \
--cc=adrodoc55@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox