From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ej1-f48.google.com (mail-ej1-f48.google.com [209.85.218.48]) (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 C830734751C for ; Sat, 28 Mar 2026 15:55:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.218.48 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774713341; cv=none; b=UEvC+hw3gtM3/uoygwQe2CWijWNJCahM0QMfLN6sslL0nV5YWa+RrrTrzz4JSH8e8IemmvaOyAp6kxgdWCCgGYttJrRvVn5fmEHf5YTBnpY1z7/el3Vpy8OYkDSCW8mxtzFNPPxeftj63A3kNmWnwfRfKvV9Ntqtbtafz3Fr8B8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774713341; c=relaxed/simple; bh=DvZxylFcHruvbPeEYKBDnW4krrtPrW1e6CzdanuSK0s=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=XcCHztOYKf5Xat5KFweNOhB0tj6K3BP82XU+VABuVOb2iSWuimEjzkOCMFgYc17aPxjthQsYhNAHV06eHXo7XdvIAFPjn7d2VI/3UcpW4HQLMeqx971zGo5hlEAKUaEcicqP8GswMuiGEvP5+iEPijr+CJBHwGC6IYitGFeCErs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=TKgkL4Bo; arc=none smtp.client-ip=209.85.218.48 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="TKgkL4Bo" Received: by mail-ej1-f48.google.com with SMTP id a640c23a62f3a-b9b1ffbb9f5so383472866b.2 for ; Sat, 28 Mar 2026 08:55:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1774713338; x=1775318138; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=h5H8gCTp/IRDQQxZGW/iIFZfQLZCVS/4MhsWoyOCHpA=; b=TKgkL4BoKWn7Dw/kPV19DYR0DOKMU3oaTaVb52jVU26/ElAKhg3CTbEW2phnTN8Ro/ bzQUkOprVeufw7BRklz1nwn/+dapUrfMomXvDtN6u6wP31/QOB74t/lpAQ2ezlzsjJTp IX7kYmH3QZkyLBGYkTq5LrCj4kx/qK5r6zr0RWfgnLbTnbEB0NKWVPab60fxldJbDKt9 87YCTKN6veGXEKwwYIi24oaHS9z27oJcABbbJ2xEGC5r+akhYdZmWuKJmf2oAtE5IDju WlT78yUNTI6m+vgCbHdnFA5GeoX1S8FLdCRUJR3iOtJMEX+f89bucKpMgo2H8jtAdJ37 o9UQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1774713338; x=1775318138; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=h5H8gCTp/IRDQQxZGW/iIFZfQLZCVS/4MhsWoyOCHpA=; b=CDGn5R0BWg34LsheEL5A5XLlHBTw1JYnS7HMflAm6C3Ct+UTWnej8oCO08Kmcx2nl8 6F9xqHbw7PlXLXEoBP/BjsuzekQt3F85+fsZwhVoAabxEyMozG3Ml+PKBTeVqLpETKvP qQj7BRjAafoE5jN2gruoBwA1VekwvMslyNp7IGMQgQvZwRQ6eHsdsKAGUgKLuy6KARgT 4FsBfmE0fI8FMPiCR7odG4zgLfFWhydNHwsrgyU1e4mUBxCnzI4RoZcAVMaZx2wSX8Ab 1Kqko/EnArcc2nfr/DZT7KNGkg71qGq+qIxSdCc2VaTLigOpl9DPIkPkqc/JhuCAD1CP kWmQ== X-Forwarded-Encrypted: i=1; AJvYcCUbTdXWhfNLpMFqY/uT5N9r4gAUiWWZ/v6Fusw28JXE8BnKf0mqJoEZHOQLxlWioJQVq3A0nGv0W3sdJQA=@vger.kernel.org X-Gm-Message-State: AOJu0Yyo5/LkY6SNtOIhs/G33azN0ubjP9SGrBCsDZAEyC/dVBmVqanw 7PKS7zIOHGmrLCYMn0fUAuhRRyjLm09P5Y0BDCqkz5KDn0d+lyssKXnxk78fRA== X-Gm-Gg: ATEYQzzUwrDCas+DkJ2O1gnUejQcLrt794FZ5E0r8xnHTymQ+bU99ORMXXQRiLIJXwx Ee7cRhEg48+OL7HNB5Y48ZtE/GqfY/bVbiHrKYwTsZLBx8znlShvjfXi0aEX/v3zEzubsYbkQIT LmkaCGO1/G/3gu1NnuwHSh54cd+5vMR35TPnpWabhvMoxsleQsv8g11L+JqbY7av4i4hgoGIWUM aJPh0Rl+ktPfxxblPVvvEGFMuF3UPY9DCnqdBtdUmAjVnZSZWph74LgTyCGp+k+gs5SsixCeJFx gZeFiHvL6KfanrvXouIftv9l/aavX/Or50qKqfkB7ksnEo/vU9M0hOnn7+EV1hn7D7MFyBaqjrk XEYz6M9nLG8xHC5yodvLRbIZELyCd1G+H2b9F58IZzsNkwenxyBcyHdu/lV0NbahFE/ReAANR+B BuLfLCMcZ/WXyMJUAz9pUdv9sXk+h5H3tTpZhyGxRX X-Received: by 2002:a05:600c:8485:b0:487:1fc:14f9 with SMTP id 5b1f17b1804b1-48727d77c8fmr103560685e9.15.1774703228845; Sat, 28 Mar 2026 06:07:08 -0700 (PDT) Received: from [192.168.1.50] ([81.196.40.93]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-48722be608bsm204120235e9.0.2026.03.28.06.07.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 28 Mar 2026 06:07:08 -0700 (PDT) Message-ID: <5eb90d6d-e590-4c9e-91c8-1ba315f45304@gmail.com> Date: Sat, 28 Mar 2026 15:07:06 +0200 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [BUG] wifi: rtw88: Hard system freeze on RTL8821CE when power_save is enabled (LPS/ASPM conflict) To: LB F Cc: Ping-Ke Shih , "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" References: Content-Language: en-US From: Bitterblue Smith In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 28/03/2026 13:41, LB F wrote: > Hi Bitterblue, > > Apologies for the delayed response. I applied your diagnostic patch > right away but held off on replying because the NULL pointer crash > has not reproduced since — it has been over 36 hours now with no > oops, which is unusual (previously it occurred in 4 out of 7 boots, > typically within 2 minutes to 24 hours). > > I wanted to wait and collect the hex dumps from the crash-time burst > (the 50+ "unused phy status page" events that always preceded the > oops), as those would be the most valuable. Unfortunately, the crash > hasn't happened yet during this session. If/when it does, I will > follow up immediately with those dumps. > > In the meantime, here is what I have so far. The patch is working > and producing output. I collected 76 "unused phy status page" events > during this boot, with the following time distribution: > > 14:01 1 event (isolated) > 16:33 1 event > 16:57-17:00 73 events (burst over ~3 minutes, no crash followed) > 00:03 1 event (isolated) > > Page number distribution (no page 0 or 1, all are "garbage" pages): > > page 10: 10 page 7: 8 page 8: 7 page 13: 7 > page 11: 7 page 9: 6 page 15: 6 page 12: 6 > page 4: 5 page 2: 5 page 14: 4 page 5: 2 > page 3: 2 page 6: 1 > > Here are representative hex dumps. I'm showing the byte-level dump > (second print_hex_dump) since it is easier to read: > > Isolated event (page 9): > > rtw_8821ce 0000:13:00.0: unused phy status page (9) > 00000000: c7 5e 9c 9d 91 69 4d dc b0 67 c2 09 84 33 00 00 .^...iM..g...3.. > 00000010: 00 1e fe 3f cf f2 f0 08 01 29 00 00 00 11 2a 01 ...?.....)....*. > 00000020: 0e 00 00 00 00 00 00 20 ....... > > Burst event (page 14): > > rtw_8821ce 0000:13:00.0: unused phy status page (14) > 00000000: bd 2c e0 3d 00 00 00 11 87 0a 40 80 88 33 00 00 .,.=......@..3.. > 00000010: 00 1e fe 3f 3e b6 9b 44 01 2e 00 00 00 11 2a 01 ...?>..D......*. > 00000020: 20 00 00 00 00 00 00 20 ...... > > Burst event (page 12) — byte 0x10 is 0x7e instead of usual 0x00: > > rtw_8821ce 0000:13:00.0: unused phy status page (12) > 00000000: 1c b3 7f 15 d1 94 95 7e 70 5e f4 e3 b4 a1 bf 10 .......~p^...... > 00000010: 7e 1e fe 3f 2e f1 62 44 01 2c 00 00 00 11 2a 01 ~..?..bD.,....*. > 00000020: 14 00 00 00 00 00 00 20 ....... > > Burst event (page 2) — contains MAC addresses: > > rtw_8821ce 0000:13:00.0: unused phy status page (2) > 00000000: 88 55 51 95 d1 66 ad 50 2f 25 3f 89 ae 35 ef 77 .UQ..f.P/%?..5.w > 00000010: 00 1e fe 3f 89 68 62 4d 88 42 40 00 8c c8 4b 68 ...?.hbM.B@...Kh > 00000020: d1 63 6c 68 a4 1c 97 5b .clh...[ > > Note: bytes 0x1a-0x1f are 8c:c8:4b:68:d1:63 — my adapter's MAC. > bytes 0x20-0x25 are 6c:68:a4:1c:97:5b — the AP's BSSID (partially, > the dump is only 40 bytes so it cuts off after 0x25). > > Burst event (page 15) — completely random, no recognizable structure: > > rtw_8821ce 0000:13:00.0: unused phy status page (15) > 00000000: c6 a1 92 1c a7 68 6b 97 12 bd ad 89 30 98 ab 94 .....hk.....0... > 00000010: 00 1e fe 3f ec 3f 3e 44 1f c2 91 41 0e 9b 54 5f ...?.?>D...A..T_ > 00000020: 30 eb 40 18 6f d3 25 62 0.@.o.%b > > Burst event (page 10) — offset 0x10 is completely different pattern: > > rtw_8821ce 0000:13:00.0: unused phy status page (10) > 00000000: cb 1c 2a df f1 69 d0 05 58 c0 e8 0e d0 59 87 6e ..*..i..X....Y.n > 00000010: 63 7e 56 f0 95 fa b8 d3 d5 4b 3e fa b0 0c 0e be c~V......K>..... > 00000020: 42 28 14 89 15 c1 fd ad B(...... > > Last isolated event (page 4): > > rtw_8821ce 0000:13:00.0: unused phy status page (4) > 00000000: 97 ee fa 4e 04 90 00 21 c0 0f 89 80 b3 33 00 00 ...N...!.....3.. > 00000010: 00 1e fe 3f 97 7e 64 90 5d 3e 74 fa 70 e0 39 65 ...?.~d.]>t.p.9e > 00000020: 48 a4 40 d3 de a9 85 15 H.@..... > > Observations: > > - Bytes at offset 0x0e-0x0f are usually 00 00 or have low values > in most dumps, but some are completely random. > - Bytes 0x11-0x13 are almost always 1e fe 3f (with byte 0x10 > being 00 or 7e), suggesting this is a consistent part of the > RX descriptor that is not corrupted. > - The "page 2" dump at 17:00:23 clearly contains the adapter > and AP MAC addresses, confirming this is real RX frame data. > - Some dumps (page 10, page 5, page 15) have completely random > data with no recognizable RX descriptor structure at all. > - The 73-event burst at 16:57-17:00 happened over ~3 minutes but > did NOT result in a crash this time. Previously, similar bursts > of 50+ events within ~1 second always led to the NULL pointer > dereference in rtw_fw_c2h_cmd_handle+0x127. > > I will keep monitoring and will send the crash-time dumps as soon as > the oops reproduces. > > Thanks for looking into this. > > Best regards, > Oleksandr Havrylov The other print_hex_dump is important too, so please attach the full dmesg. You don't need to wait for a crash. It appears to be caused by random data, so I don't expect those dumps to be more useful than these. Of course, adding a NULL check like you said before is a good idea. The one dump that contains your MAC addresses has them 24 bytes lower than they are supposed to be.