On Mon, Jun 04, 2018 at 08:30:55PM +0200, Alexander Bluhm wrote:
> On Mon, Jun 04, 2018 at 01:23:53AM +0200, Alexander Bluhm wrote:
> > On my amd64 regress machine I see a witness_warn panic now.
>
> It is triggered by /usr/src/regress/sys/kern/mount. With visa@'s
> improved stack trace I see:
My serial console server mangled the output. Here is better one
from ddb> dmesg.
userret: returning with the following locks held:
exclusive rrwlock inode r = 0 (0xffffff023d492b48) locked @ /usr/src/sys/ufs/uf
s/ufs_vnops.c:1559
#0 witness_lock+0x254
#1 _rw_enter+0x29b
#2 _rrw_enter+0x3e
#3 VOP_LOCK+0x3d
#4 vn_lock+0x34
#5 vget+0xf7
#6 cache_lookup+0x217
#7 ufs_lookup+0x112
#8 VOP_LOOKUP+0x4f
#9 vfs_lookup+0x27e
#10 namei+0x226
#11 vn_open+0xcf
#12 doopenat+0x1af
#13 syscall+0x32a
#14 Xsyscall_untramp+0xc0
panic: witness_warn
Stopped at db_enter+0x12: popq %r11
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*340900 45836 0 0x100003 0 2 cp
db_enter() at db_enter+0x12
panic() at panic+0x138
witness_warn(4daf31f665ef77b2,ffff800021f74290,ffff8000ffff6960) at witness_war
n+0x4fb
userret(184acb3033f01432) at userret+0x1a0
syscall(e44e1a254de07323) at syscall+0x423
Xsyscall_untramp(6,0,0,0,0,2) at Xsyscall_untramp+0xc0
end of kernel
end trace frame: 0x7f7ffffd19b0, count: 9
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports. Insufficient info makes it difficult to find and fix bugs.
