NVIDIA / NVIDIA/open-gpu-kernel-modules

Suspend/resume black screen with nvidia-open 595.71.05 on RTX 4070 Mobile (Wayland/Niri, Lenovo LOQ)

Open
#1,136 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

NVIDIA Open GPU Kernel Modules Version: 595.71.05 Package: linux-cachyos-nvidia-open 7.0.5-1 Kernel: Linux 7.0.3-1-cachyos

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

CachyOS

Kernel Release

Suspend/resume black screen and DRM framebuffer errors

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 4070 Laptop GPU

Describe the bug

The system consistently fails to resume correctly after suspend.

After waking the laptop:

  • displays remain black,
  • the session does not recover,
  • VT switching does not restore output,
  • the issue also reproduces outside Wayland sessions.

The problem occurs:

while running a Wayland session with Niri, and after stopping the graphical session completely and suspending directly from a TTY.

Because the issue reproduces from a pure TTY environment, this does not appear to be compositor-specific.

Reproduction steps

  1. Boot the system normally or TTY
  2. Run: systemctl suspend
  3. Try to wake the laptop

Relevant logs

The following errors appear during DRM/compositor initialization:
nvidia-modeset: ERROR: Invalid request parameters, planePitch or rmObjectSizeInBytes, passed during surface registration

Niri also reports DRM framebuffer failures:

failed to add a framebuffer for the bo
Permission denied (os error 13)

Additional notes

  • The issue reproduces even after stopping SDDM and suspending from a plain TTY.
  • The issue reproduces with and without external monitor attached.
  • SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=true and false were both tested without improvement.
  • Kernel log reports:
    Low-power S0 idle used by default for system suspend
  • ACPI-related firmware errors are also present:
  • ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.PEGP.GPS.NVD1], AE_NOT_FOUND
To Reproduce
  1. Boot the system normally or TTY
  2. Run: systemctl suspend
  3. Try to wake the laptop
Bug Incidence

Always

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

Start by reviewing the attached nvidia-bug-report.log.gz and reproducing the failure with systemctl suspend from a plain TTY. Trace the suspend/resume path around the reported nvidia-modeset DRM surface-registration error and the framebuffer failure, then verify that resume restores display output without those errors.】【。

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.