Ubuntu
nvidia-graphics-drivers-510 package

display turns suddenly off and then on again

Bug #1978401 reported by Marcel Franke
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-510 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi,

Randomly the display turns off and then on again. Happens sometimes many times and others times not at all, randomly.

Related to https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-495/+bug/1956252

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
Uname: Linux 5.15.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.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 510.73.05 Sat May 7 05:30:26 UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 12 09:45:00 2022
DistUpgraded: 2022-04-21 07:46:27,025 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A] [10de:1e07] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd TU102 [GeForce RTX 2080 Ti Rev. A] [1458:37a9]
InstallationDate: Installed on 2022-04-03 (69 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS PRO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=7d72a26f-7e2e-4ed2-851b-4bedb4181f16 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-04-21 (52 days ago)
dmi.bios.date: 01/19/2021
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F12l
dmi.board.asset.tag: Default string
dmi.board.name: Z390 AORUS PRO-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.:bvrF12l:bd01/19/2021:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSPRO-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z390 AORUS PRO
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
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.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

Revision history for this message
Marcel Franke (donutloop) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

A monitor going blank and then coming back almost always means that a stable signal (enough bandwidth) can't be maintained.

You should start by trying to replace the DisplayPort cable, or at least re-plugging the one you have. If that doesn't solve it then to at least prove the theory please try using 1920x1080 for a little while.

tags: added: bandwidth nvidia
affects: xorg (Ubuntu) → nvidia-graphics-drivers-510 (Ubuntu)
Changed in nvidia-graphics-drivers-510 (Ubuntu):
status: New → Incomplete
Revision history for this message
Marcel Franke (donutloop) wrote (last edit ):

I bought a new cable a while back, the same problem as with the old cable. I'm using 4k Monitor so do you mean I should switch to HD resolution?

Revision history for this message
Marcel Franke (donutloop) wrote :

I switched to HD resolution, I will test it in the next few days (7 days or so).

Revision history for this message
Marcel Franke (donutloop) wrote :

I think you are right, under HD resolution it works flawless. How can I fix it?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I only know how to fix this on the Intel graphics driver ("max bpc" setting). I can't yet find a setting documented for Nvidia that would fix it...

http://us.download.nvidia.com/XFree86/Linux-x86_64/515.48.07/README/index.html

So my only suggestion is to replug both ends of the cable or try yet another cable. 4K at 60Hz should be easy to maintain with a good DP1.2 cable, or any DP1.4 cable.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This might be it:

  Option "Dac8Bit" "true"

Revision history for this message
Marcel Franke (donutloop) wrote :

I configured it today, I hope it makes a difference!

Revision history for this message
Marcel Franke (donutloop) wrote :

i turned on the Dac8Bit option, problem is the same, more ideas how fix it?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Replug both ends of the DisplayPort cable, or try yet another cable. 4K at 60Hz should be easy to maintain with a good DisplayPort 1.2 cable, or any DisplayPort 1.4 cable. So I would recommend looking for cables that claim to support DisplayPort 1.4 (or higher).

Revision history for this message
Marcel Franke (donutloop) wrote :

ok I brought a new cable, will be the second new DisplayPort cable. The first one is from version 1.2 and the newly brought cable is from version 1.4

Revision history for this message
Marcel Franke (donutloop) wrote :

still the same problem as before

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I'm running out of affordable ideas... It's possible the problem is at either end of the cable -- in the monitor or the graphics card :(

Changed in nvidia-graphics-drivers-510 (Ubuntu):
status: Incomplete → New
Revision history for this message
Marcel Franke (donutloop) wrote :

I run the nvidia-bug-report.sh, can you see something in the logs?

see appendix, which contains a log report of the Nvidia graphic card.

Revision history for this message
Marcel Franke (donutloop) wrote :

i have found those logs in the log file

Aug 21 00:12:39 donutloop kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug 21 00:12:39 donutloop kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug 21 00:12:39 donutloop kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug 21 00:12:39 donutloop kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership

is that the cause of it, maybe?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I don't think modeset ownership is a problem during normal usage, only when changing VTs or on startup. So probably not related, but maybe.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.