Looks as if the same thing affected both my laptop and my build machine -- each updated from r357688 (built yesterday & smoke-tested without incident). While I got some screenshots for the laptop, I have a serial console for the build machine, so: ... ---<<BOOT>>--- Table 'FACP' at 0xde3c1b98 Table 'APIC' at 0xde3c1ca8 APIC: Found table at 0xde3c1ca8 APIC: Using the MADT enumerator. Copyright (c) 1992-2020 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 13.0-CURRENT #817 r357726M/357726: Mon Feb 10 04:09:32 PST 2020 root_at_freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 FreeBSD clang version 9.0.1 (git_at_github.com:llvm/llvm-project.git c1a0a213378a458fbea1a5c77b315c7dce08fd05) (based on LLVM 9.0.1) WARNING: WITNESS option enabled, expect reduced performance. ... mountroot: waiting for device /dev/ada0s4a... Fatal trap 9: general protection fault while in kernel mode cpuid = 6; apic id = 06 instruction pointer = 0x20:0xffffffff80c7f97b stack pointer = 0x28:0xfffffe00aa965160 frame pointer = 0x28:0xfffffe00aa965160 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 = 1 (kernel) trap number = 9 panic: general protection fault cpuid = 6 time = 24 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00aa964e40 vpanic() at vpanic+0x185/frame 0xfffffe00aa964ea0 panic() at panic+0x43/frame 0xfffffe00aa964f00 trap_fatal() at trap_fatal+0x386/frame 0xfffffe00aa964f60 trap() at trap+0x8b/frame 0xfffffe00aa965090 calltrap() at calltrap+0x8/frame 0xfffffe00aa965090 --- trap 0x9, rip = 0xffffffff80c7f97b, rsp = 0xfffffe00aa965160, rbp = 0xfffffe00aa965160 --- biotrack_buf() at biotrack_buf+0xb/frame 0xfffffe00aa965160 g_io_deliver() at g_io_deliver+0x30/frame 0xfffffe00aa9651b0 g_io_request() at g_io_request+0x28a/frame 0xfffffe00aa9651e0 g_part_start() at g_part_start+0x289/frame 0xfffffe00aa965260 g_io_request() at g_io_request+0x28a/frame 0xfffffe00aa965290 g_part_start() at g_part_start+0x289/frame 0xfffffe00aa965310 g_io_request() at g_io_request+0x28a/frame 0xfffffe00aa965340 g_io_getattr() at g_io_getattr+0x6b/frame 0xfffffe00aa965380 ffs_mount() at ffs_mount+0x1950/frame 0xfffffe00aa965530 vfs_domount() at vfs_domount+0x835/frame 0xfffffe00aa965760 vfs_donmount() at vfs_donmount+0x911/frame 0xfffffe00aa965800 kernel_mount() at kernel_mount+0x57/frame 0xfffffe00aa965850 parse_mount() at parse_mount+0x4a1/frame 0xfffffe00aa9659a0 vfs_mountroot() at vfs_mountroot+0x53b/frame 0xfffffe00aa965b10 start_init() at start_init+0x28/frame 0xfffffe00aa965bb0 fork_exit() at fork_exit+0x80/frame 0xfffffe00aa965bf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00aa965bf0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- KDB: enter: panic [ thread pid 1 tid 100002 ] Stopped at kdb_enter+0x37: movq $0,0x1087a36(%rip) db> I can leave the build machine in that state for up to a few hours easily enough, in case there's value in that (so I can do a bit of directed poking, for example). I have yesterday's (verbose) dmesg.boot for the build machine up at http://www.catwhisker.org/~david/FreeBSD/history/freebeast.13_dmesg.txt; based on that, it looks as if what showed up yesterday at that point was: ... da3: Delete methods: <NONE(*),ZERO> GEOM: new disk da3 (da3:umass-sim0:0:0:3): PREVENT ALLOW MEDIUM REMOVAL not supported. mountroot: waiting for device /dev/ada0s4a... atrtc0: providing initial system time start_init: trying /sbin/init GEOM_PART: partition 1 on (diskid/DISK-1350095E5057, MBR) is not aligned on 4096 bytes GEOM_PART: partition 2 on (diskid/DISK-1350095E5057, MBR) is not aligned on 4096 bytes ... GEOM_PART: partition 2 on (diskid/DISK-1350095E5057, MBR) is not aligned on 4096 bytes GEOM_PART: partition 3 on (diskid/DISK-1350095E5057, MBR) is not aligned on 4096 bytes lo0: link state changed to UP re0: link state changed to DOWN cpuctl: access to MSR registers/cpuid info. CPU: Intel(R) Core(TM) i7-4790 CPU _at_ 3.60GHz (3591.76-MHz K8-class CPU) Origin="GenuineIntel" Id=0x306c3 Family=0x6 Model=0x3c Stepping=3 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> .... I will go ahead and reboot the laptop in the mean time. Peace, david -- David H. Wolfskill david_at_catwhisker.org It's unfortunate that so many Senate Republicans forswore their Oaths of Office. See http://www.catwhisker.org/~david/publickey.gpg for my public key.
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:23 UTC