I've been running FreeBSD on various servers for years, but I'm no expert. I use "freebsd-update" and binary packages, but have generally found FreeBSD to be exceptionally stable and low-maintenance. This particular server has been running for several years, and was initially installed from FreeBSD 12.0-RELEASE. I've had no trouble using freebsd-update and pkg for version upgrades, until now. As soon as 14.1-RELEASE was available, I tried to do an upgrade, but couldn't boot into the new system because of a "panic: integer divide fault" error. Fortunately I'm using ZFS and boot environments, so I could boot back into the working 14.0-RELEASE boot environment. Since then I've tried several more times to upgrade, but always hit that same integer divide fault error. A freebsd-update to FreeBSD 14.0-RELEASE-p11, today, went fine, but an update to 14.1-RELEASE again failed. Today I managed to get a serial console connection to work, so that I could capture the error and stack trace. This server is a Lenovo System x3650 M2 -[794752U]. Running 2x Intel(R) Xeon(R) X5660 for a total of 24 cores, with 32G of RAM. Booting from a ZFS mirror, with a lot of other disks connected, but encrypted, so I use a script to manually "geli attach" them and then "zpool import" them. Below is what I captured, today: Loading kernel... /boot/kernel/kernel text=0x17baa0 text=0xd5ffd8 text=0x425e7c data=0x180+0xe80 data=0x1868b0+0x479750 0x8+0x189d38+0x8+0x1ad39c Loading configured modules... /boot/entropy size=0x1000 /boot/modules/pefs.ko size 0x2e8e0 at 0x2139000 /boot/kernel/zfs.ko size 0x5cd608 at 0x2168000 /etc/hostid size=0x25 ---<<BOOT>>--- Copyright (c) 1992-2023 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 14.1-RELEASE-p5 GENERIC amd64 FreeBSD clang version 18.1.5 (https://github.com/llvm/llvm-project.git llvmorg-18.1.5-0-g617a15a9eac9) VT(vga): resolution 640x480 CPU: Intel(R) Xeon(R) CPU X5660 @ 2.80GHz (2800.19-MHz K8-class CPU) Origin="GenuineIntel" Id=0x206c2 Family=0x6 Model=0x2c Stepping=2 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=0x29ee3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AESNI> AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM> AMD Features2=0x1<LAHF> Structured Extended Features3=0x9c000000<IBPB,STIBP,L1DFL,SSBD> VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) avail memory = 33314013184 (31770 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: <IBM THURLEY > FreeBSD/SMP: Multiprocessor System Detected: 24 CPUs FreeBSD/SMP: 2 package(s) x 6 core(s) x 2 hardware threads random: unblocking device. Firmware Warning (ACPI): 32/64X length mismatch in FADT/Gpe0Block: 128/64 (20221020/tbfadt-748) Firmware Warning (ACPI): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20221020/tbfadt-850) ioapic0 <Version 2.0> irqs 0-23 ioapic1 <Version 2.0> irqs 24-47 Launching APs: 1 9 15 4 10 5 22 12 13 17 21 20 7 14 19 18 23 11 2 3 16 6 8 random: entropy device external interface kbd1 at kbdmux0 vtvga0: <VT VGA driver> smbios0: <System Management BIOS> at iomem 0xfdf40-0xfdf5e smbios0: Version: 2.5, BCD Revision: 2.5 aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS> [.... some lines left out ....] isa0: <ISA bus> on isab0 atapci0: <Intel ICH10 SATA300 controller> port 0x4118-0x411f,0x412c-0x412f,0x4110-0x4117,0x4128-0x412b,0x40f0-0x40ff,0x40e0-0x40ef irq 16 at device 31.2 on pci0 ata2: <ATA channel> at channel 0 on atapci0 ata3: <ATA channel> at channel 1 on atapci0 atapci1: <Intel ICH10 SATA300 controller> port 0x4108-0x410f,0x4124-0x4127,0x4100-0x4107,0x4120-0x4123,0x40d0-0x40df,0x40c0-0x40cf irq 21 at device 31.5 on pci0 ata4: <ATA channel> at channel 0 on atapci1 ata5: <ATA channel> at channel 1 on atapci1 ns8250: UART FCR is brokene> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (115200,n,8,1) uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff pnpid ORM0000 on isa0 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 15. est0: <Enhanced SpeedStep Frequency Control> on cpu0 Fatal trap 18: integer divide fault while in kernel mode cpuid = 4; apic id = 04 instruction pointer = 0x20:0xffffffff80e9c064 stack pointer = 0x28:0xffffffff82b4ad00 frame pointer = 0x28:0xffffffff82b4ada0 code segment = base rx0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) rdi: 0000000000000000 rsi: 0000000000000000 rdx: 0000000000000000 rcx: 0000000000000000 r8: 0000000000200000 r9: 0000000000000000 rax: 00000000fffffbe0 rbx: 0000000000000000 rbp: ffffffff82b4ada0 r10: 0000000000000000 r11: 3ffffffffffffff8 r12: 00000000fffffc00 r13: 0000000000000000 r14: 0000000000000000 r15: 1ffffffffffffff8 trap number = 18 panic: integer divide fault cpuid = 4 time = 1 KDB: stack backtrace: #0 0xffffffff80b7fefd at kdb_backtrace+0x5d #1 0xffffffff80b32bd1 at vpanic+0x131 #2 0xffffffff80b32a93 at panic+0x43 #3 0xffffffff8100091b at trap_fatal+0x40b #4 0xffffffff80fd6d48 at calltrap+0x8 #5 0xffffffff80e9d651 at zone_alloc_item+0x191 #6 0xffffffff80e9cc04 at zone_ctor+0x5a4 #7 0xffffffff80e9d651 at zone_alloc_item+0x191 #8 0xffffffff80e9d2dd at uma_zcreate+0x8d #9 0xffffffff82140788 at pefs_crypto_init+0x28 #10 0xffffffff821390ef at pefs_init+0xef #11 0xffffffff80c06eb6 at vfs_modevent+0x3f6 #12 0xffffffff80b0dea5 at module_register_init+0x85 #13 0xffffffff80abb685 at mi_startup+0xb5 #14 0xffffffff8037c023 at btext+0x23 Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort
*** This bug has been marked as a duplicate of bug 281618 ***