Quick report: riscv64-1.p paniced yesterday. I don't remember having
hit this kind of crash before and I can't tell whether it's the "usual"
memory corruption bug I hit since months. The kernel is
OpenBSD 7.2-current (GENERIC.MP) #7: Sun Nov 6 07:49:26 MST 2022
[email protected]:/sys/arch/riscv64/compile/GENERIC.MP
which is -current from that day plus the mmap/munmap/mprotect syscalls
unlocked patch
As playing with ddb(4) on riscv64 puts you at risk of a freeze and the
machine is remote with no remote PDU, I won't play with random commands.
(sometimes just mach ddbcpu N freezes). I would welcome suggestions
about which commands would be most useful in this stuation.
OpenBSD/riscv64 (riscv64-1.ports.openbsd.org) (console)
login: panic: smashed stack in uvm_fault_lower_lookup
Stopped at panic+0x106: addi a0,zero,256 TID PID UID PR
FLAGS PFLAGS CPU COMMAND
*321951 95523 55 0x2 0 3 cc
297450 49971 55 0x2 0 0 c++
329612 78965 55 0x2 0 1 cc
87162 99025 55 0x2 0 2 c++
panic() at panic+0x106
igc_acquire_phy_base() at igc_acquire_phy_base
uvm_fault_wire() at uvm_fault_wire
uvm_fault_lower() at uvm_fault_lower+0x4c
uvm_fault() at uvm_fault+0x150
do_trap_user() at do_trap_user+0x116
cpu_exception_handler_user() at cpu_exception_handler_user+0x7c
end of kernel
end trace frame: 0x19c71, count: 8
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{3}> show panic
*cpu3: smashed stack in uvm_fault_lower_lookup
ddb{3}>
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
