On 1.6.2022. 0:27, Stuart Henderson wrote:
> I accidentally updated a router to -current instead of 7.1 and hit this.
> (Thanks sysupgrade - it was running a 7.0-stable kernel before...)
>
> Unfortunately it runs with ddb.panic=0 and this time it hanged, I won't
> have time to figure anything out with it when I get it back online, but
> might be able to do so later in the week.
>
> Thought I'd send it out now as a heads-up as much as anything (and maybe
> someone has an idea). Boot messages below.
Hi,
I think that this is relayd panic. I'm seeing this too while testing TCP
Large Receive Offloading. I will send proper bug report just in next mail...
r420-1# rcctl -f start relayd
relayd(ok)
r420-1# uvm_fault(0xfffffd8571260e70, 0x0, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at pf_find_or_create_ruleset+0x1c: movb 0(%rdi),%al
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*307542 67712 89 0x1100012 0 2K relayd
pf_find_or_create_ruleset(0) at pf_find_or_create_ruleset+0x1c
pfr_add_tables(b0caf510000,1,ffff80000104343c,10000000) at
pfr_add_tables+0x6ae
pfioctl(4900,c450443d,ffff800001043000,3,ffff80002271e550) at pfioctl+0x1daf
VOP_IOCTL(fffffd857631f1f8,c450443d,ffff800001043000,3,fffffd862f7d6960,ffff80002271e550)
at VOP_IOCTL+0x5c
vn_ioctl(fffffd854c7a2308,c450443d,ffff800001043000,ffff80002271e550) at
vn_ioctl+0x75
sys_ioctl(ffff80002271e550,ffff8000227f5b40,ffff8000227f5b90) at
sys_ioctl+0x2c4
syscall(ffff8000227f5c00) at syscall+0x374
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7f7ffffd3d40, count: 7
https://www.openbsd.org/ddb.html describes the minimum info required in
bug reports. Insufficient info makes it difficult to find and fix bugs.
