linux-kernel - Re: Regression: system freeze on resume from suspend introduced by printk per-console suspended state

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aYCEL905vRkBlU5D@pathway>
Date: Mon, 2 Feb 2026 12:02:07 +0100
From: Petr Mladek <pmladek@...e.com>
To: ysard <ysard_git@....fr>
Cc: John Ogness <john.ogness@...utronix.de>, linux-kernel@...r.kernel.org,
	senozhatsky@...omium.org
Subject: Re: Regression: system freeze on resume from suspend introduced by
 printk per-console suspended state

On Sat 2026-01-31 23:22:09, ysard wrote:
> Here are the logs, debug_console_lock is disabled 4 seconds after each test
> to avoid consuming the 100 reports (kworker events are frequent here).
>
> > It would be nice to provide three logs with this patch:
> >
> >    1. console_lock() API called by
> >        echo suspend >/proc/driver/nvidia/suspend
> 
> [   65.417500] [     T88] printk: console lock API call [1]: console_lock() by pid=88, comm=kworker/4:1+events
> [   65.417581] [     T88] printk: console lock API call [2]: console_unlock() by pid=88, comm=kworker/4:1+events
> [   74.984380] [     T88] printk: console lock API call [3]: console_lock() by pid=88, comm=kworker/4:1+events
> [   74.984450] [     T88] printk: console lock API call [4]: console_unlock() by pid=88, comm=kworker/4:1+events
> [   75.134088] [     T88] printk: console lock API call [5]: console_lock() by pid=88, comm=kworker/4:1+events
> [   75.134289] [     T88] printk: console lock API call [6]: console_unlock() by pid=88, comm=kworker/4:1+events

Could you please provide the full log, including the backtraces?
I am curious about the callers of the console_lock()...

Best Regards,
Petr