From: lofm2605 <lofm2605@gmail.com>
To: "Rafael J . Wysocki" <rafael@kernel.org>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
VU TUNG LAM <lofm2605@gmail.com>
Subject: [PATCH] ACPI: PM: Add unused power resource quirk for THUNDEROBOT 911Pro
Date: Sun, 11 Oct 2026 12:44:55 +0700 [thread overview]
Message-ID: <20261011054455.1472-1-lofm2605@gmail.com> (raw)
From: VU TUNG LAM <lofm2605@gmail.com>
On the THUNDEROBOT 911Pro laptop (board NLCC, BIOS TP127), the NVMe
drive in the CPU-attached M.2 slot (0000:02:00.0, behind root port
00:01.1) and the discrete NVIDIA GPU (0000:01:00.0) are inaccessible
after boot:
nvme 0000:02:00.0: Unable to change power state from D3cold to D0, device inaccessible
nvme 0000:02:00.0: error -ENODEV: probe failed
snd_hda_intel 0000:01:00.1: Unable to change power state from D3cold to D0, device inaccessible
Both devices are enumerated normally and work under Windows. This is
the same symptom as on the THUNDEROBOT ZERO, a sibling Tiger Lake-H +
RTX 3060 model, which was fixed by commit cd7ef20ba8c6 ("ACPI: PM: Add
unused power resource quirk for THUNDEROBOT ZERO"). The SSDT with OEM
Table ID "TglH_Rvp" on this machine defines PXP_ power resources in the
same way, but the existing quirk only matches product names containing
"ZERO".
Add a DMI entry for the 911Pro so that its unused power resources are
left on, as is done for the ZERO.
Fixes: a1224f34d72a ("ACPI: PM: Check states of power resources during initialization")
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=222118
Assisted-by: LLM
Signed-off-by: LamVU <lofm2605@gmail.com>
---
Not tested: I have not been able to build and boot a kernel with this
change yet. The failure was observed with Ubuntu's 7.0.0-31-generic
kernel, which already contains cd7ef20ba8c6. I can test a patched
kernel and boot with dyndbg="file drivers/acpi/power.c +p" if needed.
drivers/acpi/power.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/drivers/acpi/power.c b/drivers/acpi/power.c
--- a/drivers/acpi/power.c
+++ b/drivers/acpi/power.c
@@ -1121,6 +1121,20 @@ static const struct dmi_system_id dmi_leave_unused_power_resources_on[] = {
}
},
+ {
+ /*
+ * THUNDEROBOT 911Pro (board NLCC): same SSDT bug as the
+ * THUNDEROBOT ZERO above. Power resource 'PXP' is turned off
+ * as unused during initialization, which makes the NVMe drive
+ * in the CPU-attached M.2 slot and the NVIDIA dGPU
+ * inaccessible.
+ */
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "THUNDEROBOT"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "911Pro"),
+ DMI_MATCH(DMI_BOARD_NAME, "NLCC"),
+ },
+ },
{}
};
reply other threads:[~2026-10-11 5:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261011054455.1472-1-lofm2605@gmail.com \
--to=lofm2605@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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
all inboxes | Powered by JetHome®