NVIDIA / NVIDIA/open-gpu-kernel-modules

Kernel panic on resume from S3 suspend on Dell Precision 5510 (Quadro M1000M, nvidia_uvm NULL pointer dereference)

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

535.309.01

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

Linux Mint 22.3

Kernel Release

Linux Precision-5510 6.17.0-35-generic #35~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 26 19:30:42 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

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

GPU 0: Quadro M1000M (UUID: GPU-c78ca889-0d95-417e-4d83-d4d0e4a505c0)

Describe the bug

Describe the bug

A Dell Precision 5510 experiences a reproducible kernel panic during resume from S3 suspend when the NVIDIA driver is active.

The system resumes correctly when using only Intel HD Graphics 530.

The crash occurs every time suspend/resume is attempted and appears to originate from the NVIDIA UVM module.

Reproduction steps

  1. Boot system with NVIDIA GPU enabled.

  2. Open a terminal.

  3. Run:

    systemctl suspend

  4. Wake the system.

  5. Kernel panic occurs during resume.

Expected behavior

System should resume normally from suspend without crashing.

Actual behavior

Kernel panic occurs during resume.

Relevant trace:

RIP: 0010:_raw_q_flush+0x96/0xf0 [nvidia_uvm]
CR2: 0000000000000000
NULL pointer dereference

Additional messages:

note: nvidia-sleep.sh exited with irqs disabled
note: nvidia-sleep.sh exited with preempt_count 1
psmouse serio1: Failed to disable mouse on isa0060/serio1

Hardware

  • Dell Precision 5510
  • NVIDIA Quadro M1000M
  • Intel HD Graphics 530
  • 4K Display (3840x2160)

Software

  • Linux Mint 22.3 (Ubuntu 24.04 based)
  • Kernel 6.17.0-35-generic
  • NVIDIA Driver 535.309.01
  • CUDA 12.2

Reproducibility

100% reproducible.

Occurs on every suspend/resume cycle.

Workaround

Disable NVIDIA GPU and use Intel HD Graphics 530 only.

Suspend/resume then works correctly with no kernel panic.

Additional information

  • GPU functions correctly for rendering, display output, and CUDA workloads.

  • Failure occurs only during suspend/resume.

  • Tried:

    • NVreg_EnableGpuFirmware=0
    • mem_sleep_default=deep
    • acpi.ec_no_wakeup=1
    • GRUB parameter changes

None resolved the issue.

gpu_drivers.txt
suspend_logs.txt
system_info.txt

To Reproduce

Reproduction steps

  1. Boot system with NVIDIA GPU enabled.

  2. Open a terminal.

  3. Run:

    systemctl suspend

  4. Wake the system.

  5. Kernel panic occurs during resume.

Bug Incidence

Always

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

nvidia-bug-report.sh will now collect information about your
system and create the file 'nvidia-bug-report.log.gz' in the current
directory. It may take several seconds to run. In some
cases, it may hang trying to capture data generated dynamically
by the Linux kernel and/or the NVIDIA kernel module. While
the bug report log file will be incomplete if this happens, it
may still contain enough data to diagnose your problem.

If nvidia-bug-report.sh hangs, consider running with the --safe-mode
and --extra-system-data command line arguments.

Please include the 'nvidia-bug-report.log.gz' log file when reporting
your bug via the NVIDIA Linux forum (see forums.developer.nvidia.com)
or by sending email to 'linux-bugs@nvidia.com'.

By delivering 'nvidia-bug-report.log.gz' to NVIDIA, you acknowledge
and agree that personal information may inadvertently be included in
the output. Notwithstanding the foregoing, NVIDIA will use the
output only for the purpose of investigating your reported issue.

Running nvidia-bug-report.sh... complete.

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 reproducing the failure with systemctl suspend while the NVIDIA GPU is enabled, then inspect the nvidia_uvm NULL-pointer trace and the nvidia-sleep.sh resume messages. Compare this with suspend/resume using Intel graphics only; done means the Dell Precision 5510 resumes without a kernel panic while the NVIDIA driver remains active.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.