From nobody Mon Apr 6 20:10:53 2026 Received: from rtits2.realtek.com.tw (rtits2.realtek.com [211.75.126.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4A908149C6F; Wed, 18 Mar 2026 00:58:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=211.75.126.72 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773795534; cv=none; b=niuLjIiy68ErA/fpIkbaYuUJ2IFTYXEymz51tAhB76OHAuRfkuv84qvJ4TJaxR0IJiG0UfHKpJ5118dCULr3s6VPCWYLpshJscAZ2eIOi9ABtNj0UZ4HVpJwPE6Q2wW/7LwOQuCfZgA9QGmp0D36hXnc2TVJvK5JKMaCibKeqL0= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773795534; c=relaxed/simple; bh=YlTT5m2+thgBlad5I2qjDQPKVLambcx1RoJpX3rqyWI=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=T8Nh2PcoXT13yAgeGZOF5urtR4pAuFoWXLD0hTuJZ9dbyidnuPkTsUBUzz/eDkwogZogIF3IOdsihUbUoHE5nrgbH/ZTyzPac06clMLIXooRMuvlGjJURA/wE/P1m0LqVr4pqREbLkzFD2MAcsXnvRkXOLJFyr5t9CW2+M/AzAA= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=realtek.com; spf=pass smtp.mailfrom=realtek.com; dkim=pass (2048-bit key) header.d=realtek.com header.i=@realtek.com header.b=S2OsSqXl; arc=none smtp.client-ip=211.75.126.72 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=realtek.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=realtek.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=realtek.com header.i=@realtek.com header.b="S2OsSqXl" X-SpamFilter-By: ArmorX SpamTrap 5.80 with qID 62I0wmJM3781169, This message is accepted by code: ctloc85258 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=realtek.com; s=dkim; t=1773795528; bh=YlTT5m2+thgBlad5I2qjDQPKVLambcx1RoJpX3rqyWI=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=S2OsSqXlB9Bg5aZ//FKhY48uqLBMY2abegEHAZY/k/QVJF7tqq97FBQXE9EF9vIu8 oEC+soogGBpLYyXebJu9Yw/PrO8RiHinybv4fjnj1uG1wcF+i7SQWNHfnZcUPo93V9 rMYKz53V4ArfTgjXDTQR+gGr8zgET6nmoT6w7M85eBXeMW0oqRHT8N68ypR5uRX6QX FJwjgTykAbAFDWemktagLTsymEnEOq2rLbtprWURyog8WGw3joYyDH+sCeVEXp5B9N eTQrdK4ceGRWzihbboi2nY9N7GZzw8gGs/G/QCWsE4Z1GH1fX6r9RpW2NZcI/EKdW3 lsZU6vNVkAg0g== Received: from mail.realtek.com (rtkexhmbs02.realtek.com.tw[172.21.6.41]) by rtits2.realtek.com.tw (8.15.2/3.21/5.94) with ESMTPS id 62I0wmJM3781169 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 18 Mar 2026 08:58:48 +0800 Received: from RTKEXHMBS06.realtek.com.tw (10.21.1.56) by RTKEXHMBS02.realtek.com.tw (172.21.6.41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.10; Wed, 18 Mar 2026 08:58:48 +0800 Received: from RTKEXHMBS06.realtek.com.tw ([fe80::4cbd:6c6c:b92b:3913]) by RTKEXHMBS06.realtek.com.tw ([fe80::4cbd:6c6c:b92b:3913%10]) with mapi id 15.02.1748.010; Wed, 18 Mar 2026 08:58:48 +0800 From: Ping-Ke Shih To: LB F CC: "linux-wireless@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) Thread-Topic: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict) Thread-Index: AQHcsA6WTRRnBRFJhEKVxaR7JwwWq7Wm+M9wgAAbfgCAAX9nAIAAB6mAgAAK64CAAElZAIABMBnAgADMOgCAACdjAIAAB1+AgAJAYICAAB3nAIAAxOYAgAJBRiCAAKEnAIAA2QBQgAD06wCAAJVNMA== Date: Wed, 18 Mar 2026 00:58:48 +0000 Message-ID: References: <1e96af437fa24674b353ddb530b2d8e7@realtek.com> <792645eed36041f0b3df951f1b28a08a@realtek.com> <458ed80e39734ea99610050140bb31ce@realtek.com> <1bd495ffe57c47eb827eec084729afa2@realtek.com> In-Reply-To: Accept-Language: en-US, zh-TW Content-Language: zh-TW Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 LB F wrote: > Ping-Ke Shih wrote: > > To reproduce this reliable, you need to remove driver ko and mac80211.k= o, > > and reinstall them. > > > > However, you have confirmed this is the symptom. I think only if you > > want to dig why the rate reported by hardware is weird, otherwise we > > can ignore this warning. >=20 > Following your suggestion, I performed a full stack reload including > mac80211.ko and cfg80211.ko, and was able to reproduce the warning: >=20 > [152.226055] Rate marked as a VHT rate but data is invalid: MCS: 0, NSS= : 0 > [152.226057] WARNING: net/mac80211/rx.c:5491 at > ieee80211_rx_list+0x177/0x1020 [mac80211] > [152.226336] CPU: 2 UID: 0 PID: 638 Comm: irq/56-rtw_pci Tainted: G > IOE 6.19.7-1-cachyos > [152.226344] Hardware name: HP HP Notebook/81F0, BIOS F.50 11/20/2020 >=20 > One observation worth mentioning: the warning triggered approximately > 72 seconds after initial association, coinciding with a Bluetooth > device connecting to the system. This may suggest the NSS=3D0 condition > occurs during BT coexistence negotiation rather than during normal > WiFi traffic. I am not sure if this is relevant, but I wanted to > mention it in case it helps narrow down the root cause. >=20 > I also noticed the offset is now +0x177, which matches exactly what > you showed from v6.19.6. The earlier +0x183 was likely an artifact of > CachyOS's LTO optimizations while mac80211 had been resident for a > long time. >=20 > As you noted, this appears to be a separate issue from the freeze and > h2c timeout problems, so I leave it to your judgment whether it > warrants further investigation. I add a printk to show the case VHT and NSS=3D=3D0 as below. Please help to collect the output, and then I can see what it happened.=20 diff --git a/drivers/net/wireless/realtek/rtw88/rx.c b/drivers/net/wireless= /realtek/rtw88/rx.c index 8b0afaaffaa0..a4e3a3bce748 100644 --- a/drivers/net/wireless/realtek/rtw88/rx.c +++ b/drivers/net/wireless/realtek/rtw88/rx.c @@ -230,6 +230,11 @@ static void rtw_rx_fill_rx_status(struct rtw_dev *rtwd= ev, &rx_status->nss); } + if (rx_status->encoding =3D=3D RX_ENC_VHT && rx_status->nss =3D=3D = 0) { + printk("VHT NSS=3D0 pkt_stat->rate=3D0x%x rx_status->band= =3D%d rx_status->rate_idx=3D%d\n", + pkt_stat->rate, rx_status->band, rx_status->rate_id= x); + } + rx_status->flag |=3D RX_FLAG_MACTIME_START; rx_status->mactime =3D pkt_stat->tsf_low; >=20 > --- >=20 > I would like to take this opportunity to thank you sincerely for your > time, patience, and expertise throughout this whole process. From your > very first response to the final v2 patch, your guidance made it > possible to properly identify and resolve a bug that had been causing > real frustration for users of this hardware for a long time. I also thanks for your time and help. :) Ping-Ke