NVIDIA / NVIDIA/open-gpu-kernel-modules

Changing output frequency breaks output.

Open
#928 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C
Stars
17.4k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

NVIDIA Open GPU Kernel Modules Version

580.82.07

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.
  • I confirm that this does not happen with the proprietary driver package.
Operating System and Version

Manjaro Linux, nobara, cachyos (VMs)

Kernel Release

Does not matter as far I can tell. Tested 6.15 , 6.16 and 6.17-rc4

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.
  • I am running on a stable kernel release.
Hardware: GPU

5070 TI

Describe the bug

Changing output frequency causes output to fail. VM is working just with no display output.

[ 5722.546831] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
[ 5739.191230] [drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000200] Flip event timeout on head 0
[ 5743.203295] [drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000200] Failed to apply atomic modeset. Error code: -22
[ 5746.871070] [drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000200] Flip event timeout on head 0
[ 5750.878727] [drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000200] Failed to apply atomic modeset. Error code: -22

EDIT: I downgraded driver to version 575.65.04 and I've yet to see it fail. I can change output frequency at will.

To Reproduce
  1. keep changing your display output frequency (LG C1 via hdmi 2.1 in my case, from 119.88Hz to 23.976Hz and back most of the time fails.)
    ...it fails more times than it actually succeeds. I have to ssh and reboot VM or reset it on proxmox.

[ 5722.546831] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
[ 5739.191230] [drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000200] Flip event timeout on head 0
[ 5743.203295] [drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000200] Failed to apply atomic modeset. Error code: -22
[ 5746.871070] [drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000200] Flip event timeout on head 0
[ 5750.878727] [drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000200] Failed to apply atomic modeset. Error code: -22

Bug Incidence

Sometimes

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the attached nvidia-bug-report.log.gz and the nvidia-modeset and nvidia_drm errors reported during repeated changes between 119.88Hz and 23.976Hz. Reproduce the failure with the NVIDIA 580.82.07 driver, RTX 5070 Ti, LG C1 over HDMI 2.1, and a VM, then compare behavior with 575.65.04; done means output frequency changes no longer lose display output or produce the reported timeouts.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.