I have had Eisy rebooting about once a week sometimes twice in a row for a couple of months now. I have the added storage with HA running on Eisy and HA reboots so I know it is a complete system reboot. I finally tried to look into things but not getting far with my abilities. I have activated the core dump and on the last restart I got some information but not sure what it means.

Dump header from device: /dev/gpt/swap0

Architecture: amd64

Architecture Version: 2

Dump Length: 1192792064

Blocksize: 512

Compression: none

Dumptime: 2026-02-20 23:06:11 -0700

Hostname: eisy

Magic: FreeBSD Kernel Dump

Version String: FreeBSD 14.3-RELEASE-p5 #5 releng/14.3-n271450-382f54740ee4-dirty: Tue Oct 28 19:30:07 PDT 2025

root@bsdev143.isy.io:/usr/obj/usr/src/amd64.amd64/sys/eisy

Panic String: ISR and isrvec_stk out of sync

Dump Parity: 1684056904

Bounds: 0

Dump Status: good

Last lines before reboot.

panic: ISR and isrvec_stk out of sync

cpuid = 2

time = 1771653971

KDB: stack backtrace:

#0 0xffffffff80a1a3ed at kdb_backtrace+0x5d

#1 0xffffffff809cbee1 at vpanic+0x161

#2 0xffffffff809cbd73 at panic+0x43

#3 0xffffffff82c114ac at vlapic_update_ppr+0xec

#4 0xffffffff82c12769 at vlapic_pending_intr+0x19

#5 0xffffffff82c02f29 at vm_run+0xa99

#6 0xffffffff82c0657c at vmmdev_ioctl+0x95c

#7 0xffffffff8085798b at devfs_ioctl+0xcb

#8 0xffffffff80ac9ed8 at vn_ioctl+0xc8

#9 0xffffffff80857ffe at devfs_ioctl_f+0x1e

#10 0xffffffff80a3b635 at kern_ioctl+0x255

#11 0xffffffff80a3b381 at sys_ioctl+0x101

#12 0xffffffff80e13847 at amd64_syscall+0x117

#13 0xffffffff80deb9ab at fast_syscall_common+0xf8

Timeout initializing vt_vga

Uptime: 1h25m43s

Dumping 1137 out of 7903 MB:..2%..12%..22%..31%..41%..51%..61%..71%..81%..91%

This is the main thing that I found that shows an error with the ISR and isrvec_stk out of sync but when I try to go deeper with AI telling me what to look for it does not shed any light on the picture for me.

[admin@eisy /var/crash]$ (cat /var/log/messages; bzcat /var/log/messages.*.bz2) | grep -i "panic"

Feb 20 23:06:48 eisy kernel: panic: ISR and isrvec_stk out of sync

Feb 20 23:06:48 eisy kernel: #1 0xffffffff809cbee1 at vpanic+0x161

Feb 20 23:06:48 eisy kernel: #2 0xffffffff809cbd73 at panic+0x43

Feb 20 23:06:48 eisy savecore[1638]: reboot after panic: ISR and isrvec_stk out of sync

[admin@eisy /var/crash]$ dmesg | grep -i "panic"

panic: ISR and isrvec_stk out of sync

#1 0xffffffff809cbee1 at vpanic+0x161

#2 0xffffffff809cbd73 at panic+0x43

[admin@eisy /var/crash]$ dumpon -l

gpt/swap0

So if anyone sees something that I can investigate further I would appreciate some guidance otherwise I will open a ticket to see what the UDI people think.

Thanks for any help that can be offered!

Tom

The first thing I would check is if the eisy is getting hot. Especially since you're running HA on it too. I'd try a simple test first, like aiming a small fan at it, and see if the reboots keeps happening. If it's in a small space, try freeing it up a bit.

29 minutes ago, Guy Lavoie said:

The first thing I would check is if the eisy is getting hot. Especially since you're running HA on it too. I'd try a simple test first, like aiming a small fan at it, and see if the reboots keeps happening. If it's in a small space, try freeing it up a bit.

Good point I forgot to add I was seeing an average core temp of 50c which seemed OK but I put a computer fan on top of it that dropped the core Temps to about 41c

I followed the AI further which says that Bhyve/HA was using APIC virtualization which is causing the crash. I put

hw.vmm.intel.apicv_active="0"

hw.vmm.x2apic_wr_msr_exit="1"

into /boot/loader.conf and restarted then verified it was disabled. Now I just have to wait and see if the random reboots are gone.

Edited 10 hours ago10 hr by tazman