Date: Thu, 16 Sep 2004 03:53:58 -0000 From: Pyun YongHyeon <yongari@kt-is.co.kr> To: pf4freebsd@freelists.org Subject: [pf4freebsd] Re: pf errors meaning Message-ID: <20031006022328.GB735@kt-is.co.kr> In-Reply-To: <3F803A15.9060405@dequim.ist.utl.pt> References: <1065107810.3f7c4162b252a@mrna.ist.utl.pt> <19920876018.20031002175427@love2party.net> <3F7CB204.9030506@dequim.ist.utl.pt> <20031003075152.GA16760@kt-is.co.kr> <3F803A15.9060405@dequim.ist.utl.pt>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 05, 2003 at 04:34:45PM +0100, Bruno Afonso wrote: > Pyun YongHyeon wrote: >=20 > > You can see the offending function _fget() in /sys/kern/kern_descrip= .c. > > I believe this error is not related with FreeBSD pf. > > However, you don't have traces so I can't sure that. >=20 > yes :-( >=20 > > Did you have two kernel modules in your system?(/boot/kernel and > > /usr/local/modules) Did you patch your kernel after installing > > FreeBSD pf? Can you tell me the exact procure you used while loading > > and unloading pf? Can you post your rule file and comment on your > > network setup? Did your rule file have table rules? >=20 > Only have one model. > I used stock kernel from releng_5_1 with only some options added. :-) > I'm using a port based rc.d script... I only changed the file paths. > I use tables... I have a 10.10.0.0/20 table, and some other tables=20 > collecting a lot of /24 and /22 networks. > I have also removed one synproxy rule I had for http... Since I had=20 > problems with it in the past, I removed it once again. (re-introduced = it=20 > when installing 1.66) >=20 > > No. It does not necessarily mean FreeBSD pf is error free. There > > might be bugs creeping through pf module. >=20 > I have had no more panics since I removed the synproxy rule and disabl= ed=20 > dnscache. But this is irrelevant as we can't really know what caused t= he=20 > panics. :-( > I never heard anyone having dnscache panics, so I found that *odd*. >=20 Interesting. Then I'll check synproxy code. However, as I didn't see any related problems up to date, it may take a long time to scrutinize. >=20 > > > the break into ddb as I can't afford the box down for a couple ho= urs :-( > > > Unfortunately, someone pressed the restart button before I could = get to=20 > > > ddb via serial console... > > >=20 > > You dont't have to let the box down for a while. At least, we need a > > trace report to identify the problem. At DDB propmt you can invoke > > 'trace' command and write down the output. If you have enabled kerne= l > > debugging options, you may get valuable crash dump file. This is the > > most perferrable one. >=20 > I'm not working full time, this is a college and I'm a poor student=20 > being explored. :-) > I am going to look into crash dumps. >=20 Regards, Pyun YongHyeon --=20 Pyun YongHyeon <http://www.kr.freebsd.org/~yongari>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031006022328.GB735>