Date: Sun, 1 Nov 2015 11:25:08 -0800 From: NGie Cooper <yaneurabeya@gmail.com> To: Daniel Dettlaff <dmilith@gmail.com> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, Kristof Provost <kp@freebsd.org> Subject: Re: Panic with PF on current. Message-ID: <E1641CC2-BC0C-4A07-BDB5-A044696985AD@gmail.com> In-Reply-To: <E9BCA1E2-EF3D-4DBD-8540-37CD8711D054@gmail.com> References: <E9BCA1E2-EF3D-4DBD-8540-37CD8711D054@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Nov 1, 2015, at 10:54, Daniel Dettlaff <dmilith@gmail.com> wrote: >=20 > Hello. >=20 > I have my first kernel panic, probably related to pf/pflog in CURRENT: >=20 > 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= >=20 > I=E2=80=99m using Vmware Fusion 7.0 pro as host. >=20 > I catched that panic on main system console (verbose boot turned on): >=20 > http://s.verknowsys.com/18bfec6f00e939e0b93952a4117fda34.png >=20 > As you see it looks related to pfsync. Hence I tried to disable pf for = test, but just after `service pf stop` more =E2=80=9Cdetailed panic" = happened: >=20 > http://s.verknowsys.com/a1500912956930aa9eda16383347657c.png > and with some backtrace: > http://s.verknowsys.com/9f413eec8be03faf898208ef9d2fe555.png >=20 > 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. >=20 >=20 > Panic will happen only if =E2=80=9Cpf" kernel module is loaded. Since = I disabled =E2=80=9Cpf" and =E2=80=9Cpflog", system works as expected, = no panic at all. >=20 >=20 > This issue was also reported to #HardenedBSD since I=E2=80=99m not = sure it=E2=80=99s related to hardening patches or not. (It seems not = related at the moment). >=20 > 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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1641CC2-BC0C-4A07-BDB5-A044696985AD>