From: Ping-Ke Shih <pkshih@realtek.com>
To: LB F <goainwo@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict)
Date: Fri, 20 Mar 2026 02:02:17 +0000 [thread overview]
Message-ID: <a8e187e1b40e4a35bbeb3bc3a3d21821@realtek.com> (raw)
In-Reply-To: <CALdGYqSd61wxNrPDui+m-S+Na_is-RM18-=L6xm-Jf4QQ+-DOg@mail.gmail.com>
LB F <goainwo@gmail.com> wrote:
> Ping-Ke Shih <pkshih@realtek.com> wrote:
> > Not sure what hardware get wrong. Let's validate rate when reading
> > from hardware. Since 1M rate can only 20MHz, I set it together.
> > Please help to test below. I suppose you can see "weird rate=xxx",
> > but "WARNING: net/mac80211/rx.c:5491" disappears.
>
> Hi Ping-Ke,
>
> I can confirm your patch works as expected. Here are the full results.
>
> --- Test environment ---
>
> Kernel: 6.19.7-1-cachyos
> Patch: your rate validation patch applied to rtw_rx_query_rx_desc(),
> on top of the v2 DMI quirk (ASPM + LPS Deep disabled)
>
> --- Captured log (relevant excerpt) ---
>
> [ 43.046] input: Soundcore Q10i (AVRCP) <-- BT headset connected
> [ 111.551] rtw_8821ce 0000:13:00.0: unused phy status page (13)
> [ 111.635] weird rate=101
> [ 111.635] rtw_8821ce 0000:13:00.0: unused phy status page (7)
> [ 111.741] weird rate=102
> [ 115.045] weird rate=98
> [ 118.371] weird rate=104
>
> --- Analysis ---
>
> 1. Timing: the anomalous events began approximately 68 seconds after
> the Bluetooth A2DP headset (Soundcore Q10i) established its
> connection. No anomalies were observed before BT connected.
>
> 2. Multiple invalid rate values were captured, not just 0x65:
>
> weird rate=101 (0x65)
> weird rate=102 (0x66)
> weird rate=98 (0x62)
> weird rate=104 (0x68)
>
> All four values exceed DESC_RATE_MAX (0x53 = 83 decimal). This
> suggests the hardware occasionally reports a range of out-of-bounds
> rate values during BT/Wi-Fi coexistence, not a single fixed value.
>
> 3. The "unused phy status page" messages (pages 13 and 7) appeared
> immediately before and alongside the "weird rate" events. As noted
> in my previous message, only pages 0 and 1 are expected. This
> further suggests the firmware leaks internal coexistence state
> into the RX ring during BT antenna arbitration.
>
> 4. Most importantly: the WARNING: net/mac80211/rx.c:5491 did NOT
> appear anywhere in the log. Your rate clamping patch successfully
> intercepts the out-of-bounds values before they propagate to
> mac80211, preventing the invalid VHT NSS=0 warning entirely.
>
> --- Conclusion ---
>
> Your patch achieves the intended result. The "weird rate" printk
> confirms the hardware is the source of the invalid values (occurring
> during BT coexistence), and the mac80211 WARNING is suppressed.
>
> Please let me know if you need any additional data or further testing.
I'll send formal patch (Cc you) for the invalid VHT NSS=0, but not to
handle "unused phy status page". Please give me Tested-by tag on the
patch after I send it.
Ping-Ke
next prev parent reply other threads:[~2026-03-20 2:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 21:48 [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict) LB F
2026-03-10 2:02 ` Ping-Ke Shih
2026-03-10 11:01 ` LB F
2026-03-10 15:12 ` LB F
2026-03-11 2:20 ` Ping-Ke Shih
2026-03-11 2:15 ` Ping-Ke Shih
2026-03-11 2:22 ` Ping-Ke Shih
2026-03-11 11:00 ` LB F
2026-03-11 15:22 ` LB F
2026-03-12 1:56 ` Ping-Ke Shih
2026-03-12 21:42 ` LB F
2026-03-13 0:03 ` LB F
2026-03-13 0:29 ` LB F
2026-03-14 10:52 ` LB F
2026-03-14 12:39 ` LB F
2026-03-15 0:24 ` LB F
2026-03-16 2:55 ` Ping-Ke Shih
2026-03-16 20:27 ` LB F
2026-03-17 1:28 ` Ping-Ke Shih
2026-03-18 0:00 ` LB F
2026-03-18 0:58 ` Ping-Ke Shih
2026-03-18 23:55 ` LB F
2026-03-19 0:22 ` LB F
2026-03-19 0:49 ` Ping-Ke Shih
2026-03-19 1:24 ` Ping-Ke Shih
2026-03-19 23:58 ` LB F
2026-03-20 0:41 ` LB F
2026-03-20 1:00 ` Ping-Ke Shih
2026-03-20 1:19 ` LB F
2026-03-20 2:02 ` Ping-Ke Shih [this message]
2026-03-21 12:07 ` LB F
2026-03-23 2:01 ` Ping-Ke Shih
2026-03-25 20:38 ` LB F
2026-03-26 23:52 ` LB F
2026-03-16 2:50 ` 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=a8e187e1b40e4a35bbeb3bc3a3d21821@realtek.com \
--to=pkshih@realtek.com \
--cc=goainwo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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