Re: [REGRESSION][BISECTED] "Wakeup event detected during hibernation" on Dell Precision 7780 (was "[PATCH v4] PM: hibernate: Avoid missing wakeup events during hibernation")

[Mario Limonciello <mario.limonciello@amd.com>]

On 10/21/2025 7:54 AM, Askar Safin wrote:
> Chris Feng <chris.feng@mediatek.com>:
>> Wakeup events that occur in the hibernation process's
>> hibernation_platform_enter() cannot wake up the system. Although the
>> current hibernation framework will execute part of the recovery process
>> after a wakeup event occurs, it ultimately performs a shutdown operation
>> because the system does not check the return value of
>> hibernation_platform_enter(). In short, if a wakeup event occurs before
>> putting the system into the final low-power state, it will be missed.
>>
>> To solve this problem, check the return value of
>> hibernation_platform_enter(). When it returns -EAGAIN or -EBUSY (indicate
>> the occurrence of a wakeup event), execute the hibernation recovery
>> process, discard the previously saved image, and ultimately return to the
>> working state.
> 
> #regzbot introduced: 0c4cae1bc00d31c78858c184ede351baea232bdb
> 
> Hibernation doesn't work on my laptop.
> 
> My laptop is Dell Precision 7780.
> 
> Hibernation starts, then aborts. dmesg contains:
> 
> [   28.283320] PM: hibernation: Wakeup event detected during hibernation, rolling back.
> 
> I did bisect. The bug reproduces starting with 0c4cae1bc00d.
> 
> The bug still reproduces on v6.18-rc2.
> 
> Note: there is another problem with PM on my laptop, which is tracked here:
> https://lore.kernel.org/all/197ae95ffd8.dc819e60457077.7692120488609091556@zohomail.com/ .
> 
> So I always revert 1796f808e4bb in my kernels.
> 
> But this doesn't prevent this hibernation bug.
> 
> In other words, this hibernation bug still happens on v6.18-rc2 even
> with 1796f808e4bb reverted.
> 
> Steps to reproduce:
> 1. Power off laptop, then power on
> 2. Hibernate ("sudo systemctl hibernate")
> 
> Hibernate will not work.
> 
> Note that to reproduce the bug you need power off laptop, and then power on
> it in step 1. Merely reboot doesn't cause bug. I. e. reproducibilty
> depends on whether last boot was reboot or cold power on.
> 
> Also: suspend works normally (assuming I reverted 1796f808e4bb), but hibernate
> doesn't.
> 
> This is "dmesg --level=debug+" on v6.18-rc2-with-1796f808e4bb-reverted:
> 
> https://zerobin.net/?0459f6411446622d#8i0Ifo6o68By3+UlYUr2t2KL7YLXsKEXrkfszpE77Rw=
> 
> This is config of this kernel:
> 
> https://zerobin.net/?04e89ceab8284c1d#9bpaZKqVXFSaeav/WW6GOCwD4i3SozzQ8pBEJ6LWwVM=
> 

To me it sounds like it's potentially the same root cause for the early 
suspend wakeup as well as the hibernate wakeup.

Assuming the GPIO pointed out in that other thread 
(https://lore.kernel.org/all/20250918183336.5633-1-safinaskar@gmail.com/) 
is indeed the touchpad GPIO I had a suspicion.  Are you closing the lid 
and putting the laptop in a bag or putting anything on top of it?

I wonder if the touchpad is not disabled by the hardware and getting 
pressure through the lid and physically clicking/activating.

I've seen this exact issue occur on a Framework 16 as well.  The 
workaround is to disable wakeup from touchpad before suspend/hibernate.