Intel N100 Alder Lake: random hangs plus reboots

I have a 16GB Minix Z100 passively cooled mini-PC here running FreeBSD 15.0-RELEASE.
I must say these are fantastic 100% silent low-cost and cool-running machines for general purpose basic computing needs.

I installed FreeBSD 15.0-RELEASE, installed net/realtek-re-kmod198 network driver for the Realtek RTL8125 hardware.
I installed the Intel i915kms video driver.

All seemed good and then it randomly locked up for a few seconds (whilst it core dumped?) and then it spontaneously rebooted.
This happened multiple times so there is some unknown issue that needs identifying.

Where do I start in trying to diagnose what's happening?
 
Will see if this helps:

 
I have tracked down the relevant crash files in /var/crash and will post excerpts here to get an idea of what is happening:

/var/crash/core.txt.0:
Code:
Unable to find a kernel debugger.
Please install the devel/gdb port or gdb package.

/var/crash/info.0:
Code:
Dump header from device: /dev/nda0p3
  Architecture: amd64
  Architecture Version: 2
  Dump Length: 974733312
  Blocksize: 512
  Compression: none
  Dumptime: 2026-01-11 16:39:47 +0000
  Hostname: fbsd
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 15.0-RELEASE releng/15.0-n280995-7aedc8de6446 GENERIC
  Panic String: page fault
  Dump Parity: 1132736026
  Bounds: 0
  Dump Status: good

/var/crash/vmcore.0: (excerpt)
Code:
minidump FreeBSD/amd64
---<<BOOT>>---
Copyright (c) 1992-2025 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 15.0-RELEASE releng/15.0-n280995-7aedc8de6446 GENERIC amd64
FreeBSD clang version 19.1.7 (https://github.com/llvm/llvm-project.git llvmorg-19.1.7-0-gcd708029e0b2)
VT(efifb): resolution 1920x1080
CPU: Intel(R) N100 (806.40-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0xb06e0  Family=0x6  Model=0xbe  Stepping=0
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x7ffafbbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x121<LAHF,ABM,Prefetch>
  Structured Extended Features=0x239ca7eb<FSGSBASE,TSCADJ,BMI1,AVX2,FDPEXC,SMEP,BMI2,ERMS,INVPCID,NFPUSG,PQE,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PROCTRACE,SHA>
  Structured Extended Features2=0x98c007bc<UMIP,PKU,OSPKE,WAITPKG,GFNI,VAES,VPCLMULQDQ,RDPID,MOVDIRI,MOVDIR64B>
  Structured Extended Features3=0xfc184410<FSRM,MD_CLEAR,IBT,IBPB,STIBP,L1DFL,ARCH_CAP,CORE_CAP,SSBD>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  IA32_ARCH_CAPS=0x180fd6b<RDCL_NO,IBRS_ALL,SKIP_L1DFL_VME,MDS_NO,TAA_NO>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
  TSC: P-state invariant, performance statistics
real memory  = 17179869184 (16384 MB)
avail memory = 16425865216 (15664 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <ALASKA A M I >
WARNING: L3 data cache covers more APIC IDs than a package (7 > 3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
random: registering fast source Intel Secure Key Seed
random: fast provider: "Intel Secure Key Seed"
random: unblocking device.
ioapic0 <Version 2.0> irqs 0-119
Launching APs: 1 3 2
random: entropy device external interface
kbd0 at kbdmux0
efirtc0: <EFI Realtime Clock>
efirtc0: registered as a time-of-day clock, resolution 1.000000s
smbios0: <System Management BIOS> at iomem 0x75cba000-0x75cba017
smbios0: Entry point: v3 (64-bit), Version: 3.6
aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS,SHA1,SHA256>
acpi0: <ALASKA A M I >
acpi0: Power Button (fixed)
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 19200000 Hz quality 950
Event timer "HPET" frequency 19200000 Hz quality 550
Event timer "HPET1" frequency 19200000 Hz quality 440
Event timer "HPET2" frequency 19200000 Hz quality 440
Event timer "HPET3" frequency 19200000 Hz quality 440
Event timer "HPET4" frequency 19200000 Hz quality 440
atrtc1: <AT realtime clock> on acpi0
atrtc1: Warning: Couldn't map I/O.
atrtc1: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
vgapci0: <VGA-compatible display> port 0x4000-0x403f mem 0x6000000000-0x6000ffffff,0x4000000000-0x400fffffff at device 2.0 on pci0
vgapci0: Boot video device
xhci0: <XHCI (generic) USB 3.0 controller> mem 0x6001110000-0x600111ffff at device 13.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
xhci0: xECP capabilities <PROTO,PROTO,VEND(c0),LEGACY,VEND(c6),VEND(c7),VEND(c2),DEBUG,VEND(c3),VEND(d1),VEND(ce),VEND(c8),VEND(c9),VEND(ca),VEND(cc),VEND(cd),VEND(d2),VEND(cf),VEND(d3)>
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
xhci1: <XHCI (generic) USB 3.0 controller> mem 0x6001100000-0x600110ffff at device 20.0 on pci0
xhci1: 32 bytes context size, 64-bit DMA
xhci1: xECP capabilities <PROTO,PROTO,VEND(c0),LEGACY,VEND(c6),VEND(c7),VEND(c2),DEBUG,VEND(c3),VEND(c4),VEND(ce),VEND(c8),VEND(c9),VEND(ca),VEND(cb),VEND(cc),VEND(cd)>
usbus1 on xhci1
usbus1: 5.0Gbps Super Speed USB v3.0
pci0: <memory, RAM> at device 20.2 (no driver attached)
pci0: <simple comms> at device 22.0 (no driver attached)
pcib1: <ACPI PCI-PCI bridge> at device 28.0 on pci0
pci1: <ACPI PCI bus> on pcib1
re0: <Realtek PCIe 2.5GbE Family Controller> port 0x3000-0x30ff mem 0x80500000-0x8050ffff,0x80510000-0x80513fff at device 0.0 on pci1
re0: Using Memory Mapping!
re0: Using 1 MSI-X message
re0: ASPM disabled
re0: version:1.98.00
re0: Ethernet address: a0:1e:0b:14:8d:e6

This product is covered by one or more of the following patents:            
US6,570,884, US6,115,776, and US6,327,625.
<6>re0: Ethernet address: a0:1e:0b:14:8d:e6
pcib2: <ACPI PCI-PCI bridge> at device 29.0 on pci0
pci2: <ACPI PCI bus> on pcib2
nvme0: <Generic NVMe Device> mem 0x80420000-0x80423fff at device 0.0 on pci2
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
hdac0: <Intel Alder Lake-N HDA Controller> mem 0x6001130000-0x6001133fff,0x6001000000-0x60010fffff at device 31.3 on pci0
pci0: <serial bus> at device 31.5 (no driver attached)
acpi_button0: <Sleep Button> on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_button1: <Power Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_syscontainer0: <System Container> on acpi0
acpi_syscontainer1: <System Container> on acpi0
atrtc0: <AT realtime clock> at port 0x70 irq 8 on isa0
atrtc0: Warning: Couldn't map I/O.
atrtc0: registered as a time-of-day clock, resolution 1.000000s
atrtc0: Can't map interrupt.
atrtc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 16.
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
hwpstate_intel0: <Intel Speed Shift> on cpu0
cpufreq0: <CPU frequency control> on cpu0
hwpstate_intel1: <Intel Speed Shift> on cpu1
cpufreq1: <CPU frequency control> on cpu1
hwpstate_intel2: <Intel Speed Shift> on cpu2
cpufreq2: <CPU frequency control> on cpu2
hwpstate_intel3: <Intel Speed Shift> on cpu3
cpufreq3: <CPU frequency control> on cpu3
Timecounter "TSC" frequency 806400737 Hz quality 1000
Timecounters tick every 1.000 msec
ugen1.1: <Intel XHCI root HUB> at usbus1
ugen0.1: <Intel XHCI root HUB> at usbus0
uhub0 on usbus1
uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1
uhub1 on usbus0
uhub1: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
nvme0: Allocated 64MB host memory buffer
hdacc0: <Realtek ALC897 HDA CODEC> at cad 0 on hdac0
hdaa0: <Realtek ALC897 Audio Function Group> at nid 1 on hdacc0
pcm0: <Realtek ALC897 (Front Analog)> at nid 20 and 24 on hdaa0
nda0 at nvme0 bus 0 scbus0 target 0 lun 1
nda0: <FORESEE XP1000F512G V1.28 NF59392010763>
nda0: Serial Number NF59392010763
nda0: nvme version 1.4
nda0: 488386MB (1000215216 512 byte sectors)
Trying to mount root from zfs:zroot/ROOT/default []...
uhub1: 3 ports with 3 removable, self powered
uhub0: 16 ports with 16 removable, self powered
Root mount waiting for: usbus1
ugen1.2: <Keychron Keychron Q3 Max> at usbus1
usbhid0 on uhub0
usbhid0: <Keychron Keychron Q3 Max, class 0/0, rev 2.00/1.00, addr 1> on usbus1
hidbus0: <HID bus> on usbhid0
hkbd0: <Keychron Keychron Q3 Max Keyboard> on hidbus0
kbd1 at hkbd0
usbhid1 on uhub0
usbhid1: <Keychron Keychron Q3 Max, class 0/0, rev 2.00/1.00, addr 1> on usbus1
hidbus1: <HID bus> on usbhid1
usbhid2 on uhub0
usbhid2: <Keychron Keychron Q3 Max, class 0/0, rev 2.00/1.00, addr 1> on usbus1
hidbus2: <HID bus> on usbhid2
hkbd1: <Keychron Keychron Q3 Max Keyboard> on hidbus2
kbd2 at hkbd1
ugen1.3: <Microsoft Microsoft Basic Optical Mouse v2.0> at usbus1
usbhid3 on uhub0
usbhid3: <Microsoft Microsoft Basic Optical Mouse v2.0, class 0/0, rev 1.10/1.04, addr 2> on usbus1
hidbus3: <HID bus> on usbhid3
<118>Setting hostuuid: 78e02694-54a7-3344-b167-0d3de1b689c2.
<118>Setting hostid: 0x97ce2be8.
<118>Starting file system checks:
<118>/dev/gpt/efiboot0: FILESYSTEM CLEAN; SKIPPING CHECKS
<118>Mounting local filesystems:.
<118>no pools available to import
<118>Loading kernel modules: i915kms
<6>[drm] Got Intel graphics stolen memory base 0x7c800000, size 0x3c00000
drmn0: <drmn> on vgapci0
vgapci0: child drmn0 requested pci_enable_io
vgapci0: child drmn0 requested pci_enable_io
i915/adlp_dmc.bin: could not load binary firmware /boot/firmware/i915/adlp_dmc.bin either
adlp_dmc.bin: could not load binary firmware /boot/firmware/adlp_dmc.bin either
i915_adlp_dmc.bin: could not load binary firmware /boot/firmware/i915_adlp_dmc.bin either
lkpi_iic0: <LinuxKPI I2C> on drmn0
iicbus0: <Philips I2C bus> on lkpi_iic0
iic0: <I2C generic I/O> on iicbus0
lkpi_iic1: <LinuxKPI I2C> on drmn0
iicbus1: <Philips I2C bus> on lkpi_iic1
iic1: <I2C generic I/O> on iicbus1
lkpi_iic2: <LinuxKPI I2C> on drmn0
iicbus2: <Philips I2C bus> on lkpi_iic2
iic2: <I2C generic I/O> on iicbus2
lkpi_iic3: <LinuxKPI I2C> on drmn0
iicbus3: <Philips I2C bus> on lkpi_iic3
iic3: <I2C generic I/O> on iicbus3
lkpi_iic4: <LinuxKPI I2C> on drmn0
iicbus4: <Philips I2C bus> on lkpi_iic4
iic4: <I2C generic I/O> on iicbus4
lkpi_iic5: <LinuxKPI I2C> on drmn0
iicbus5: <Philips I2C bus> on lkpi_iic5
iic5: <I2C generic I/O> on iicbus5
lkpi_iic6: <LinuxKPI I2C> on drmn0
iicbus6: <Philips I2C bus> on lkpi_iic6
iic6: <I2C generic I/O> on iicbus6
lkpi_iic7: <LinuxKPI I2C> on drmn0
iicbus7: <Philips I2C bus> on lkpi_iic7
iic7: <I2C generic I/O> on iicbus7
lkpi_iic8: <LinuxKPI I2C> on drmn0
iicbus8: <Philips I2C bus> on lkpi_iic8
iic8: <I2C generic I/O> on iicbus8
drmn0: successfully loaded firmware image 'i915/adlp_dmc.bin'
drmn0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20)
sysctl_add_oid: can't re-use a leaf (hw.dri.debug)!
<6>[drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
VT: Replacing driver "efifb" with new "drmfb".
start FB_INFO:
height=1080 width=1920 depth=32
pbase=0x4000000000 vbase=0xfffffe00f8c00000
name=drmn0 id=i915drmfb flags=0x0 stride=7680
end FB_INFO
<118>Autoloading module: acpi_wmi
<118>Autoloading module: hcons
<118>Autoloading module: hms
<118>Autoloading module: hsctrl
<118>Autoloading module: ichsmb
ichsmb0: <Intel Alder Lake SMBus controller> port 0xefa0-0xefbf mem 0x6001138000-0x60011380ff at device 31.4 on pci0
smbus0: <System Management Bus> on ichsmb0
acpi_wmi0: <ACPI-WMI mapping> on acpi0
acpi_wmi0: cannot find EC device
acpi_wmi0: Embedded MOF found
acpi_wmi1: <ACPI-WMI mapping> on acpi0
acpi_wmi1: cannot find EC device
acpi_wmi1: Embedded MOF found
hms0: <Keychron Keychron Q3 Max Mouse> on hidbus2
hms0: 8 buttons and [XYWH] coordinates ID=2
hsctrl0: <Keychron Keychron Q3 Max System Control> on hidbus2
hcons0: <Keychron Keychron Q3 Max Consumer Control> on hidbus2
hms1: <Microsoft Microsoft Basic Optical Mouse v2.0> on hidbus3
hms1: 3 buttons and [XYW] coordinates ID=0
<118>Setting up harvesting: PURE_RDSEED,RANDOMDEV,[CALLOUT],[UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,[NET_ETHER],NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED
<118>Feeding entropy: .
<118>ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/alsa-lib /usr/local/lib/compat/pkg /usr/local/lib/gcc13 /usr/local/lib/perl5/5.42/mach/CORE /usr/local/lib/qt6 /usr/local/lib/samba4 /usr/local/llvm19/lib /usr/local/llvm19/lib/x86_64-portbld-freebsd15.0 /usr/local/share/chromium
<118>32-bit compatibility ldconfig path: /usr/lib32 /usr/local/lib32/gcc13
<118>Setting hostname: fbsd.
<6>lo0: link state changed to UP
<6>re0: link state changed to UP
<118>Starting Network: lo0 re0.
<118>lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384
<118>    options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
<118>    inet 127.0.0.1 netmask 0xff000000
<118>    inet6 ::1 prefixlen 128
<118>    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
<118>    groups: lo
<118>    nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
<118>re0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
<118>    options=2018<VLAN_MTU,VLAN_HWTAGGING,WOL_MAGIC>
<118>    ether a0:1e:0b:14:8d:e6
<118>    inet6 fe80::a21e:bff:fe14:8de6%re0 prefixlen 64 scopeid 0x1
<118>    inet6 2a00:23c7:f8b6:8301:a21e:bff:fe14:8de6 prefixlen 64 autoconf pltime 314929610 vltime 314929610
<118>    media: Ethernet autoselect (1000baseT <full-duplex>)
<118>    status: active
<118>    nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
<118>Starting devd.
<118>Starting event4 moused.
<118>Starting event5 moused.
<118>Starting event6 moused.
<118>Starting event7 moused.
<118>Starting event8 moused.
<118>Starting event9 moused.
<118>Starting dhclient.
<118>DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7
<118>DHCPOFFER from 192.168.1.254
<118>DHCPREQUEST on re0 to 255.255.255.255 port 67
<118>DHCPACK from 192.168.1.254
<118>bound to 192.168.1.84 -- renewal in 43200 seconds.
<118>route: message indicates error: File exists
<118>add host 127.0.0.1: gateway lo0 fib 0: route already in table
<118>route: message indicates error: File exists
<118>add host ::1: gateway lo0 fib 0: route already in table
<118>add net fe80::: gateway ::1
<118>add net ff02::: gateway ::1
<118>add net ::ffff:0.0.0.0: gateway ::1
<118>add net ::0.0.0.0: gateway ::1
<118>Updating /var/run/os-release done.
<118>Updating motd:.
<118>Clearing /tmp (X related).
<118>Creating and/or trimming log files.
<118>Starting syslogd.
<118>No core dumps found.
<118>Mounting late filesystems:.
<118>Starting powerd.
<118>Starting dbus.
<118>Starting default moused.
<118>Configuring vt: keymap.
<118>Performing sanity check on sshd configuration.
<118>Starting sshd.
<118>Starting cron.
<118>Starting background file system checks in 60 seconds.
<118>Starting lightdm.
<118>
<118>Sun Jan 11 16:21:40 UTC 2026

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address    = 0xfe0
fault code        = supervisor read data, page not present
instruction pointer    = 0x20:0xffffffff83810d86
stack pointer            = 0x28:0xfffffe00d2d56780
frame pointer            = 0x28:0xfffffe00d2d567c0
code segment        = base 0x0, limit 0xfffff, type 0x1b
            = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags    = interrupt enabled, resume, IOPL = 3
current process        = 5038 (MainThread)
rdi: 0000000000000000 rsi: 0000000000000000 rdx: 0000000000000000
rcx: 0000000000000000  r8: 0000000000686ba0  r9: 00000000000000ff
rax: 00000000000001fd rbx: 0000000000000000 rbp: fffffe00d2d567c0
r10: 0000000000000000 r11: 0000000000007df7 r12: fffffe010d90d000
r13: 0000000000000011 r14: 000000000000010f r15: fffff8005fabc550
trap number        = 12
panic: page fault
cpuid = 0
time = 1768149587
KDB: stack backtrace:
#0 0xffffffff80bbe1ed at kdb_backtrace+0x5d
#1 0xffffffff80b71576 at vpanic+0x136
#2 0xffffffff80b71433 at panic+0x43
#3 0xffffffff81079f69 at trap_pfault+0x3c9
#4 0xffffffff8104ff18 at calltrap+0x8
#5 0xffffffff83818ef8 at intel_remap_pages+0x438
#6 0xffffffff83816303 at i915_vma_pin_ww+0x113
#7 0xffffffff838db87d at intel_plane_pin_fb+0x34d
#8 0xffffffff8381c2df at intel_prepare_plane_fb+0x10f
#9 0xffffffff83a174f2 at drm_atomic_helper_prepare_planes+0x32
#10 0xffffffff83843dc6 at intel_atomic_commit+0xd6
#11 0xffffffff83a19719 at drm_atomic_helper_page_flip+0x59
#12 0xffffffff83a4ad51 at drm_mode_page_flip_ioctl+0x421
#13 0xffffffff83a400d9 at drm_ioctl_kernel+0xb9
#14 0xffffffff83a4046e at drm_ioctl+0x2de
#15 0xffffffff80df12fd at linux_file_ioctl+0x2fd
#16 0xffffffff80be0cb5 at kern_ioctl+0x255
#17 0xffffffff80be0a01 at sys_ioctl+0x101
Uptime: 18m22s
 
As a kernel debug novice, from the dump above the issue seems related to the Intel i915kms driver:

Code:
Fatal trap 12: page fault while in kernel mode
fault code        = supervisor read data, page not present
KDB: stack backtrace:
#0 0xffffffff80bbe1ed at kdb_backtrace+0x5d
#1 0xffffffff80b71576 at vpanic+0x136
#2 0xffffffff80b71433 at panic+0x43
#3 0xffffffff81079f69 at trap_pfault+0x3c9
#4 0xffffffff8104ff18 at calltrap+0x8
#5 0xffffffff83818ef8 at intel_remap_pages+0x438
#6 0xffffffff83816303 at i915_vma_pin_ww+0x113
#7 0xffffffff838db87d at intel_plane_pin_fb+0x34d
#8 0xffffffff8381c2df at intel_prepare_plane_fb+0x10f
#9 0xffffffff83a174f2 at drm_atomic_helper_prepare_planes+0x32
#10 0xffffffff83843dc6 at intel_atomic_commit+0xd6
#11 0xffffffff83a19719 at drm_atomic_helper_page_flip+0x59
#12 0xffffffff83a4ad51 at drm_mode_page_flip_ioctl+0x421
#13 0xffffffff83a400d9 at drm_ioctl_kernel+0xb9
#14 0xffffffff83a4046e at drm_ioctl+0x2de
#15 0xffffffff80df12fd at linux_file_ioctl+0x2fd
#16 0xffffffff80be0cb5 at kern_ioctl+0x255
#17 0xffffffff80be0a01 at sys_ioctl+0x101

Any help going further with this would be appreciated.
 
I'd try this in loader.conf:
Code:
hw.i915kms.nuclear_pageflip=0

Install Intel DDX:
Code:
pkg install 'xf86-video-intel'

And conf:
Code:
mkdir -p '/usr/local/etc/X11/xorg.conf.d' && ee '/usr/local/etc/X11/xorg.conf.d/10-graphics-custom.conf'
Code:
Section "OutputClass"
    Identifier "Intel (intel custom)"
    MatchDriver "i915"
    Driver "intel"
    Option "AccelMethod" "SNA"
    Option "DRI" "3"
    Option "TearFree" "0"
    Option "VSync" "0"
    Option "PageFlip" "0"
    Option "SwapbuffersWait" "0"
    Option "TripleBuffer" "0"
    Option "Throttle" "0"
EndSection
 
I'd try this in loader.conf:
Code:
hw.i915kms.nuclear_pageflip=0

Install Intel DDX:
Code:
pkg install 'xf86-video-intel'

And conf:
Code:
mkdir -p '/usr/local/etc/X11/xorg.conf.d' && ee '/usr/local/etc/X11/xorg.conf.d/10-graphics-custom.conf'
Code:
Section "OutputClass"
    Identifier "Intel (intel custom)"
    MatchDriver "i915"
    Driver "intel"
    Option "AccelMethod" "SNA"
    Option "DRI" "3"
    Option "TearFree" "0"
    Option "VSync" "0"
    Option "PageFlip" "0"
    Option "SwapbuffersWait" "0"
    Option "TripleBuffer" "0"
    Option "Throttle" "0"
EndSection

After those changes, it booted to a black screen with solid white cursor at top left of the screen, plus a moveable mouse pointer, but no GUI. Normally it would have progressed to a lightdm-gtk-greeter user login GUI where I could login.
 
After those changes, it booted to a black screen with solid white cursor at top left of the screen, plus a moveable mouse pointer, but no GUI. Normally it would have progressed to a lightdm-gtk-greeter user login GUI where I could login.
Hmm, maybe Intel DDX doesn't support newer Intel chips; I'd remove the xorg.conf and uninstall xf86-video-intel (nuclear_pageflip=0 should still be fine)
 
I have made those changes but left the line in /boot/loader.conf.
I logged in as normal, so all good there, and opened a few apps but no crash so far...will use it longer and see what happens. 👍
 
One thing to watch for with the N100 is to put the latest cpu microcode on the box. See https://forums.freebsd.org/threads/intel-n100-generates-data-corruption.99663/post-722320

Also 'passively cooled' always me feel a bit queasy. It all depends how they have built it. The plastic case in that picture doesn't look very convincing to me, the heatsink is probably inside, so they are hoping that enough warm air is going to come out of the top lid grill by convection alone to cool the chip. I've found that replacing the headsink paste on a few of those N100 mini-pc's makes them a lot more stable. The stuff they use in the factory is usually very cheap stuff, and they always seem to put far too much of it on, in the 2 or 3 boxes I have opened up. The result is unexplained random system crashes, basically because the chip momentarily overheats. On one of the machines I did this too, replacing the factory paste with a thin layer of arctic mx-4 dropped the cpu temps about 10 deg C and made the box much more stable.
 
One thing to watch for with the N100 is to put the latest cpu microcode on the box. See https://forums.freebsd.org/threads/intel-n100-generates-data-corruption.99663/post-722320

Also 'passively cooled' always me feel a bit queasy. It all depends how they have built it. The plastic case in that picture doesn't look very convincing to me... unless it's actually sold metal and the case is the heatsink. I've found that replacing the headsink paste on a few of those N100 mini-pc's makes them a lot more stable. The stuff they use in the factory is usually very cheap stuff, and they always seem to put far too much of it on, in the 2 or 3 boxes I have opened up. The result is unexplained random system crashes, basically because the chip momentarily overheats. On one of the machines I did this too, replacing the factory paste with a thin layer of arctic mx-4 dropped the cpu temps about 10 deg C and made the box much more stable.
Very interesting re the temporary overheating leading to crashes!

I have used passively cooled PCs for the last 15 years without any instability due to overheating so far...unless this is the first machine that does this for me. I used another identical machine with Linux over the last year or so without issues once I got it installed and configured correctly.

If heat can be proven to be the problem then I will do what you say about replacing the thermal paste.

I will take a look at the thread you posted, thanks a lot!
 
When I think of passive cooling, I tend to think of something like this N100 box from MSI, not a small plastic minipc case with a grille in the top. Or perhaps those are actually metal heatsink fins on top of the minix case, it's hard to tell from the photo on their website; but even if they are metal, they don't look very beefy.
1768163664898.png
 
Very interesting re the temporary overheating leading to crashes!

I have used passively cooled PCs for the last 15 years without any instability due to overheating so far...unless this is the first machine that does this for me. I used another identical machine with Linux over the last year or so without issues once I got it installed and configured correctly.

If heat can be proven to be the problem then I will do what you say about replacing the thermal paste.

I will take a look at the thread you posted, thanks a lot!
Well, I could be wrong of course. I have definitely seen heat causing random crashes on N100 mini pc's though, although those were ones with fans! Anyway, just something to be aware of, you don't always suspect hardware nowadays.
 
When I think of passive cooling, I tend to think of something like this box from MSI, not a small plastic minipc case with a grille in the top. Or perhaps those are actually metal heatsink fins on top of the minix case, it's hard to tell from the photo on their website; but even if they are metal, they don't look very beefy.
View attachment 24855
The Minix Z100 is a heavy solid lump of metal - no plastic.
I have a script which uses coretemp to retrieve the CPU temp and at idle it shows about 36C running FreeBSD 15.
Update on adding 'hw.i915kms.nuclear_pageflip=0' to /boot/loader.conf: no crash yet! Looking good so far, but I will use it more this evening to see if it ever crashes.
 
I've definitely got one fanless mini PC (but an N150 rather than an N100) that crashes/randomly reboots with OpenBSD/FreeBSD/Linux - haven't got to the bottom of it. I have many other similar fanless machines that are rock solid with BSDs & Linux.

So (hardware) duds definitely exist.

With the problematic machine I tried the BSDs and both OpenBSD and FreeBSD had crashes after 10-15 minutes idle, so I assumed BSD driver issues, but Linux Mint exhibited the same behaviour in the same sort of timeframe. I've parked that machine for now, but I was assuming thermal issues (but it was just a hunch.)

So if this is a new machine you are setting up, might be worth trying Linux to see if that's more stable - if it is more stable, then that points to a BSD problem, but if Linux has the same issues you know it's more pointing towards hardware.
 
I intend to use this machine as an experimental / bleeding edge FreeBSD 16 running all the latest code, so any fixes like this will be incorporated into the customisation of it.
 
I've definitely got one fanless mini PC (but an N150 rather than an N100) that crashes/randomly reboots with OpenBSD/FreeBSD/Linux - haven't got to the bottom of it. I have many other similar fanless machines that are rock solid with BSDs & Linux.
Very annoying. But as you say, other fanless machines are fine. Maybe the PC with problems would still crash if it was actively cooled, perhaps just some bad config somewhere?

So (hardware) duds definitely exist.
Yes they do!

With the problematic machine I tried the BSDs and both OpenBSD and FreeBSD had crashes after 10-15 minutes idle, so I assumed BSD driver issues, but Linux Mint exhibited the same behaviour in the same sort of timeframe. I've parked that machine for now, but I was assuming thermal issues (but it was just a hunch.)
These things can be hard to troubleshoot, it's true.

So if this is a new machine you are setting up, might be worth trying Linux to see if that's more stable - if it is more stable, then that points to a BSD problem, but if Linux has the same issues you know it's more pointing towards hardware.
I have an identical machine (I have 2 Minix Z100s) running Linux which is fine. With blackbird's tweak in the /boot/loader.conf I have seen no crash yet which is very promising but I will see if it crashes again.
 
The Minix Z100 is a heavy solid lump of metal - no plastic.
I have a script which uses coretemp to retrieve the CPU temp and at idle it shows about 36C running FreeBSD 15.
Update on adding 'hw.i915kms.nuclear_pageflip=0' to /boot/loader.conf: no crash yet! Looking good so far, but I will use it more this evening to see if it ever crashes.
OK, so it should be fine then. Maybe I guessed it wrong on this one. Yeah, I couldn't tell from the picture whether it's plastic or metal. If that top surface is a decent sized heatsink, it should be ok.
 

View attachment 24857

It's a bit hard to tell from the photo. If it's all metal, it should be pretty good. The review doesn't say. Looks like quite a nice box actually.
Yes, it's all metal on all sides even underneath, very heavy for its size. It feels nice and warm on a cold winter night but not too hot. They really are fantastic value for money and with 16GB RAM, 512GB SSD (not the fastest but completely fine) and being completely silent - what's not to like? Easy to travel with too. Unfortunately they may be hard to find for sale now though as they have seemingly replaced this model with higher specced CPUs - N150, N300/350 etc but at much higher prices.
 
Yeah I can't find that little MSI box anywhere, but it was only announced a few months ago, and appears to be aimed at industrial customers. Which is a shame because it looks nice. But the minix box looks nice too.
 
OK great, I will terminate it if I see CPU getting too hot for too long - need to check specs.
You can install pbzip2 from packages. It should run the pbzip2 stress test stable indefinitely if they have got the cooling right, IMHO. You're not even doing any disk i/o or running the gpu with that test, just the cpu cores.
 
Back
Top