On Fri, Oct 08 2021, Jeremie Courreges-Anglas <j...@wxcvbn.org> wrote: > riscv64.ports was running dpb(1) with two other members in the build > cluster. A few minutes ago I found it in ddb(4). The report is short, > sadly, as the machine doesn't return from the 'bt' command. > > The machine is acting both as an NFS server and and NFS client. > > OpenBSD/riscv64 (riscv64.ports.openbsd.org) (console)
OpenBSD/riscv64 (riscv64.ports.openbsd.org) (console) login: panic: mtx 0xffffffc22b7c5200: locking against myself Stopped at panic+0xfe: addi a0,zero,256 TID PID UID PR FLAGS PFLAGS CPU COMMAND 502511 85783 55 0x2 0 2 c++ 492656 41392 55 0x2 0 3 c++ 199505 3143 55 0x2 0 0 c++ * 21652 39857 55 0x2 0 1K c++ panic() at panic+0xfa panic() at mtx_enter+0xd2 mtx_enter_try() at pmap_fault_fixup+0x46 pmap_fault_fixup() at do_trap_supervisor+0xd4 do_trap_supervisor() at cpu_exception_handler_supervisor+0x78 cpu_exception_handler_supervisor() at pool_get+0x76 pool_get() at pmap_vp_enter+0xec https://www.openbsd.org/ddb.html describes the minimum info required in bug reports. Insufficient info makes it difficult to find and fix bugs. ddb{1}> show panic *cpu1: mtx 0xffffffc22b7c5200: locking against myself ddb{1}> One day I'll learn how to use ddb and uvm. Not today. :) -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
