[nvidia] Lock screen is frozen

[Sam Magura]

After suspending my PC, sometimes when I resume, I get stuck on the lock screen which shows the current time and says "Click or press any key". No matter which mouse button or key I press, the screen is frozen. The mouse cursor is displayed but does not move.

It seems to occur more frequently when my computer has been suspended for at least several hours. I would say this issue occurs about 50% of the time (very roughly speaking).

Things I have tried which did not work:

- Unplugging and re-plugging in my mouse
- Turning my keyboard off and on again
- Ctrl+Alt+F2 through F6, in an attempt to get access to a TTY

This is on a fresh install of 22.04.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-27-generic 5.15.0-27.28
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC3: srmagura 1247 F.... pulseaudio
 /dev/snd/controlC2: srmagura 1247 F.... pulseaudio
 /dev/snd/controlC0: srmagura 1247 F.... pulseaudio
 /dev/snd/controlC1: srmagura 1247 F.... pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 28 17:53:11 2022
InstallationDate: Installed on 2022-04-23 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
IwConfig:
 lo no wireless extensions.

 enp4s0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-27-generic N/A
 linux-backports-modules-5.15.0-27-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: Default string
dmi.board.name: B450M DS3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: B450M DS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. Next time the problem happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

5. Also check for signs of recent crashes by following https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[Sam Magura (srmagura)]

Here's the prevboot.txt file you requested. Line 20160, timestamp May 26 19:02:39, is when I pressed the power button to resume from suspend.

I followed the steps from here (https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment), but none of the crashes appear to be related to this issue. Here's a screenshot: https://ibb.co/m6zxhhx. Notice the latest crash is from May 21 (in my time zone), so 5 days ago.

[Daniel van Vugt (vanvugt)]

> Line 20160, timestamp May 26 19:02:39, is when I pressed the power
> button to resume from suspend.

Thanks for the detailed info. From that moment on I can see the system resuming including Xorg waking up but no errors are logged at all.

Are you able to ssh into the frozen machine from another machine? I would like to know what 'ps auxw' reports at that point.

Also if the mouse cursor is frozen then the bug is lower level than gnome-shell so this is either in Xorg, the Nvidia Xorg driver, or the kernel.

[Sam Magura (srmagura)]

Sounds good — yes, I will try to ssh into it next time it happens.

[Sam Magura (srmagura)]

Yes, the mouse cursor does get frozen.

The bug occurred and I was able to ssh into the computer. I've attached the results of `ps auxw` as you requested.

[Sam Magura (srmagura)]

This hasn't happened to me in a while, so I think it is fixed, at least when using the latest 515 Nvidia drivers.