NVIDIA / NVIDIA/nvidia-modprobe
Frequent Coredumps in Journalctl
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 85
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Process 9298 (nvidia-modprobe) of user 1000 dumped core.
Module /usr/bin/nvidia-modprobe without build-id.
Stack trace of thread 9298:
#0 0x00006ffc8b30783b n/a (/usr/lib/ld-linux-x86-64.so.2 + 0x2183b)
#1 0x00006ffc8b3020f8 n/a (/usr/lib/ld-linux-x86-64.so.2 + 0x1c0f8)
#2 0x00006ffc8b3039be n/a (/usr/lib/ld-linux-x86-64.so.2 + 0x1d9be)
#3 0x00006ffc8b302748 n/a (/usr/lib/ld-linux-x86-64.so.2 + 0x1c748)
ELF object binary architecture: AMD x86-64
Appears frequently in my journalctl logs.
Adresses in ld-linux-x86-64.so.2 are always the same.
The way I could somehow reproduce it was running an application with wine.
(Unigine Superposition Benchmark Windows Version dx11 1080p Extreme).
Driver Version: 555.58
Kernel: Linux 6.9.7-arch1-1
Display (PL2760Q): 2560x1440 @ 144Hz
DE: KDE Plasma 6.1.1
GPU: NVIDIA GeForce RTX 2080 Rev. A [Discrete]
Contributor guide
No contributing guide indexed for this repository
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
The payload names no source file or test. Start by reproducing the nvidia-modprobe coredump with the stated Wine workload and inspecting journalctl output on the listed Linux, kernel, and driver setup; done means the recurring coredump is no longer observed under that reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- operating-systems, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100