Hi, I run a 2G/100G virtual machine at openbsd.amsterdam freshly upgraded from stable to the latest snapshot and I've figured out the panic by the two steps detailed there:
1. The system has a root @reboot crontab entry that start a tmux session in the background (so always detached from a TTY during the whole procedure) + a /root/.tmux.conf which is some copy of my usual tmux confi, which appears to call a script that does `apm -b` (we have our quick workaround by removing it). The tmux session and the programs ran inside started just fine at the exception of the tmux session itself. By attaching that special session created @reboot, I noticed that tmux somehow fallback'd on the builtin's default config. (Green bottom status-bar and defaults keybinds). Which indeed indicated me that something went wrong. 2. It's only when I started tmux manually that the .tmux.conf calling `apm -b` triggerred the crash: # tmux ^M campfire.01:ksh* <-- my "on-top" status-bar was loaded this time uvm_fault(0xfffffd8078416cf0, 0x39c, 0, 2) -> e kernel: page fault trap, code=2 Stopped at acpiopen+0x85: orb $0x1,0x39c(%r13) TID PID UID PRFLAGS PFLAGS CPU COMMAND *173406 19781 0 0x2 0 0 apm acpiopen(5300,1,2000,ffff8000ffff0b08) at acpiopen+0x85 spec_open(ffff800021648598) at spec_open+0xe0 VOP_OPEN(fffffd803bb6bcb0,1,fffffd80691bf550,ffff8000ffff0b08) at VOP_OPEN+0x4e vn_open(ffff8000216487b0,1,0) at vn_open+0x275 doopenat(ffff8000ffff0b08,ffffff9c,f9805daef3b,0,0,ffff800021648980) at doopena t+0x1d1 syscall(ffff8000216489f0) at syscall+0x364 Xsyscall() at Xsyscall+0x128 end of kernel end trace frame: 0x775e645c8040, count: 8 Thanks you for having a look. This is just a surface analysis I was able to do for now. I will take the necessary time on my side to setup the build environment on this host and be ready to test patches. PS: I would also like to thanks misha for his genius idea and hosting services I use proudly since 2020. dmesg: OpenBSD 7.3-current (GENERIC) #1267: Fri Aug 4 12:41:36 MDT 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 2130694144 (2031MB) avail mem = 2046570496 (1951MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf3740 (10 entries) bios0: vendor SeaBIOS version "1.14.0p3-OpenBSD-vmm" date 01/01/2011 bios0: OpenBSD VMM acpi at bios0 not configured cpu0 at mainbus0: (uniprocessor) cpu0: Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz, 2300.04 MHz, 06-2d-07 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,CX8,SEP,PGE,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,HV,NXE,PAGE1GB,LONG,LAHF,ITSC,MD_CLEAR,MELTDOWN cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 15MB 64b/line 20-way L3 cache cpu0: smt 0, core 0, package 0 cpu0: using VERW MDS workaround pvbus0 at mainbus0: OpenBSD pvclock0 at pvbus0 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "OpenBSD VMM Host" rev 0x00 virtio0 at pci0 dev 1 function 0 "Qumranet Virtio RNG" rev 0x00 viornd0 at virtio0 virtio0: irq 3 virtio1 at pci0 dev 2 function 0 "Qumranet Virtio Network" rev 0x00 vio0 at virtio1: address fe:e1:bb:6f:67:15 virtio1: irq 5 virtio2 at pci0 dev 3 function 0 "Qumranet Virtio Storage" rev 0x00 vioblk0 at virtio2 scsibus1 at vioblk0: 1 targets sd0 at scsibus1 targ 0 lun 0: <VirtIO, Block Device, > sd0: 102400MB, 512 bytes/sector, 209715200 sectors virtio2: irq 6 virtio3 at pci0 dev 4 function 0 "OpenBSD VMM Control" rev 0x00 vmmci0 at virtio3 virtio3: irq 7 isa0 at mainbus0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns8250, no fifo com0: console vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets root on sd0a (ed63eb54292b967c.a) swap on sd0b dump on sd0b -- xs
