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: Mon, 16 Mar 2026 02:55:57 +0000 [thread overview]
Message-ID: <1bd495ffe57c47eb827eec084729afa2@realtek.com> (raw)
In-Reply-To: <CALdGYqSf66mBiufysr3tjm74A_w98LRN50fik0U9WGVvkBJ_5g@mail.gmail.com>
LB F <goainwo@gmail.com> wrote:
>
> Oleksandr Havrylov <goainwo@gmail.com> wrote:
> > After extended testing with your DMI patch applied, the hard freeze is
> > gone. However, with ASPM disabled but LPS Deep still active, I observe
> > periodic h2c timeouts during idle which cause occasional WiFi throughput
> > drops and Bluetooth audio stuttering. When I additionally set
> > disable_lps_deep=Y, all symptoms disappear completely. This confirms
> > that combining the ASPM quirk with dynamic LPS_DEEP_MODE_NONE would be
> > the complete fix. Ready to test an updated patch if you decide to
> > include this.
>
> Hi Ping-Ke,
>
> While monitoring logs with the current patch applied, I noticed two
> things that might be useful.
>
> First, the following message appears each time the driver loads:
>
> rtw88_8821ce 0000:13:00.0: can't disable ASPM; OS doesn't have ASPM control
>
> This suggests the BIOS retains control over ASPM and prevents any
> OS-level override via pci_disable_link_state(). The system remains
> stable regardless, which confirms that the rtw_pci_disable_aspm flag
> approach in your patch is the correct and effective method here.
Not sure if this is because PCIE bridge has no ASPM capability?
>
> Second, during normal operation I observe this warning periodically:
>
> WARNING: net/mac80211/rx.c:5491 at ieee80211_rx_list+0x177/0x1020 [mac80211]
LN5491 (kernel v6.19.6) is:
case RX_ENC_VHT:
if (WARN_ONCE(status->rate_idx > 11 ||
!status->nss ||
status->nss > 8,
"Rate marked as a VHT rate but data is invalid: MCS: %d, NSS: %d\n",
status->rate_idx, status->nss))
goto drop;
break;
Looks like driver reports improper VHT nss/rate? But this warns once, and
you message isn't like this.
Could you check the source code LN5491 you are using?
Ping-Ke
next prev parent reply other threads:[~2026-03-16 2:56 UTC|newest]
Thread overview: 60+ 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 [this message]
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
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-27 10:52 ` Bitterblue Smith
2026-03-28 11:41 ` LB F
2026-03-28 13:07 ` Bitterblue Smith
2026-03-28 13:40 ` LB F
2026-03-28 18:52 ` Bitterblue Smith
2026-03-28 20:59 ` LB F
2026-03-28 21:31 ` LB F
2026-03-28 21:53 ` LB F
2026-03-30 1:23 ` Ping-Ke Shih
2026-03-30 11:34 ` LB F
2026-03-31 0:32 ` Ping-Ke Shih
2026-04-03 21:47 ` LB F
2026-04-04 10:44 ` LB F
2026-04-06 12:41 ` LB F
2026-04-08 14:26 ` Bitterblue Smith
2026-04-26 20:38 ` Bitterblue Smith
2026-04-26 23:17 ` LB F
2026-04-27 0:26 ` LB F
2026-04-27 10:08 ` LB F
2026-04-27 21:19 ` LB F
2026-04-27 21:30 ` Bitterblue Smith
2026-04-27 21:48 ` LB F
2026-04-27 22:25 ` LB F
2026-04-29 20:13 ` LB F
2026-04-30 10:56 ` 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=1bd495ffe57c47eb827eec084729afa2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.