Re: Panic with PF on current.
> 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) > This seems to be a lock ordering issue between ZFS and devfs. It appears to have been around for a while too. I found PR 142878 with the same witness warning. Regards, Kristof ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Panic with PF on current.
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 enabled) > > 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.com/VerKnowSys/ServeD-OS/blob/master/etc/src.conf > My loader.conf: > https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/loader.conf.served > My sysctl.conf: > https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/sysctl.conf.served > > I’m using Vmware Fusion 7.0 pro as host. > > Thank you :) Hope this will help someone, let me know if I can help somehow > further. Please email kp@ [next time] if you run into issues with pf(4). If the issues have not been fixed/identified already, please file bugs. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Panic with PF on current.
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/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.com/VerKnowSys/ServeD-OS/blob/master/etc/src.conf My loader.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/loader.conf.served My sysctl.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/sysctl.conf.served I’m using Vmware Fusion 7.0 pro as host. Thank you :) Hope this will help someone, let me know if I can help somehow further. -- kind regards Daniel (dmilith) Dettlaff signature.asc Description: Message signed with OpenPGP using GPGMail
Panic with PF on current.
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 My make.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/make.conf My src.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/src.conf My loader.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/loader.conf.served My sysctl.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/sysctl.conf.served I’m using Vmware Fusion 7.0 pro as host. I catched that panic on main system console (verbose boot turned on): http://s.verknowsys.com/33551a89eda736059df6dcb35ea4eda3.png with bt: http://s.verknowsys.com/caeb3389d9e7399793a12c44f5760466.png Thank you :) Hope this will help someone, let me know if I can help somehow further. -- kind regards Daniel (dmilith) Dettlaff signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Panic with PF on current.
> 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/VerKnowSys/ServeD-OS/blob/master/etc/make.conf > My src.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/src.conf > My loader.conf: > https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/loader.conf.served > My sysctl.conf: > https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/sysctl.conf.served > > I’m using Vmware Fusion 7.0 pro as host. > > I catched that panic on main system console (verbose boot turned on): > > http://s.verknowsys.com/18bfec6f00e939e0b93952a4117fda34.png > > As you see it looks related to pfsync. Hence I tried to disable pf for test, > but just after `service pf stop` more “detailed panic" happened: > > http://s.verknowsys.com/a1500912956930aa9eda16383347657c.png > and with some backtrace: > http://s.verknowsys.com/9f413eec8be03faf898208ef9d2fe555.png > > My build (kernel + world + HBSD patches) is here: > http://served.verknowsys.com/ServeD-OS-Base-11.0-v0.11.7-amd64.tar.xz if you > want to try to reproduce it maybe. > > > Panic will happen only if “pf" kernel module is loaded. Since I disabled “pf" > and “pflog", system works as expected, no panic at all. > > > This issue was also reported to #HardenedBSD since I’m not sure it’s related > to hardening patches or not. (It seems not related at the moment). > > Thank you :) Hope this will help someone, let me know if I can help somehow > further. CCing kp. What version of FreeBSD (revision, git hash) is this based on? Thanks, -NGie ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Panic with PF on current.
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.com/VerKnowSys/ServeD-OS/blob/master/etc/src.conf My loader.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/loader.conf.served My sysctl.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/sysctl.conf.served I’m using Vmware Fusion 7.0 pro as host. I catched that panic on main system console (verbose boot turned on): http://s.verknowsys.com/18bfec6f00e939e0b93952a4117fda34.png As you see it looks related to pfsync. Hence I tried to disable pf for test, but just after `service pf stop` more “detailed panic" happened: http://s.verknowsys.com/a1500912956930aa9eda16383347657c.png and with some backtrace: http://s.verknowsys.com/9f413eec8be03faf898208ef9d2fe555.png My build (kernel + world + HBSD patches) is here: http://served.verknowsys.com/ServeD-OS-Base-11.0-v0.11.7-amd64.tar.xz if you want to try to reproduce it maybe. Panic will happen only if “pf" kernel module is loaded. Since I disabled “pf" and “pflog", system works as expected, no panic at all. This issue was also reported to #HardenedBSD since I’m not sure it’s related to hardening patches or not. (It seems not related at the moment). Thank you :) Hope this will help someone, let me know if I can help somehow further. -- kind regards Daniel (dmilith) Dettlaff signature.asc Description: Message signed with OpenPGP using GPGMail