From: sashiko-bot@kernel.org
To: "Denis Benato" <denis.benato@linux.dev>, linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/1] PCI: Disable D3cold for Killer BE200-family WiFi on MSI Claw A1M
Date: Sun, 25 Oct 2026 23:30:39 +0000 [thread overview]
Message-ID: <sashiko-outbox-184522@kernel.org> (raw)
In-Reply-To: <20261025231813.128649-2-denis.benato@linux.dev>
> During s2idle the platform removes power from the WiFi slot (D3cold).
> The Killer BE1750 (Intel BE200, 8086:272b) installed in the MSI Claw A1M
> fails to resume from that state: the PCIe link does not retrain
> ("pcieport 0000:00:1c.0: Data Link Layer Link Active not set in
> 100 msec") and every device register reads back as 0xffffffff, so the
> card disappears from the bus and the machine must be power-cycled.
>
> Keeping the device in D3hot with the link in L1.2 during system sleep
> makes suspend and resume work reliably: the package still reaches >99%
> S0ix residency and the card survives every cycle (verified over multiple
> suspend/resume tests with an RTC-timed wake).
>
> Disable D3cold for the BE200-family device on this board. This mirrors
> the udev-level workaround distributions already ship for the AX200/AX210
> (8086:2725), which suffers from the same class of problem, and moves it
> into the kernel where it belongs.
>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=220223
> Signed-off-by: Denis Benato <denis.benato@linux.dev>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261025231813.128649-1-denis.benato@linux.dev?part=1
next prev parent reply other threads:[~2026-10-25 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 23:18 [PATCH 0/1] PCI: Disable D3cold for Killer BE200-family WiFi on MSI Claw A1M Denis Benato
2026-10-25 23:18 ` [PATCH 1/1] " Denis Benato
2026-10-25 23:30 ` sashiko-bot [this message]
2026-10-26 18:48 ` Bjorn Helgaas
2026-10-26 19:09 ` Denis Benato
2026-10-26 20:23 ` Grumbach, Emmanuel
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=sashiko-outbox-184522@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=denis.benato@linux.dev \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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