[Bug] RTX 3060 Ti (GA104) on 1.10.0: WindowServer stuck in NVMTL translate, watchdog panic during Metal bench
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
Research direction
Start by reviewing the reported NVMTL translation stack and the driver 1.10.0 changes relevant to GA104 and Metal shader compilation; the issue does not name source files or tests. Reproduce the Geekbench 7 Metal failure if possible, then trace the reported path and check whether the benchmark completes without a watchdog panic.
Written by the indexing model from the issue text.
Description
Send logs report ID
NM-7SM4BKZP, NM-Q81PDHEW, NM-ZV982BNB, NM-846QZCY1, NM-SJDAJN86, NM-D232WBFM, NM-KF5M220N, NM-PDVQ17AQ, NM-EV292HM9, NM-HHDA0AJ5, NM-4SW72PP6, NM-8VAFAQF6, NM-BH5ER05D, NM-J59BC2H4, NM-ZB48T7XT, NM-Z4RZC8ZR
Where does it go wrong?
An app or game
What happens
Sluggish desktop. Geekbench Metal dies at ~2/3, then watchdog panic (no checkins 91s, uptime 801s).
WindowServer cpu_resource x3, shutdown_stall x4.
Stack: CA::OGL::MetalContext -> NVMTLLibrary newFunction -> nvmtl_translate -> metal2vulkan emit_vulkan_spirv (42 samples).
Panic: iMacPro1,1 Sequoia 15.8.1 24H32, i5-13500, RTX 3060 Ti 8GB GA104, driver 1.10.0 via 1401.
Boot-args: nvfb=1 nvaccel=1 nvfbheads=4 -nvkmsnosmooth amfi_get_out_of_my_way=0x1 amfi=0x80
Report IDs: NM-7SM4BKZP, NM-Q81PDHEW, ... (全部)
Not sent: driver-kernel-log.txt size limit, system log 124
App or game (if it is one)
Geekbench 7 Metal benchmark
Did you change anything yourself?
No. Only 1401 defaults.
OpenCore DBG-109-2026-09-30, SMBIOS iMacPro1,1, BIOS Above4G ON CSM OFF.
Boot-args: -v debug=0x100 keepsyms=1 ctrsmt=full nvfb=1 nvaccel=1 nvfbheads=4 -nvkmsnosmooth amfi_get_out_of_my_way=0x1 amfi=0x80
- Dominant language
- Rust
- Stars
- 2.5k
- Forks
- 233
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from nullmoth/nvidia-macos-driver
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nullmoth/nvidia-macos-driver#141 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nullmoth/nvidia-macos-driver#126 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
nullmoth/nvidia-macos-driver#108 · 6 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
nullmoth/nvidia-macos-driver#28 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nullmoth/nvidia-macos-driver#170 ·
Maintainers usually reply within 1 day
All issues in nullmoth/nvidia-macos-driver
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
RustCrypto/SSH#596 ·
-
proxy: SQL-over-HTTP turns empty arrays into [""] or [false], or HTTP 500 for int and float arraysOpen
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
neondatabase/neon#12965 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
goauthentik/authentik#26867 ·
Maintainers usually reply within 1 day
-
api bug macos maintainer-needed p2 triaged
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
area::tern difficulty::easy good first issue kind::cleanup triage::ready
Difficulty 1/5 1-3 hours Newbie friendliness 88/100