From owner-freebsd-current@FreeBSD.ORG Mon Apr 19 01:55:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 505AB16A4CE for ; Mon, 19 Apr 2004 01:55:52 -0700 (PDT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEFC743D45 for ; Mon, 19 Apr 2004 01:55:51 -0700 (PDT) (envelope-from marks@dell-laptop.6bone.nl) Received: by postman.ripe.net (Postfix, from userid 8) id C85544ED3F; Mon, 19 Apr 2004 10:55:50 +0200 (CEST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 82FA34E058; Mon, 19 Apr 2004 10:55:50 +0200 (CEST) Received: from dell-laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id i3J8tmc4027383; Mon, 19 Apr 2004 10:55:49 +0200 Received: (nullmailer pid 3388 invoked by uid 1001); Mon, 19 Apr 2004 08:55:48 -0000 Date: Mon, 19 Apr 2004 10:55:48 +0200 From: Mark Santcroos To: Johan Pettersson Message-ID: <20040419085548.GC805@laptop.6bone.nl> References: <1082303878.855.6.camel@klamath.syndrom23.de> <20040418202011.GA1000@laptop.6bone.nl> <20040419104141.629c050e.manlix@demonized.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040419104141.629c050e.manlix@demonized.net> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: N 0.000000 / 0.0 / 0.0 / disabled X-RIPE-Signature: c4ae47f08e776573e967b5ffaa612333 cc: andreas.kohn@gmx.net cc: current@freebsd.org Subject: Re: Page fault in rt_newaddrmsg on gif0 destruction X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 08:55:52 -0000 On Mon, Apr 19, 2004 at 10:41:41AM +0200, Johan Pettersson wrote: > I have had this problem on my server since I first installed 5.0-RELEASE > on it. Running 5.2.1-RELEASE-p4 now and the problem is still there. That was (most likely) a different issue as this was only introduced 2 days ago or so. Mark