NVIDIA / NVIDIA/open-gpu-kernel-modules
Driver crash occurred while screen was locked
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
NVIDIA Open GPU Kernel Modules Version
570.133.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
Arch Linux
Kernel Release
6.13.7-arch1-1 #1 SMP PREEMPT_DYNAMIC
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: NVIDIA GeForce RTX 4070 Laptop GPU (UUID: GPU-85fade4b-34aa-55e3-2fe2-caacc7060d25)
Describe the bug
After updating to version 570.133.07, the driver crashed, which caused the entire machine to freeze. This issue has never occurred with driver version 570.124.04.
I'm using KDE with Wayland. I have two displays: the built-in laptop screen and an external monitor connected via HDMI.
At the moment of the freeze, the screen lock was active, and it's possible that the monitors had also gone to sleep. No GPU- or CPU-intensive applications were running in the background at the time.
To Reproduce
I don't currently know a reliable way to reproduce the issue.
Bug Incidence
Once
nvidia-bug-report.log.gz
crash-journal.log.gz - full journal from the boot
nvidia-bug-report.log.gz
More Info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing nvidia-bug-report.log.gz and crash-journal.log.gz for the freeze while the screen lock or displays were asleep. Compare the reported 570.133.07 behavior with 570.124.04 and determine whether the logs provide a reproducible failure or a clear driver fault; completion would require a confirmed diagnosis and regression fix.
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
- Needs clarification
- Newbie friendliness
- 25/100