Shuttle DL30N Intel v226 kernel panics

Started by andyrtr, October 25, 2024, 09:29:37 PM

Previous topic - Next topic
I've setup a new box using a Shuttle DL30N (Intel N100 and Intel 226 NICs). I've instantly updated the BIOS to avoid the known stability issues caused by the Intel NICs. I've done a full successful memtest86+ run.

Now I'm faced with random kernel panics/reboots. Maybe someone can help me to locate the issue:

load_dn_aqm dn_aqm PIE loaded
cannot forward src fe80:1::6786:fd3d:6726:b5f7, dst 2001:db8::4, nxt 6, rcvif igc0, outif igc1
cannot forward src fe80:1::6786:fd3d:6726:b5f7, dst 2001:bc8:1210:8bb::, nxt 6, rcvif igc0, outif igc1
cannot forward src fe80:1::6786:fd3d:6726:b5f7, dst 2001:bc8:1210:8bb::, nxt 6, rcvif igc0, outif igc1


Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 06
fault virtual address   = 0x8000000000
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff830460ad
stack pointer           = 0x28:0xfffffe00c629edd0
frame pointer           = 0x28:0xfffffe00c629ee10
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         = 2 (clock (0))
rdi: fffffe00fd5be1d8 rsi: 0000000000000000 rdx: 0000008000000000
rcx: fffffe00fd5be1c0  r8: 0000000000003000  r9: 000000000000000f
rax: fffffe00fd5be1e8 rbx: fffffe00fcf95000 rbp: fffffe00c629ee10
r10: 0018000000000000 r11: 000000007ff75b03 r12: fffffe00fd5be1c0
r13: 00000000000062b4 r14: 000000000000002f r15: fffffe00fd5be1d8
trap number             = 12
panic: page fault
cpuid = 3
time = 1729812657
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00c629eac0
vpanic() at vpanic+0x131/frame 0xfffffe00c629ebf0
panic() at panic+0x43/frame 0xfffffe00c629ec50
trap_fatal() at trap_fatal+0x40b/frame 0xfffffe00c629ecb0
trap_pfault() at trap_pfault+0x46/frame 0xfffffe00c629ed00
calltrap() at calltrap+0x8/frame 0xfffffe00c629ed00
--- trap 0xc, rip = 0xffffffff830460ad, rsp = 0xfffffe00c629edd0, rbp = 0xfffffe00c629ee10 ---
ng_netflow_expire() at ng_netflow_expire+0x24d/frame 0xfffffe00c629ee10
softclock_call_cc() at softclock_call_cc+0x12c/frame 0xfffffe00c629eec0
softclock_thread() at softclock_thread+0xe5/frame 0xfffffe00c629eef0
fork_exit() at fork_exit+0x7f/frame 0xfffffe00c629ef30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00c629ef30
--- trap 0x2dc12dc1, rip = 0x16f216f212391239, rsp = 0xc140c14c911c911, rbp = 0x6f4d6f4d24952495 ---
KDB: enter: panic
---<<BOOT>>---
Copyright (c) 1992-2023 The FreeBSD Project.

My former Zotac ZBOX CI323 (Intel N3150) consumes idle 8W/load ~8,5W. The current Shuttle N100 box is idle 8,5W/load ~10,2W but suddenly jumps to ~19W and stays there all time not going back. Intel speed shift looks good and seems to be still in use.

Any idea how to find out whether this may be ssd / memory / cpu / NIC related?

Linux also showed a kernel panic when moving large amounts of files. Removing and inserting the ssd seems to have fixed the panic.

Testing the system with a linux 6.6.x LTS branch kernel also consumes high ~18W power. A current 6.11.x linux kernel seems to have this fixed running <6W. FreeBSD/OPNsense seem to be missing the power consumption fix so far. I'll keep using a current linux on this system for now.