[Bug 291239] Kernel panic when running most wayland WMs (nvidia)
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 291239] Kernel panic when running most wayland WMs (nvidia)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 291239] Kernel panic when running most wayland WMs (nvidia)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 291239] Kernel panic when running most wayland WMs (nvidia)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 291239] Kernel panic when running most wayland WMs (nvidia)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 291239] Kernel panic when running most wayland WMs (nvidia)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 291239] Kernel panic when running most wayland WMs (nvidia)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 291239] Kernel panic when running most wayland WMs (nvidia)"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 291239] Kernel panic when running most wayland WMs (nvidia)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 26 Nov 2025 17:59:39 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291239
Bug ID: 291239
Summary: Kernel panic when running most wayland WMs (nvidia)
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs@FreeBSD.org
Reporter: solidwarea@outlook.com
I apologize in advance if I've categorized this incorrectly or if the reason
for my issue is due to the lack of proper research, but I've tried my best but
I can't figure out what's wrong.
I am able to start Wayfire and Sway/SwayFX properly, but running KDE on Wayland
using the tty and sddm leads to a kernel panic, and so does running niri.
Running hyprland gives me a blank screen for a few seconds then my system
restarts. Both niri and KDE have on one or two occasions loaded the desktop for
a few seconds, but freezes immediately after that, then goes on to crash and
restart my system again.
Specifications:
Nvidia GTX 1660 Super
Driver version: 580.105.08 (graphics/nvidia-drm-kmod)
FreeBSD 15.0-RC3 (I believe I got the same result on 14.3-Release when I tried
it)
---
Kldstat:
4 3 0xffffffff83400000 605d178 nvidia.ko
8 2 0xffffffff8945e000 1650f8 nvidia-modeset.ko
9 1 0xffffffff83357000 14a88 nvidia-drm.ko
---
/etc/rc.conf:
sshd_enable="YES"
moused_nondefault_enable="NO"
# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
dumpdev="AUTO"
zfs_enable="YES"
firewall_enable="YES"
firewall_type="workstation"
kld_list="nvidia nvidia-modeset nvidia-drm"
dbus_enable="YES"
sddm_enable="NO"
seatd_enable="YES"
linux_enable="YES"
---
/boot/loader.conf:
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
cryptodev_load="YES"
zfs_load="YES"
hw.nvidiadrm.modeset="1"
hw.nvidia.registry.EnableGpuFirmware=1
---
Error and kernel panic:
exec dbus-launch --exit-with-session ck-launch-session startplasma-wayland
org.kde.startup: not a reply org.freedesktop.locale1 QDBusMessage(type=Error,
service="", error name="org.freedesktop.DBus.Error.ServiceUnknown", error
message="The name org.freedesktop.locale1 was not provided by any .service
files", signature="", contents="The name org.freedesktop.locale1 was not
provided by any .service files"))
No backend specified, automatically choosing drm
kwin_wayland_drm: drmModelistLessee: Failed: Invalid argument
kwin_screencast: Failed to connect PipeWire context
Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address = 0x10
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80f1eed4
stack pointer = 0x8:0xffffffff80d51f0a30
frame pointer = 0x8:0xffffffff80d51f0a80
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 = 6502 (kwin_wayland)
rdi: 0000000000000000 rsi: 0000000000000010 rdx: 0000000000000000
rcx: 0000000000000001 r8: fffffe00d51f0a78 r9: fffffe00d51f0bc0
rax: 0000000000000000 rbx: 0000000000000000 rbp: fffffe00d51f0a60
r10: 00000000f7fa0000 r11: 0000000000004111 r12: fffff8031b84fe88
r13: 0000000000000000 r14: 0000000000000010 r15: 0000004000530000
trap number = 12
panic: page fault
cpuid = 3
time = 1764173413
KDB: stack backtrace:
#0 0xffffffff80bbe1ad at kdb_backtrace+0x5d
#1 0xffffffff80b71536 at vpanic+0x136
#2 0xffffffff80b713f3 at panic+0x43
#3 0xffffffff81079f69 at trap_pfault+0x3c9
#4 0xffffffff8104fea8 at calltrap+0x8
#5 0xffffffff80dfa97c at kpi_vm_insert_pfn_prot_locked+0xfc
#6 0xffffffff83363e55 at nv_drm_gem_nvks_handle_vma_fault+0xfc
#7 0xffffffff80df4682 at linux_cdev_pager_populate+0x122
#8 0xffffffff80e07e19 at vm_fault_allocate+0x3a9
#9 0xffffffff80e065c3 at vm_fault+0x363
#10 0xffffffff80b70613 at vm_fault_trap+0x4d
#11 0xffffffff81079d99 at trap_pfault+0x1f9
#12 0xffffffff810796cf at trap+0x54f
#13 0xffffffff8104fea8 at calltrap+0x8
Uptime: 385
Dumping 995 out of 16096 MB: ..2%..12%..21%..31%..41%..52%..62%..71%..81%..91%
Dump complete
Automatic reboot in 15 seconds - press a key on the console to abort
---
The numbers may be a bit off since I had to extract the output from a photo of
my screen as I otherwise couldn't figure out how to save it to my computer. If
that is of any importance, let me know so that I can double check to make sure
everything is in order.
Thank you!
--
You are receiving this mail because:
You are the assignee for the bug.