615.71.09: hangs and vertical line corruption on DP monitors (RTX 4060), 610.57.04 works

NVIDIA Open GPU Kernel Modules Version

615.71.09 (Arch nvidia-open-dkms). 610.57.04 works.

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.

Not tested.

Operating System and Version

Arch Linux, Hyprland 0.56.2 (Wayland)

Kernel Release

7.2.4-arch1-2 and 7.2.6-arch2-1

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

NVIDIA GeForce RTX 4060 (drives both displays). A second GPU (RTX 4070 SUPER) is present with no displays attached.

Describe the bug

On 615.71.09, with two DisplayPort monitors on the RTX 4060 (Philips 27M2N5500 and AOC Q27G4N, both 2560x1440@180):

• System hangs while the compositor starts (no TTY switch, power button does nothing). Both times the kernel logged:
  nvidia-modeset: WARNING: GPU:1: Lost display notification (0:0x00000000); continuing.
• Once, the Philips showed corruption: the whole image, cursor included, made of 1 px vertical lines with a few px of black between them. It did not show up in screenshots. The AOC was fine.
• On the first boot after the upgrade: nvidia-modeset: ERROR: GPU:1: Idling display engine timed out: 0x0000c77d:0:0:707

Going back to 610.57.04 (same kernel, cables, monitors and config) fixes all of it. Possibly related to #1357.

To Reproduce

• RTX 4060 with the two monitors above over DP, 2560x1440@180, Hyprland
• Driver 615.71.09, reboot a few times

Bug Incidence

Sometimes

nvidia-bug-report.log.gz

Not available, I'm back on 610.57.04.

More Info

No response

Start by reproducing the two-DisplayPort RTX 4060 setup with Hyprland on 615.71.09, then compare the kernel's nvidia-modeset warnings with the known-good 610.57.04 version. Collect nvidia-bug-report.log.gz and check whether the behavior relates to #1357. Done means the compositor starts reliably without hangs or display corruption in this configuration.