Ubuntu

Ubuntu 24.04 crashes to login screen when display turns off

Bug #2068849 reported by Cpuccino on 2024-06-09

This bug report is a duplicate of: Bug #2062426: simple-framebuffer: swiotlb buffer is full. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu	Incomplete	Undecided	Unassigned

Bug Description

Happens pretty consistently, when I turn off the monitor, and then re-open it, session crashes and throws me back to the login screen.

```
Jun 10 13:29:57 cpuccino-ubuntu kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Jun 10 13:29:57 cpuccino-ubuntu kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Jun 10 13:29:57 cpuccino-ubuntu kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Jun 10 13:29:57 cpuccino-ubuntu kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
```

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
Uname: Linux 6.8.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.fabric-imex-mgmt:
DeviceFileMinor: 4323
DeviceFileMode: 256
DeviceFileModify: 1
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 555.52.04 Tue Jun 4 13:54:58 UTC 2024
GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4)
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 10 04:18:32 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
DkmsStatus: nvidia/555.52.04, 6.8.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation AD102 [GeForce RTX 4090] [10de:2684] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] AD102 [GeForce RTX 4090] [1462:5102]
InstallationDate: Installed on 2024-06-09 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-35-generic root=UUID=6d88b286-7d50-4d17-8d36-5ec19316ffb0 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2022
dmi.bios.release: 22.4
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2204
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX Z690-A GAMING WIFI D4
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd11/30/2022:br22.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ690-AGAMINGWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

See original description

Tags:

Revision history for this message

Cpuccino (cpuccino) wrote on 2024-06-09:

.proc.driver.nvidia.params.txt Edit (944 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (177.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (15.0 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (1.1 MiB, text/plain; charset="utf-8")
Lspci.txt Edit (20.0 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (1.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Lsusb-t.txt Edit (2.5 KiB, text/plain; charset="utf-8")
Lsusb-v.txt Edit (192.7 KiB, text/plain; charset="utf-8")
MonitorsUser.xml.txt Edit (1.7 KiB, text/plain; charset="utf-8")
NvidiaBugReportLog.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (53.1 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (47.9 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (10.7 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (472.1 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (62.4 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (13.1 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (12.6 KiB, text/plain; charset="utf-8")
acpidump.txt Edit (3.3 MiB, text/plain; charset="utf-8")
nvidia-settings.txt Edit (79.2 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (33.3 KiB, text/plain; charset="utf-8")

Cpuccino (cpuccino) on 2024-06-10

description:

updated

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2024-06-10:

The only problem I can see here is bug 2062426. You should be able to use the workarounds from bug 2060268 to try and solve that. If you still have issues with the workarounds in place then please follow:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment