> On 06 Nov 2015, at 01:12, Daniel Dettlaff wrote:
> I have interesting verbose output with backtrace (not panic) from one of my
> VMs: http://s.verknowsys.com/f0d457ce9420399baaf531012c33eb81.png
> It’s triggered by autostarting jail on bridged vlan interface (no VNET
> feature enabled)
>
Thi
On Thu, Nov 5, 2015 at 4:12 PM, Daniel Dettlaff wrote:
> Hello.
>
> I have interesting verbose output with backtrace (not panic) from one of my
> VMs: http://s.verknowsys.com/f0d457ce9420399baaf531012c33eb81.png
> It’s triggered by autostarting jail on bridged vlan interface (no VNET
> feature e
Hello.
I have interesting verbose output with backtrace (not panic) from one of my
VMs: http://s.verknowsys.com/f0d457ce9420399baaf531012c33eb81.png
It’s triggered by autostarting jail on bridged vlan interface (no VNET feature
enabled)
I built kernel using this config:
https://github.com/VerK
Hello.
I have my second kernel panic, related with “MAC_PORTACL” kernel module loading
in CURRENT.
The only thing to do is to put mac_portacl_load=“YES” in loader.conf and boot
machine.
I built kernel using this config:
https://github.com/VerKnowSys/ServeD-OS/blob/master/kernel/VERKNOWSYS-11.0
> On Nov 1, 2015, at 10:54, Daniel Dettlaff wrote:
>
> Hello.
>
> I have my first kernel panic, probably related to pf/pflog in CURRENT:
>
> I built kernel using this config:
> https://github.com/VerKnowSys/ServeD-OS/blob/master/kernel/VERKNOWSYS-11.0
> My make.conf:
> https://github.com/Ver
Hello.
I have my first kernel panic, probably related to pf/pflog in CURRENT:
I built kernel using this config:
https://github.com/VerKnowSys/ServeD-OS/blob/master/kernel/VERKNOWSYS-11.0
My make.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/make.conf
My src.conf: https://github.c
