On 25.2.2022. 23:22, Alexander Bluhm wrote: > On Fri, Feb 25, 2022 at 10:21:50PM +0100, Hrvoje Popovski wrote: >> On 24.2.2022. 22:42, Alexander Bluhm wrote: >>> Hi, >>> >>> Hrvoje reported some crashes with pfsync, IPsec and parallel >>> forwarding. Some locks were missing around the tdb flags in pfsync. >> >> before trying this diff i wanted to see if i could still trigger panic >> with sasyncd setup and parallel forwarding diff. and here's panic >> >> r620-2# uvm_fault(0xffffffff822c8f70, 0xe7, 0, 2) -> e >> kernel: page fault trap, code=0 >> Stopped at ipsp_delete_acquire+0x61: movq %rax,0xe8(%rcx) >> TID PID UID PRFLAGS PFLAGS CPU COMMAND >> 486149 44310 68 0x1000010 0 3 sasyncd >> 330850 23209 0 0x14000 0x200 4 softnet >> 48580 70158 0 0x14000 0x200 1 softnet >> 4459 11329 0 0x14000 0x200 2 softnet >> 70953 79831 0 0x14000 0x200 5 softnet >> *303117 65399 0 0x14000 0x40000200 0 softclock >> ipsp_delete_acquire(fffffd837c504c30) at ipsp_delete_acquire+0x61 >> ipsp_delete_acquire_timo(fffffd837c504c30) at ipsp_delete_acquire_timo+0x20 >> softclock_thread(ffff8000fffff500) at softclock_thread+0x13b >> end trace frame: 0x0, count: 12 >> 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{0}> >> >> >> now i will try all the same with this diff .. > > I just commited it before I saw your mail. I hope the best. >
I'm hitting committed diff for a sometime and by now boxes should panic, but they running just fine .. i will still play with sasyncd setup, maybe something comes up
