From: sashiko-bot@kernel.org
To: "Ryan Brue" <ryanbrue.dev@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v4] pci: Add broken-GPE quirk for some Lenovo Legions with Nvidia GPUs
Date: Tue, 10 Nov 2026 21:33:01 +0000 [thread overview]
Message-ID: <sashiko-outbox-207770@kernel.org> (raw)
In-Reply-To: <20261110-broken-gpe-legion-v4-1-c672bb1c4d91@gmail.com>
> From: Lyude Paul <lyude@redhat.com>
>
> On certain Lenovo Legion devices (including the 16APH8, 16AHP9, and
> 15AHP9), the firmware appears to enjoy firing a GPE on the parent PCIe
> port of the nvidia GPU very shortly after the GPU enters D3Cold. This means
> that every time the GPU is runtime suspended, ACPI firmware immediately
> wakes up its parent PCIe port, which then wakes up the GPU. Once it falls
> asleep again, the cycle repeats.
>
> Note, this bug doesn't require Nvidia's driver. It happens on nouveau and
> nova as well, and it even seems possible for this to happen without any
> driver loaded.
>
> This seems to simply be a bug. Luckily, there is nothing that we actually
> need ACPI wakeup events for on the GPU. Events such as display connector
> hotplug events in D3Cold come through as ACPI_VIDEO events which aren't
> affected by this quirk.
>
> Reported-by: Ryan Brue <ryanbrue.dev@gmail.com>
> Link: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/905
> Co-developed-by: Ryan Brue <ryanbrue.dev@gmail.com>
> Signed-off-by: Ryan Brue <ryanbrue.dev@gmail.com>
> Signed-off-by: Lyude Paul <lyude@redhat.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110-broken-gpe-legion-v4-1-c672bb1c4d91@gmail.com?part=1
next prev parent reply other threads:[~2026-11-10 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 21:24 [PATCH v4] pci: Add broken-GPE quirk for some Lenovo Legions with Nvidia GPUs Ryan Brue
2026-11-10 21:25 ` Ryan Brue
2026-11-10 21:33 ` sashiko-bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-10 21:23 Ryan Brue
2026-11-10 21:33 ` sashiko-bot
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-207770@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=ryanbrue.dev@gmail.com \
--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