Public bug reported:
This issue doesn't happen with Nnvidia version 525 or 535 but it happens
with 545 and 550.
Steps to reproduce:
- Run window manager or desktop environment without compositor manager.
For example XFCE with Settings – Window Manager Tweaks – Compositor and
disable Enable display compositing. (The problem is visible with this
compositor, too, but getting out of hang with this one is harder.)
- The problem seems to be some kind of race condition because in "only"
happens about 70% of the time for me. I'm using package "linux-tools-
lowlatency-hwe-22.04" to get kernel with PREEMPT_DYNAMIC which may
trigger the race condition easier.
- Run picom as follows to make sure it has no config of any kind that
might avoid the problem:
picom --config /dev/null --show-all-xerrors --log-level=TRACE &
sleep 20; killall picom
Note that this will emit a lot of log messages and picom will be
killed after 20 seconds (resulting in no compositor X session which
should be usable if not pretty).
- Switch to different virtual terminals with CTRL+ALT+F1, CTRL+ALT+F2,
..., CTRL+ALT+F7 and wait for display to refresh on each terminal.
- Assuming your initial virtual terminal was VT 7 as usual for GUI
desktop, you should now see fully black screen with your usual mouse
cursor only. Wait for the sleep timer above (20 seconds) to go off and
kill picom to restore your screen. If you had compositing enabled in
XFCE Window manager, you would be seeing the same issue but getting out
of this issue is much harder because XFCE window manager implements the
compositing internally and having compositing hang you would have to
kill your window manager to get rid of it!
I'm assuming this also happens with other software, too, that simply
happens to trigger the racy codepath during VT switch but the above is
the best way to reproduce the issue at will. The problem happens pretty
often rapidly changing to VT 1 and back to VT 7, too. It may be faster
way to reproduce the problem.
When picom hangs, the last line it outputs to stderr is as follows:
[ 2024-03-23 22:24:17.069 draw_callback_impl TRACE ] Render start, frame
416
Normally this should be followed by
[ 2024-03-23 22:24:17.069 draw_callback_impl TRACE ] Render end
on the same millisecond or one later but when NVidia driver hangs on VT
switch, this never happens.
As I wrote above, this bug doesn't occur with Nvidia driver version 535
so the bug has been introduced between version 535 and 545. I cannot
debug this further because I don't have the source code.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-545 (not installed)
ProcVersionSignature: Ubuntu 6.5.0-26.26.1~22.04.1-lowlatency 6.5.13
Uname: Linux 6.5.0-26-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Sat Mar 23 22:08:21 2024
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-05 (1904 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: nvidia-graphics-drivers-545
UpgradeStatus: Upgraded to jammy on 2023-08-11 (225 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158
** Affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-545 in Ubuntu.
https://bugs.launchpad.net/bugs/2058824
Title:
nvidia-driver-545 (and version 550) randomly hangs with compositing
manager on VT change
Status in nvidia-graphics-drivers-545 package in Ubuntu:
New
Bug description:
This issue doesn't happen with Nnvidia version 525 or 535 but it
happens with 545 and 550.
Steps to reproduce:
- Run window manager or desktop environment without compositor
manager. For example XFCE with Settings – Window Manager Tweaks –
Compositor and disable Enable display compositing. (The problem is
visible with this compositor, too, but getting out of hang with this
one is harder.)
- The problem seems to be some kind of race condition because in
"only" happens about 70% of the time for me. I'm using package "linux-
tools-lowlatency-hwe-22.04" to get kernel with PREEMPT_DYNAMIC which
may trigger the race condition easier.
- Run picom as follows to make sure it has no config of any kind that
might avoid the problem:
picom --config /dev/null --show-all-xerrors --log-level=TRACE &
sleep 20; killall picom
Note that this will emit a lot of log messages and picom will be
killed after 20 seconds (resulting in no compositor X session which
should be usable if not pretty).
- Switch to different virtual terminals with CTRL+ALT+F1, CTRL+ALT+F2,
..., CTRL+ALT+F7 and wait for display to refresh on each terminal.
- Assuming your initial virtual terminal was VT 7 as usual for GUI
desktop, you should now see fully black screen with your usual mouse
cursor only. Wait for the sleep timer above (20 seconds) to go off and
kill picom to restore your screen. If you had compositing enabled in
XFCE Window manager, you would be seeing the same issue but getting
out of this issue is much harder because XFCE window manager
implements the compositing internally and having compositing hang you
would have to kill your window manager to get rid of it!
I'm assuming this also happens with other software, too, that simply
happens to trigger the racy codepath during VT switch but the above is
the best way to reproduce the issue at will. The problem happens
pretty often rapidly changing to VT 1 and back to VT 7, too. It may be
faster way to reproduce the problem.
When picom hangs, the last line it outputs to stderr is as follows:
[ 2024-03-23 22:24:17.069 draw_callback_impl TRACE ] Render start,
frame 416
Normally this should be followed by
[ 2024-03-23 22:24:17.069 draw_callback_impl TRACE ] Render end
on the same millisecond or one later but when NVidia driver hangs on
VT switch, this never happens.
As I wrote above, this bug doesn't occur with Nvidia driver version
535 so the bug has been introduced between version 535 and 545. I
cannot debug this further because I don't have the source code.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-545 (not installed)
ProcVersionSignature: Ubuntu 6.5.0-26.26.1~22.04.1-lowlatency 6.5.13
Uname: Linux 6.5.0-26-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Sat Mar 23 22:08:21 2024
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-05 (1904 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: nvidia-graphics-drivers-545
UpgradeStatus: Upgraded to jammy on 2023-08-11 (225 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2058824/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
