NVIDIA / NVIDIA/open-gpu-kernel-modules
kernel BUG at lib/maple_tree.c:511 + swap corruption with 590.48.01 open module on kernel 6.17 (Intel+NVIDIA PRIME, RTX 4060 Laptop)
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
590.48.01-0ubuntu0.24.04.1 (crash) / 590.48.01-0ubuntu0.24.04.4 (fixed) — Ubuntu DKMS package
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
Ubuntu 24.04.4 LTS (Noble Numbat)
Kernel Release
Linux jorge-ROG-Zephyrus-G16 6.17.0-19-generic #19~24.04.2-Ubuntu SMP PREEMPT_DYNAMIC x86_64
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 4060 Laptop GPU (UUID: GPU-680c3787-33ea-03c1-4e48-6d4fdb465ea9) Host iGPU: Intel Raptor Lake-P UHD Graphics [0000:00:02.0] — PRIME on-demand mode
Describe the bug
kernel BUG at lib/maple_tree.c:511 triggered during normal desktop use with nvidia-driver-590-open 590.48.01-0ubuntu0.24.04.1 loaded in PRIME on-demand mode. The crash
cascaded into swap entry corruption (~30 instances of "Bad swap offset entry 3ffffffefffff") and systemd-journald failure, requiring manual reboot.
Updating to 590.48.01-0ubuntu0.24.04.4 (Ubuntu packaging revision) resolved the issue — 2 consecutive clean boots confirmed.
Kernel messages at time of crash:
[Thu Mar 26 19:39:58 2026] kernel BUG at lib/maple_tree.c:511!
[Thu Mar 26 19:49:52 2026] _swap_info_get: Bad swap offset entry 3ffffffefffff
... (repeated ~30 times until 20:01:02)
[Thu Mar 26 19:56:20 2026] systemd[1]: Failed to start systemd-journald.service
Note: full call trace not captured — journald crashed 16 min after the BUG before persisting the journal. kdump was not enabled.
Related Ubuntu Launchpad report: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-590/+bug/2146498
To Reproduce
- ASUS ROG Zephyrus G16 (2024) or similar Intel+NVIDIA hybrid laptop
- Ubuntu 24.04.4, kernel 6.17.0-19-generic
- Install nvidia-driver-590-open 590.48.01-0ubuntu0.24.04.1 (open/DKMS)
- Boot with GPU in on-demand (PRIME) mode
- Use system normally — crash triggered after ~47 min uptime during normal desktop use
- No specific action required to trigger the BUG
Bug Incidence
Once
nvidia-bug-report.log.gz
More Info
The proprietary driver checkbox was not checked because the crash occurred with the open module and was resolved by updating the Ubuntu packaging revision — testing with the
proprietary driver was not performed.
Hardware context: machine uses Intel+NVIDIA hybrid graphics (PRIME on-demand). The iGPU uses the xe driver. The BUG fires in lib/maple_tree.c, the kernel's VMA management
subsystem. Hypothesis: the .1 revision had a VMA manipulation code path incompatible with the maple tree API in kernel 6.17, corrupting VMA state which propagated to swap
bookkeeping (producing invalid offsets like 0x3ffffffefffff). The .4 Ubuntu revision appears to contain a fix.
Key question for NVIDIA: what changed between Ubuntu packaging revisions .1 and .4 of 590.48.01? Is it a patch to the open module source or a DKMS build fix?
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 with the related Ubuntu Launchpad report and compare the 590.48.01 Ubuntu package revisions .1 and .4. Inspect the reported failure at lib/maple_tree.c:511 and the available reproduction details for the Intel+NVIDIA PRIME setup; the missing call trace and bug-report archive limit the evidence. Done means identifying the relevant packaging or open-module change and explaining whether it prevents the VMA and swap corruption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux, ubuntu
- Domain
- computer-graphics, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100