https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297214
--- Comment #2 from Peter Eriksson <[email protected]> ---
The server has been running fine for almost 2 weeks, until this sunday when
it's HBA controller started spewing out disk errors so had to reboot the
server, then then this morning when it panic'ed twice again (08:56 & 09:15):
atal trap 9: general protection fault while in kernel mode^M
cpuid = 62; apic id = 3e^M
instruction pointer = 0x20:0xffffffff80f34dbd^M
stack pointer = 0x28:0xfffffe0aab3eba00^M
frame pointer = 0x28:0xfffffe0aab3ebb00^M
code segment = base 0x0, limit 0xfffff, type 0x1b^M
= DPL 0, pres 1, long 1, def32 0, gran 1^M
processor eflags = interrupt enabled, resume, IOPL = 0^M
current process = 40988 (vmstat)^M
rdi: fffff8bd00000000 rsi: fffff870d1b26780 rdx: 730bd5b93e715cb3^M
rcx: 000000009b470cdd r8: fffffe0aab3ebb68 r9: 0000000000000000^M
rax: 000000009b470c00 rbx: ffffffffd9f0e0eb rbp: fffffe0aab3ebb00^M
r10: 000029ea4acaa8a0 r11: fffff870d1b26cd0 r12: 0000000000000000^M
r13: 000000000000000f r14: ffffffffda107c02 r15: eccec1ce09eb1e61^M
trap number = 9^M
panic: general protection fault^M
cpuid = 62^M
time = 1787122260^M
KDB: stack backtrace:^M
#0 0xffffffff80bd69cd at kdb_backtrace+0x5d^M
#1 0xffffffff80b87526 at vpanic+0x136^M
#2 0xffffffff80b873e3 at panic+0x43^M
#3 0xffffffff81098b88 at trap_fatal+0x68^M
#4 0xffffffff8106f4b8 at calltrap+0x8^M
#5 0xffffffff80b97e21 at sysctl_root_handler_locked+0x91^M
#6 0xffffffff80b97278 at sysctl_root+0x268^M
#7 0xffffffff80b97906 at userland_sysctl+0x1a6^M
#8 0xffffffff80b97c56 at kern___sysctlbyname+0x226^M
#9 0xffffffff80b97c9d at sys___sysctlbyname+0x2d^M
#10 0xffffffff81099606 at amd64_syscall+0x126^M
#11 0xffffffff8106fdab at fast_syscall_common+0xf8^M
Uptime: 2d17h5m6s^M
Fatal trap 9: general protection fault while in kernel mode^M
cpuid = 12; apic id = 0c^M
instruction pointer = 0x20:0xffffffff825e8a34^M
stack pointer = 0x28:0xfffffe04402dbd70^M
frame pointer = 0x28:0xfffffe04402dbef0^M
code segment = base 0x0, limit 0xfffff, type 0x1b^M
= DPL 0, pres 1, long 1, def32 0, gran 1^M
processor eflags = interrupt enabled, resume, IOPL = 0^M
current process = 6 (l2arc_feed_thread)^M
rdi: fffff8604390b068 rsi: fffff81000009658 rdx: df82b6ce489cfa25^M
rcx: df82b6ce489cfa8d r8: d7ded9d1cd35e94f r9: c846fb901c778dca^M
rax: df82b6ce489cfa25 rbx: ffffffff8289b200 rbp: fffffe04402dbef0^M
r10: 0000000000000025 r11: 0000003000000000 r12: fffff8604fece000^M
r13: fffffe08591d1000 r14: 0000000004edae00 r15: df82b6ce489cfa25^M
trap number = 9^M
panic: general protection fault^M
cpuid = 12^M
time = 1787123388^M
KDB: stack backtrace:^M
#0 0xffffffff80bd69cd at kdb_backtrace+0x5d^M
#1 0xffffffff80b87526 at vpanic+0x136^M
#2 0xffffffff80b873e3 at panic+0x43^M
#3 0xffffffff81098b88 at trap_fatal+0x68^M
#4 0xffffffff8106f4b8 at calltrap+0x8^M
#5 0xffffffff80b3d97b at fork_exit+0x7b^M
#6 0xffffffff810704de at fork_trampoline+0xe^M
Uptime: 14m29s^M
Strange. I'm starting to wonder if there might be some hardware issue since I'm
only seeing this problem on this specific server. A CPU gone bad or something
with a power supply causing havoc. Ah well, I'll try some firmware updates and
see if that helps.
(Dell PowerEdge R740xd, Intel X710 10G ethernet adapters, Dell HBA330 Mini &
Broadcom 9500-16e SAS HBA adapters - we are using the same hardware in other
servers without problem. The issue was not seen at FreeBSD 15.0, but that might
just be a coincidence.)
--
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.