From owner-freebsd-stable Fri Mar 9 10:30:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from amx.mathieu.org (modemcable161.243-201-24.mtl.mc.videotron.ca [24.201.243.161]) by hub.freebsd.org (Postfix) with ESMTP id BA8D737B71E for ; Fri, 9 Mar 2001 10:30:08 -0800 (PST) (envelope-from mathieu@amx.dyn.dhs.org) Received: from amx.dyn.dhs.org (localhost [127.0.0.1]) by amx.mathieu.org (Postfix) with ESMTP id 323FB3FCD; Fri, 9 Mar 2001 13:39:04 -0500 (EST) Message-ID: <3AA92348.88B96F50@amx.dyn.dhs.org> Date: Fri, 09 Mar 2001 13:39:04 -0500 From: Mathieu Reply-To: mathieu@amx.dyn.dhs.org X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-BETA i386) X-Accept-Language: fr-CA, en MIME-Version: 1.0 To: "Rodney W. Grimes" Cc: "Dmitry A. Yanko" , freebsd-stable@FreeBSD.ORG Subject: Re: panic, ipfw broken in stable? References: <200103091822.KAA29463@gndrsh.dnsmgr.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" wrote: > > > In /etc/rc.conf: > > firewall_enable="YES" > > (panic only in this case) > > > > > > fault addr. = 0x50 > > fault code = sup. write, page not present > > ip = 0x8:0xc01a44cb > > sp = 0x10:0xc02e0ad0 > > fp = 0x10:0xc02e0b50 > > cs = base 0x0, limit 0xfffff, type 0x1b > > = dpl 0, pres. 1, def32 1, grap 1 > > p. eflags = int. enable, resume, IOPL=0 > > cur. proc = Idle > > int. mask = net > > trap. num = 12 > > panic: page fault > ... > > Since it looks like you haven't seen the ongoing thread about > your problem, I thought I would follow up to your original email. > > Right now we have a hypothosis that a MFC of the stats counters > to ip_output is causing your panic. I would like to try and > duplicate that on a system here, but I need some configuration > data from your system, particularly the ipfw rule set that > is triggering the problem. (this applies to anyone who has > seen this panic.) > > -- > Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message I also had the same problem. I removed those DummyNet rules, and I never saw the panic again ! rule add deny tcp from any to any via dc0 gid anonymous rule add pipe 1 ip from any to any out gid anonymous rule add pipe 2 ip from any to any in gid anonymous rule pipe 1 config bw 128Kbit/s queue 50Kbytes rule pipe 2 config bw 256Kbit/s queue 50Kbytes -- Mathieu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message