Hi Phuc,
On Mon, 16 Mar 2026 at 12:25, <[email protected]> wrote:
> > TL;DR it depends on kernel config.
> > With my .config, your patch is not needed (but it doesn't hurt).
> > With your .config, your patch is needed.
> > Unfortunately I haven't found yet which config options causes this.
> > I will send you my .config by personal email.
>
> Thank you for sharing your configuration file. I noticed there are
> numerous differences between our configurations. After further
> investigation, I narrowed down the main cause to the following debug
> options:
>
> CONFIG_PROVE_LOCKING=n
>
> CONFIG_DEBUG_LOCK_ALLOC=n
>
> CONFIG_DEBUG_RT_MUTEXES=n
>
> CONFIG_DEBUG_SPINLOCK=n
>
> CONFIG_DEBUG_MUTEXES=n
>
> CONFIG_DEBUG_WW_MUTEX_SLOWPATH=n
>
> CONFIG_DEBUG_RWSEMS=n
>
> CONFIG_DEBUG_LOCKING_API_SELFTESTS=n
>
> CONFIG_LOCK_STAT=n
>
> CONFIG_DEBUG_ATOMIC_SLEEP=n
>
>
> These options are enabled in your configuration but disabled in mine.
> Enabling these debug features introduces additional overhead, which
> slows down the resume process. This delay unintentionally provides
> enough time for the hardware to generate the Frame End interrupt,
> effectively masking the issue on your system.
Thank you, that explains the difference!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
