[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d06be6c6-f5b7-4259-b76a-20dc52a5ffd3@amd.com>
Date: Tue, 9 Dec 2025 21:42:21 -0600
From: Mario Limonciello <mario.limonciello@....com>
To: Askar Safin <safinaskar@...il.com>
Cc: chris.feng@...iatek.com,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
chetan.kumar@...iatek.com, hua.yang@...iatek.com, len.brown@...el.com,
liang.lu@...iatek.com, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, pavel@....cz, rafael@...nel.org,
stable@...nel.org, ting.wang@...iatek.com,
regressions <regressions@...ts.linux.dev>,
DellClientKernel <Dell.Client.Kernel@...l.com>
Subject: Re: [REGRESSION][BISECTED] "Wakeup event detected during hibernation"
on Dell Precision 7780 (was "[PATCH v4] PM: hibernate: Avoid missing wakeup
events during hibernation")
On 12/9/2025 12:02 AM, Askar Safin wrote:
> On Tue, Oct 21, 2025 at 5:29 PM Mario Limonciello
> <mario.limonciello@....com> wrote:
>> To me it sounds like it's potentially the same root cause for the early
>> suspend wakeup as well as the hibernate wakeup.
>
> Adding "gpiolib_acpi.ignore_wake=VEN_0488:00@355" or
> "gpiolib_acpi.ignore_wake=INTC1085:00@355"
> doesn't fix this bug.
>
>> Are you closing the lid
>> and putting the laptop in a bag or putting anything on top of it?
>
> No. I just click "Hibernate" button using touchpad in GUI, and hibernate fails.
>
Can you try using command line instead in case it's actually the
touchpad click still being registered?
> I just did some printf-debugging. Results:
>
> We call
> https://elixir.bootlin.com/linux/v6.18/source/kernel/power/hibernate.c#L870 ,
> it calls
> https://elixir.bootlin.com/linux/v6.18/source/kernel/power/hibernate.c#L723 ,
> it calls
> https://elixir.bootlin.com/linux/v6.18/source/kernel/power/hibernate.c#L636 ,
> it calls dpm_suspend
> https://elixir.bootlin.com/linux/v6.18/source/drivers/base/power/main.c#L2265 ,
> that dpm_suspend returns error, and this error leads to
> "Wakeup event detected during hibernation" message.
>
> Any further pointers? How to debug?
>
If you haven't already; turn on /sys/power/pm_debug_messages and
/sys/power/pm_print_times.
This should help clarify the last functions that are run and any debug
level PM related messages that are emitted that lead to the failure.
You can also check /sys/power/pm_wakeup_irq after the failure to confirm
which interrupt woke the system (assuming that was the source of the
early wakeup event).
Powered by blists - more mailing lists