Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Oct 2025 17:19:00 +0000
From:      bugzilla-noreply@freebsd.org
To:        x11@FreeBSD.org
Subject:   [Bug 290471] NIRI causing a Fatal trap: page fault on FreeBSD 14.3 with NVIDIA drivers
Message-ID:  <bug-290471-7141-JJtK8ydkaO@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-290471-7141@https.bugs.freebsd.org/bugzilla/>

index | next in thread | previous in thread | raw e-mail

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

--- Comment #11 from mfoacs@gmail.com ---
(In reply to Jan Beich from comment #8)

The drm debug method doesn't really yield anything useful because the system
hangs before anything is saved to the disk.

Several repeats and it finally dumped a .core file:

 lldb -c niri.core niri
(lldb) target create "niri" --core "niri.core"
Core file '/home/mda/niri.core' (x86_64) was loaded.
(lldb) bt
* thread #1, name = 'niri', stop reason = signal SIGABRT
  * frame #0: 0x00002126e5fbd01a libc.so.7`__sys_thr_kill + 10
    frame #1: 0x00002126e5f35a64 libc.so.7`__raise + 52
    frame #2: 0x00002126e5fe9a59 libc.so.7`abort + 73
    frame #3: 0x0000211ebde4db1a
niri`std::sys::pal::unix::abort_internal::h0a88409ea4262509 + 10
    frame #4: 0x0000211ebde6a139 niri`std::process::abort::h831a56a00fc8b4c2 +
9
    frame #5: 0x0000211ebde555b9 niri`__rustc::__rust_abort + 9
    frame #6: 0x0000211ebdc7bf89 niri`__rustc::__rust_start_panic + 9
    frame #7: 0x0000211ebde4b1e9 niri`__rustc::rust_panic + 9
    frame #8: 0x0000211ebde4aed5
niri`std::panicking::rust_panic_with_hook::h258e28e59b8ae6d9 + 640
    frame #9: 0x0000211ebde50de8
niri`std::panicking::begin_panic_handler::_$u7b$$u7b$closure$u7d$$u7d$::hbe2a0ba43379c13f
+ 152
    frame #10: 0x0000211ebde50d49
niri`std::sys::backtrace::__rust_end_short_backtrace::h47097eb228dea165 + 9
    frame #11: 0x0000211ebde4a79c niri`__rustc::rust_begin_unwind + 28
    frame #12: 0x0000211ebd44285f
niri`core::panicking::panic_fmt::hcd37a19feafcd42c + 31
    frame #13: 0x0000211ebd4449ca
niri`core::option::expect_failed::h384f106a2dc2c9ba + 90
    frame #14: 0x0000211ebdad4ea9
niri`niri::utils::cause_panic::hd5ccf46ccf94316c + 25
    frame #15: 0x0000211ebd29ed17 niri`niri::main::hced04b060c4a1ee4 + 105223
    frame #16: 0x0000211ebd26d123
niri`std::sys::backtrace::__rust_begin_short_backtrace::h4edd054e5f4c75b3 + 3
    frame #17: 0x0000211ebd2a11bc niri`main + 1116
    frame #18: 0x00002126e5f09e34 libc.so.7`__libc_start1 + 292
    frame #19: 0x0000211ebd263231 niri`_start + 33

I was able to narrow down the cause to this line in the config file:

debug {
    render-drm-device "/dev/dri/renderD128"
}

Removing it results in Niri failing to start, but no Kernel panic.

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

home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-290471-7141-JJtK8ydkaO>