On Sat, Apr 18, 2020 at 11:28 PM Thomas de Grivel <billi...@gmail.com> wrote:
> I got this error last night on an OpenBSD 6.6-stable amd64 on which I > recently enabled IKEv2 : > > > kernel: double fault trap, code=0 > > Stopped at rtable_l2+0x27: callq srp_enter+0x4 > That was the *complete* output from ddb? Really? Not a screen full of backtrace after that showing that it has a very deep stack? As you might guess from my questions: the #1 cause of a double fault traps are kernel bugs causing deep recursion where it runs off the end of the allocated stack, triggering a page fault exception which itself faults when it can't write the stack frame for the page fault. That "fault while trying to fault" results in a double fault, which I configured to be delivered on its own stack so that we can report this. Fixing the deep recursion in this case would require you providing the full stack trace to the list, so that the correct parties can see it and identify where it's incorrectly looping. Philip Guenther
