From: Petr Mladek <pmladek@suse.com>
To: ysard <ysard_git@gmx.fr>
Cc: John Ogness <john.ogness@linutronix.de>,
linux-kernel@vger.kernel.org, senozhatsky@chromium.org
Subject: Re: Regression: system freeze on resume from suspend introduced by printk per-console suspended state
Date: Mon, 2 Feb 2026 12:02:07 +0100 [thread overview]
Message-ID: <aYCEL905vRkBlU5D@pathway> (raw)
In-Reply-To: <trinity-925e197b-4c6a-49f7-b8c8-5b44e596d291-1769898129741@3c-app-mailcom-bs05>
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
next prev parent reply other threads:[~2026-02-02 11:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 22:42 Regression: system freeze on resume from suspend introduced by printk per-console suspended state ysard_git
2025-12-23 6:20 ` John Ogness
[not found] ` <trinity-43147d5d-a8ea-47c1-9f83-b578c346b387-1766479103562@3c-app-mailcom-bs12>
2026-01-08 0:05 ` pv
2026-01-08 9:43 ` John Ogness
2026-01-23 7:44 ` ysard
2026-01-23 12:19 ` Petr Mladek
2026-01-24 1:22 ` ysard
2026-01-28 14:00 ` Petr Mladek
2026-01-28 15:25 ` John Ogness
2026-01-29 9:34 ` ysard
2026-01-30 15:56 ` Petr Mladek
2026-01-30 16:28 ` Petr Mladek
2026-01-31 22:22 ` ysard
2026-02-02 11:02 ` Petr Mladek [this message]
2026-02-03 1:32 ` ysard
2026-02-03 14:11 ` Petr Mladek
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=aYCEL905vRkBlU5D@pathway \
--to=pmladek@suse.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=ysard_git@gmx.fr \
/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