[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <trinity-88777198-09ee-4655-914d-28550845a840-1770082366459@3c-app-mailcom-bs04>
Date: Tue, 3 Feb 2026 02:32:46 +0100
From: ysard <ysard_git@....fr>
To: Petr Mladek <pmladek@...e.com>
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 2026-02-02 12:02:07, Petr Mladek wrote:
> Could you please provide the full log, including the backtraces?
> I am curious about the callers of the console_lock()...
Sorry, I had been on the same grep since the beginning.
Here are the complete logs.
> 1. console_lock() API called by
> echo suspend >/proc/driver/nvidia/suspend
https://pastebin.com/6gv0bF1c
> 2. console_lock() API called by the suspend test
>
> No freeze (expected):
> $ sudo sh -c "
> mkdir -p /var/run/nvidia-sleep \
> && echo 2 > /var/run/nvidia-sleep/Xorg.vt_number \
> && chvt 63 \
> && systemctl suspend"
https://pastebin.com/10JBnnRx
> 3. No freeze with the 1st patch and uncommented synchronize_srcu() calls.:
> $ sudo sh -c "
> mkdir -p /var/run/nvidia-sleep \
> && echo 2 > /var/run/nvidia-sleep/Xorg.vt_number \
> && chvt 63 \
> && echo suspend >/proc/driver/nvidia/suspend \
> && systemctl suspend"
https://pastebin.com/nqks8h7Z
Cheers
Powered by blists - more mailing lists