Franco Fichtner

From a different user, same same but different: ``` ddb.txt06000014000014633270447 7104 ustarrootwheeldb:0:kdb.enter.default> run lockinfo db:1:lockinfo> show locks No such command; use "help" to list available commands db:1:lockinfo> show alllocks No...

And the last one: ``` ddb.txt06000014000014632525416 7102 ustarrootwheeldb:0:kdb.enter.default> run lockinfo db:1:lockinfo> show locks No such command; use "help" to list available commands db:1:lockinfo> show alllocks No such command; use "help"...

I collected all submitted panics for the scope of this ticket. One of this might be related to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279653 https://reviews.freebsd.org/D45690 ``` Fatal trap 12: page fault while in kernel mode...

First two: `ip6_input()` has no significant changes and since both panics lead to `ip6_forward()` AND `ip6_tryforward()` it's suspicious as both called functions can't really crash for the same reason in...

The ip6_input() one is still happening. I'll issue a debug kernel in RC2 to get to the bottom of it.

`ip6_forward()` commit 9cb6d71f6a41d but still unclear about the `ip6_tryforward()`

`ip6_tryforward()` seems to be buggy upstream, because https://redmine.pfsense.org/issues/15640

I still don't have a debug kernel for this, but we're still looking.

@dseven would you mind installing a debug kernel and sending me the resulting /var/crash/vmcore.* files? It should be easy to fix with a working vmcore, but I don’t have one...

@dseven perfect, got it and it works with the right panic path (sometimes these vmcores segfault in python). I will look at it tomorrow morning. Cheers, Franco