[Bug 287894] x11/nvidia-driver: panic on exit from Xorg

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287894

            Bug ID: 287894
           Summary: x11/nvidia-driver: panic on exit from Xorg
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
             Flags: maintainer-feedback?([email protected])
          Assignee: [email protected]

I sometimes get a kernel panic when exiting from Xorg with
nvidia-driver-570.169.1403000 on 14.3-RELEASE.

The first panic was on May 12 and I got about 10 crashes so far. I think the
problem is more likely to occur after using programs that use 3D acceleration.

Card is:

nvidia0: <NVIDIA GeForce GTX 1650> on vgapci0
vgapci0: child nvidia0 requested pci_enable_io
vgapci0: child nvidia0 requested pci_enable_io
nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 
570.169  Thu Jun 12 19:58:07 UTC 2025

panic message:

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x30
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff8326b11c
stack pointer           = 0x28:0xfffffe0174e73960
frame pointer           = 0x28:0xfffffe017668ab10
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 1766 (MainThread)
rdi: fffffe016ea2d000 rsi: fffff80001d54000 rdx: 0000000000000000
rcx: fffff80001d54000  r8: 000000000000902d  r9: fffffe017668a794
rax: 0000000000000000 rbx: fffff8040064e800 rbp: fffffe017668ab10
r10: 0000000000000000 r11: 685f24ab000b7351 r12: fffffe016ea2d000
r13: fffff80001d54000 r14: fffff8000fa0d600 r15: 0000000000000000
trap number             = 12
panic: page fault
cpuid = 0
time = 1751065771
KDB: stack backtrace:
#0 0xffffffff806f247d at kdb_backtrace+0x5d
#1 0xffffffff806a4701 at vpanic+0x161
#2 0xffffffff806a4593 at panic+0x43
#3 0xffffffff80a2f639 at trap_pfault+0x3d9
#4 0xffffffff80a08448 at calltrap+0x8

One of the traces always ends up in the nvidia module:

(kgdb) Tracing command "Xorg", '\000' <repeats 15 times> pid 1766 tid 100606
(CPU 0)
#0  __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
#1  doadump (textdump=<optimized out>) at /usr/src/sys/kern/kern_shutdown.c:405
#2  0xffffffff806a425b in kern_reboot (howto=260)
    at /usr/src/sys/kern/kern_shutdown.c:523
#3  0xffffffff806a4759 in vpanic (fmt=0xffffffff80a8f131 "%s", 
    ap=ap@entry=0xfffffe0174e73820) at /usr/src/sys/kern/kern_shutdown.c:967
#4  0xffffffff806a4593 in panic (fmt=<unavailable>)
    at /usr/src/sys/kern/kern_shutdown.c:891
#5  0xffffffff80a2f639 in trap_fatal (frame=<optimized out>, 
    eva=<optimized out>) at /usr/src/sys/amd64/amd64/trap.c:1000
#6  0xffffffff80a2f639 in trap_pfault (frame=0xfffffe0174e738a0, 
    usermode=false, signo=<optimized out>, ucode=<optimized out>)
#7  <signal handler called>
#8  0xffffffff8326b11c in _nv039023rm () from /boot/modules/nvidia.ko
#9  0xfffff8040063b000 in ?? ()
#10 0xfffffe016ea2d000 in ?? ()
#11 0x0000000000000000 in ?? ()

Sounds similar to bug #195806, but unlikely to be related because that bug was
fixed > 10 years ago.

-- 
You are receiving this mail because:
You are the assignee for the bug.