This is a partial report, the machine in question is now at the 'syncing disks' stage of 'boot dump' from ddb.
Anyway - I noticed that while doing a sysupgrade -s on my laptop[1] that the process hung for a number of minutes apparently while trying to configure the iwm0 interface: https://www.bsdly.net/~peter/20210301/20210301_103647.jpg When it finally proceeded from that point, I caught a glimpse of it at the boot: prompt with the message bsd.upgrade is not u+x but it proceeded to boot anyway. When I attempted a 'doas sendbug', I got a panic: "panic: config_detach: forced detach of rtsx0 failed (45)" See https://www.bsdly.net/~peter/20210301/20210301_111422.jpg https://www.bsdly.net/~peter/20210301/20210301_120803.jpg further trace etc info https://www.bsdly.net/~peter/20210301/20210301_120803.jpg and it seems to descend into iwm here: https://www.bsdly.net/~peter/20210301/20210301_121014.jpg https://www.bsdly.net/~peter/20210301/20210301_121055.jpg https://www.bsdly.net/~peter/20210301/20210301_121139.jpg After which I rebooted. The next attempt at 'doas sendbug' got me https://www.bsdly.net/~peter/20210301/20210301_132209.jpg https://www.bsdly.net/~peter/20210301/20210301_132310.jpg https://www.bsdly.net/~peter/20210301/20210301_132439.jpg https://www.bsdly.net/~peter/20210301/20210301_132504.jpg https://www.bsdly.net/~peter/20210301/20210301_132530.jpg https://www.bsdly.net/~peter/20210301/20210301_135417.jpg https://www.bsdly.net/~peter/20210301/20210301_135459.jpg When the machine comes back I should be able to extract more information such as a fresh dmesg. All the best, Peter [1] Still the same machine as described in https://bsdly.blogspot.com/2017/07/openbsd-and-modern-laptop.html -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
