[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <trinity-4a9c7cd3-cb54-452e-9d51-0fb5bdac8c0c-1767830742679@3c-app-mailcom-bs14>
Date: Thu, 8 Jan 2026 01:05:42 +0100
From: pv <pierre.vignet@...amail.fr>
To: ysard_git@....fr
Cc: John Ogness <john.ogness@...utronix.de>, linux-kernel@...r.kernel.org,
pmladek@...e.com, senozhatsky@...omium.org
Subject: Re: Regression: system freeze on resume from suspend introduced by
printk per-console suspended state
Hi, I am resending the message from December 23 because lkml considered it as spam.
First, thank you for your response.
> It is great that you can reproduce it with 6.18.2. Are you also able to
> test 6.19-rc1 and reproduce it? It would be nice to attack the problem
> from the latest code first.
The code in 6.18.2 has changed enough that I don't dare change it as I did in 6.7.
After compiling and installing 6.19-rc1 (8f0b4cce4481fb22653697cced8d0d04027cb1e8),
I can confirm that the freeze is still present.
> It would be helpful to know if you are doing anything special (like
> using "no_console_suspend") or have multiple consoles. Could you send
> the output of:
>
> $ cat /proc/consoles
>
> and
>
> $ cat /proc/cmdline
>
> Once we have this information, we can start to dig deeper.
$ cat /proc/consoles
tty0 -WU (EC p ) 4:2
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-amd64 root=/dev/mapper/vg0-root ro cryptdevice=UUID=397b50bf-8142-4456-8af2-bf39dcc8f732:cryptdisk:allow-discards mitigations=off quiet splash
It's similar for 6.19.0-rc1.
$ cat /sys/module/printk/parameters/console_suspend
Y
Thank you for your time.
Best regards.
Powered by blists - more mailing lists