From owner-freebsd-stable Tue Nov 14 10:53:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id CF6AA37B4E5 for ; Tue, 14 Nov 2000 10:53:43 -0800 (PST) Received: from stpcdz4q650 (veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id 57BED8C3E; Tue, 14 Nov 2000 12:53:34 -0600 (CST) Message-ID: <003001c04e6c$8e3a6500$c70b200a@FairIsaac.com> From: "Thomas T. Veldhouse" To: "Wilko Bulte" , "Rich Wales" Cc: References: <20001114002123.64508.richw@wyattearp.stanford.edu> <20001114074905.B333@freebie.demon.nl> Subject: Re: Bridging code in 4.2RC1 still not fixed Date: Tue, 14 Nov 2000 12:56:09 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It has been mentioned in the past many many times - and promptly forgotton just as many times. Forgive the harsh sounding critcism - just trying to get attention called to this issue. It is not at all hard to reproduce - but it does not log anything to the system logs when this sort of crash happens. The fact that nobody has looked at this over the course of the last year really surprises me. Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "Wilko Bulte" To: "Rich Wales" Cc: Sent: Tuesday, November 14, 2000 12:49 AM Subject: Re: Bridging code in 4.2RC1 still not fixed > On Mon, Nov 13, 2000 at 04:34:03PM -0800, Rich Wales wrote: > > Marko Cuk wrote: > > > > > I installed 4.2RC1 from ISO and the bridging code in > > > conjuction with ipfw is still bad and it still crashes > > > machine after a few seconds of work. > > > > In case it will help any, I tried configuring a 3.4-RELEASE system > > as a bridge a few weeks ago, but it suffered random crashes too. > > > > The crashes were "fatal trap 12" (page fault while in kernel mode), > > in the routine in_cksum(), called from udp_input(). > > > > When I reconfigure the system to work as a conventional (non-bridge) > > IP router, it's solid as a rock. Again, I'm using 3.4-RELEASE; I do > > plan to upgrade to 4.something eventually, but not just yet. > > > > I posted this to comp.unix.bsd.freebsd.misc on October 14. I asked > > if anyone knew if the problem was fixed in the 4.* versions, but no > > one ever replied. I didn't submit a PR because the problem was with > > 3.4-RELEASE and I assumed no one would be interested in pursuing it. > > That is not a really valid assumption. But I agree that the focus is on 4.x > and -current. Bugs reported on 3.x are crosschecked (by most committers) to > the 4.x codestream. > > I strongly suggest to sendpr the problem against 4.2-beta! > > -- > Wilko Bulte Arnhem, the Netherlands > wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message