From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Francesco Lauritano <francesco.lauritano1@protonmail.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Mika Westerberg <westeri@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpiolib: acpi: Disable edge events on boot on ASUS ROG Strix G16 G614PP
Date: Sun, 28 Dec 2025 22:15:06 +0200 [thread overview]
Message-ID: <aVGPysQghxHGaJ2r@smile.fi.intel.com> (raw)
In-Reply-To: <X9fJuqzxIBzuhcbjDFYBPSScoKnUpKLe13znKYaJkJpgmjcbfF6_RN2_24ksQq0Hwyvy9pVrnL7_vHEarnQyUBC0zBLmhlvp75nNhgmq7OI=@protonmail.com>
On Wed, Dec 17, 2025 at 02:01:51PM +0000, Francesco Lauritano wrote:
>
> Thanks for looking into this. Happy to dig deeper.
>
> Here are the requested dumps (boot with initcall_debug, no workaround):
(Usually we also use `ignore_loglevel`, but I think dmesg should have it anyway.)
> dmesg: https://gist.github.com/kylan11/63ec3ec319cd6bcaa043fa0b1366965a
>
> acpidump: https://gist.githubusercontent.com/kylan11/7956bbf75714265107f0886f6ed2a381/raw/1614845eb1dc6ab7e2effb6fe56b585a746abe4f/gistfile1.txt
> Some quick notes:
> - The AMD GPIO controller probes successfully (LINE 2077)
>
> - The hang occurs in the deferred IRQ handler (line 2960)
>
> - There are some ACPI errors around 0.285373 to 0.289806, though they complete quickly
This looks like related to USB4 (thubderbolt) dock? Mika, does it look familiar?
> - After the 36-second hang, everything else initializes normally.
> touchpad, audio, wifi, nvidia GPU all work fine.
>
> The ACPI tables show there's a _AEI method under \_SB_GPIO. Not sure if those
> unresolved GPP2/GPP7 references are related to what's blocking the deferred
> IRQ handler, or if it's something else entirely.
>
> Let me know if you need anything else or want me to test something specific.
>
> On Wednesday, December 17th, 2025 at 2:08 PM, Mika Westerberg <mika.westerberg@linux.intel.com> wrote:
> > On Wed, Dec 17, 2025 at 12:01:52PM +0000, francesco.lauritano1@protonmail.com wrote:
> >
> > > On the ASUS ROG Strix G16 G614PP (2025), the kernel can stall for ~36
> > > seconds during late init in acpi_gpio_handle_deferred_request_irqs().
> > >
> > > Booting with gpiolib_acpi.run_edge_events_on_boot=0 avoids the stall and
> > > restores normal boot times.
> >
> > Okay but it might just accidentally "work" and hides the real issue. Doing
> > things like this blindly might end up breaking something that relies on
> > that _AEI.
> >
> > Can you post full dmesg and acpipdump somewhere so we can try to figure out
> > what is going on?
> > > Link: https://lore.kernel.org/platform-driver-x86/6iFCwGH2vssb7NRUTWGpkubGMNbgIlBHSz40z8ZsezjxngXpoiiRiJaijviNvhiDAGIr43bfUmdxLmxYoHDjyft4DgwFc3Pnu5hzPguTa0s=@protonmail.com/
Not sure what this means. Maybe better tag like Closes should be used?
> > > Tested-by: Francesco Lauritano francesco.lauritano1@protonmail.com
This is implied that the author of the patch tested it before sending.
> > > Signed-off-by: Francesco Lauritano francesco.lauritano1@protonmail.com
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-12-28 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2kSCn4XaoXsXJ3EUR0syTdmip8Z1cBuUr0Br4sFVnwnsA8q4GlhiHOmsJkeBxvxYoLnetp4r44wIPXw42yTAFl-BtMROnIwR-NkckKgA5EY=@protonmail.com>
2025-12-17 10:06 ` [BUG] 36-second boot delay due to by acpi_gpio_handle_deferred_request_irqs on ASUS ROG Strix G16 (2025) Francesco Lauritano
2025-12-17 12:01 ` [PATCH] gpiolib: acpi: Disable edge events on boot on ASUS ROG Strix G16 G614PP francesco.lauritano1
2025-12-17 13:08 ` Mika Westerberg
2025-12-17 14:01 ` Francesco Lauritano
2025-12-28 20:15 ` Andy Shevchenko [this message]
2025-12-17 14:23 ` [BUG] 36-second boot delay due to by acpi_gpio_handle_deferred_request_irqs on ASUS ROG Strix G16 (2025) Mario Limonciello
2025-12-17 15:12 ` Francesco Lauritano
2025-12-17 16:57 ` Francesco Lauritano
2025-12-17 18:01 ` Mario Limonciello
2025-12-17 19:19 ` Francesco Lauritano
2025-12-18 6:39 ` Mika Westerberg
2025-12-18 10:33 ` Hans de Goede
2025-12-18 10:38 ` Mika Westerberg
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=aVGPysQghxHGaJ2r@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--cc=francesco.lauritano1@protonmail.com \
--cc=linusw@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=westeri@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