[Bug 267691] FreeBSD 13 and newer panic on boot on Pentium Pro system

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267691

            Bug ID: 267691
           Summary: FreeBSD 13 and newer panic on boot on Pentium Pro
                    system
           Product: Base System
           Version: CURRENT
          Hardware: i386
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: hannula@gmail.com

The system has no problems booting latest 12.4, no errors, HW is working
perfectly after all these years, tested with memtest86.

But booting 13 or CURRENT results in a crash after loading crypto, always with
the same Address 0x3446ff003446ff MCA:

crypto: <crypto core>
MCA: Bank 2, Status 0xb600000000140001
MCA: Global Cap 0x0000000000000005, Status 0x0000000000000004
MCA: Vendor "GenuineIntel", ID 0x619, APIC ID 0 
MCA: CPU 0 UNCOR EN PCC unclassified error
MCA: Address 0x3446ff003446ff
panic: Unrecoverable machine check exception 
cpuid = 0
time = 1
KDB: stack backtrace:
#0 0x107540f at kdb_backtrace+0x4f
#1 0x102da3e at vpanic+0xlle
#2 0x102d914 at panic+0x14
#3 0xl3d7ef8 at mca_intr+0xa8
#4 0x141dbd7 at trap+0x237
#5 0xffc0319f at _end+0xfde379cf
#6 0x28 at 11+0x7

Booting from
FreeBSD-14.0-CURRENT-i386-20221103-5cc5c9254da-259005-mini-memstick.img gives a
more detailed report:

MCA: Address 0x3446ff003446ff
panic: Unrecoverable machine check exception
cpuid = 0
time = 1
KDB: stack backtrace:
db_trace_self_wrapper(0,1d906a0,0,8086,0,...) at
db_trace_self_wrapper+0x28/fram
e 0x22f9a24
vpanic(1553304,22f9a60,22f9a60,22f9a70,13cc948,...) at vpanic+0xf4/frame
0x22f9a
40
panic(1553304,d906a0,22f9b3c,22fa000,1c,...) at panic+0x14/frame 0x22f9a54
mca_intr(1e28d78,8,14a05da,215,1d9033c,...) at mca_intr+0xa8/frame 0x22f9a70
trap(22f9b3c,8,28,28,40,...) at trap+0x14e/frame 0x22f9b30
calltrap() at 0xffc0321f/frame 0x22f9b30
--- trap 0xlc, eip = 0x12c129d, esp = 0x22f9b7c, ebp = 0x22f9bcc ---
zone_import(3c12c80,3c4540c,7d,0,2,...) at zone_import+0x2fd/frame 0x22f9bcc
cache_alloc(0,2) at cache_alloc+0x36e/frame 0x22f9c2c
cache_alloc_retry(0,2,1c) at cache_alloc_retry+0x18/frame 0x22f9c4c
uma_zalloc_arg(3c12c80,0,2) at uma_zalloc_arg+0xfa/frame 0x22f9c6c
malloc(44,1acef28,2) at malloc+0x6b/frame 0x22f9c8c
sysctl_add_oid(0,3df8080,ffffffff,14aa195,8004000f,3c13918,0,0,1007fb0,1518df1,1
4a0506,0) at sysctl_add_oid+0x1ab/frame 0x22f9cac
zone_alloc_sysctl(2300000,0,22f9d38,f8d144,0,...) at
zone_alloc_sysctl+0x2f2/fra
me 0x22f9d04
uma_startup3(0) at uma_startup3+0x59/frame 0x22f9d14
mi_startup() at mi_startup+0x214/frame 0x22f9d38
btext() at btext+0x5f
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at kdb_enter+0x34: movl $0,kdb_why
db> 

As I have no serial console this was OCR from screenshot, I hope I got all the
mistakes corrected.

-- 
You are receiving this mail because:
You are the assignee for the bug.