From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
Chris Vitalos <cvitalos@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: rtw89_8852bte (RTL8852BE-VT): recurring SER 0x1000/0x4000/0x1001/0x1002 on fw 0.29.122.1/.2; question on rtw8852bt_fw-1.bin
Date: Thu, 12 Nov 2026 00:28:38 +0000 [thread overview]
Message-ID: <4c9f8c150753483bbed78337885732a7@realtek.com> (raw)
In-Reply-To: <3eb642b4-a3cb-4b21-9dbd-aa6880593b57@gmail.com>
Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> On 11/11/2026 02:57, Ping-Ke Shih wrote:
> >
> > Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> >> Someone else ran into the same problem (I think) and captured four
> >> crashes with your patch. dmesg output is attached.
> >
> > I'd like to confirm the problem you encountered was also connection
> > becomes not usable?
>
> The user says there is no other problem, just the crashes.
>
> I forgot to link the report earlier:
>
> https://github.com/morrownr/rtw89/issues/98#issuecomment-6726071832
The "crash" is SER L1 that firmware detects abnormal, recovers, and
notifies driver. But it looks a little frequent:
Sun Nov 8 19:46:31 2026
Sun Nov 8 19:47:40 2026
Sun Nov 8 20:40:46 2026
Sun Nov 8 21:09:07 2026
Sun Nov 8 21:10:55 2026
We are analyzing the log. Please give us some time.
prev parent reply other threads:[~2026-11-12 0:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 0:43 rtw89_8852bte (RTL8852BE-VT): recurring SER 0x1000/0x4000/0x1001/0x1002 on fw 0.29.122.1/.2; question on rtw8852bt_fw-1.bin Chris Vitalos
2026-11-02 1:50 ` Ping-Ke Shih
2026-11-03 0:39 ` Chris Vitalos
2026-11-03 1:18 ` Ping-Ke Shih
2026-11-10 14:05 ` Bitterblue Smith
2026-11-11 0:57 ` Ping-Ke Shih
2026-11-11 12:00 ` Bitterblue Smith
2026-11-12 0:28 ` Ping-Ke Shih [this message]
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=4c9f8c150753483bbed78337885732a7@realtek.com \
--to=pkshih@realtek.com \
--cc=cvitalos@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.com \
/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