public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: LB F <goainwo@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next] wifi: rtw88: add quirks to disable PCI ASPM and deep LPS for HP P3S95EA#ACB
Date: Tue, 17 Mar 2026 01:31:37 +0000	[thread overview]
Message-ID: <c4b1b177a7a04e11b89c6f67166ef409@realtek.com> (raw)
In-Reply-To: <CALdGYqTbH1NVW7HT8JaUJ2xay5190WmpOm1TH7YJP9LfoHoFLw@mail.gmail.com>

LB F <goainwo@gmail.com> wrote:
> 
> Ping-Ke Shih <pkshih@realtek.com> wrote:
> > On an HP laptop (P3S95EA#ACB) equipped with a Realtek RTL8821CE 802.11ac
> > PCIe adapter (PCI ID: 10ec:c821), the system experiences a hard lockup
> > (complete freeze of the UI and kernel, sysrq doesn't work, requires
> > holding the power button) when the WiFi adapter enters the power
> > saving state. Disable PCI ASPM to avoid system freeze.
> > In addition, driver throws messages periodically. Though this doesn't
> > always cause unstable connection, missing H2C commands might cause
> > unpredictable results. Disable deep LPS to avoid this as well.
> 
> Tested on HP Notebook P3S95EA#ACB (kernel 6.19.7-1-cachyos):
> 
>   - No hard freeze observed during idle or active usage.
>   - Zero h2c or lps errors in dmesg across idle (10 min),
>     load stress (100MB download), and suspend/resume cycle.
>   - Both quirk flags confirmed active via sysfs without any
>     manual modprobe parameters.

Thanks for your test. I'd add this information to commit message
during getting merged. 

> 
> Tested-by: Oleksandr Havrylov <goainwo@gmail.com>
> 

As well as your Tested-by.

Ping-Ke


      reply	other threads:[~2026-03-17  1:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16  3:56 [PATCH rtw-next] wifi: rtw88: add quirks to disable PCI ASPM and deep LPS for HP P3S95EA#ACB Ping-Ke Shih
2026-03-17  0:48 ` LB F
2026-03-17  1:31   ` 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=c4b1b177a7a04e11b89c6f67166ef409@realtek.com \
    --to=pkshih@realtek.com \
    --cc=goainwo@gmail.com \
    --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