On 4/22/19 3:28 PM, Kristof Provost wrote:
On 22 Apr 2019, at 12:25, Enji Cooper wrote:
Either the sys/netinet/ or sys/netipsec/ tests triggered the panic.
Not sure which right now.
That looks to be happening during a vnet jail teardown, so it’s likely
the sys/netipsec or sys/netpfil/pf tests
On 22 Apr 2019, at 12:25, Enji Cooper wrote:
Either the sys/netinet/ or sys/netipsec/ tests triggered the panic.
Not sure which right now.
That looks to be happening during a vnet jail teardown, so it’s likely
the sys/netipsec or sys/netpfil/pf tests.
I’ve done a quick test with the pf tests
Hi Hans,
> On Apr 22, 2019, at 1:32 AM, Hans Petter Selasky wrote:
>
> On 4/22/19 10:10 AM, Hans Petter Selasky wrote:
>> On 4/22/19 9:52 AM, Enji Cooper wrote:
>>>
On Apr 22, 2019, at 12:27 AM, Hans Petter Selasky
wrote:
Author: hselasky
Date: Mon Apr 22 07:27:24 20
On 4/22/19 3:28 PM, Kristof Provost wrote:
On 22 Apr 2019, at 12:25, Enji Cooper wrote:
Either the sys/netinet/ or sys/netipsec/ tests triggered the panic.
Not sure which right now.
That looks to be happening during a vnet jail teardown, so it’s likely
the sys/netipsec or sys/netpfil/pf tests
On 22 Apr 2019, at 12:25, Enji Cooper wrote:
Either the sys/netinet/ or sys/netipsec/ tests triggered the panic.
Not sure which right now.
That looks to be happening during a vnet jail teardown, so it’s likely
the sys/netipsec or sys/netpfil/pf tests.
I’ve done a quick test with the pf tests
Hi Hans,
> On Apr 22, 2019, at 1:32 AM, Hans Petter Selasky wrote:
>
> On 4/22/19 10:10 AM, Hans Petter Selasky wrote:
>> On 4/22/19 9:52 AM, Enji Cooper wrote:
>>>
On Apr 22, 2019, at 12:27 AM, Hans Petter Selasky
wrote:
Author: hselasky
Date: Mon Apr 22 07:27:24 20
