From owner-freebsd-net@FreeBSD.ORG Thu May 12 13:57:35 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F8F516A4CE; Thu, 12 May 2005 13:57:35 +0000 (GMT) Received: from dis.dis.com (dis.dis.com [64.7.69.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E54243D7E; Thu, 12 May 2005 13:57:34 +0000 (GMT) (envelope-from freebsd@dis.com) Received: from dilbert (dilbert.dis.com [192.168.1.50]) by dis.dis.com (8.13.2/8.13.2) with SMTP id j4CDvWwE056097; Thu, 12 May 2005 06:57:34 -0700 (PDT) From: "Mark Klein" To: , "kame" Date: Thu, 12 May 2005 06:57:32 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: Importance: Normal cc: freebsd-net@freebsd.org Subject: RE: Forward: Page Fault in in6_purgeaddr X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2005 13:57:35 -0000 > -----Original Message----- > From: gnn@freebsd.org [mailto:gnn@freebsd.org] > Sent: Wednesday, May 11, 2005 6:30 PM > To: kame > Cc: freebsd-net@freebsd.org; Mark Klein > Subject: Forward: Page Fault in in6_purgeaddr > > > Forwarded to the kame folks as well as they might have already fixed > this in their own code. > > Can you tell us what else is going on when this happens? > > Is it random? It appears to happen at close to 24 hour periods ... almost 23 hours and 50 minutes, give or take a few minutes. Happens once per day only. IPv6 is NOT explicitly used at this site. Chasing the code makes it appear it could be related to the PPP tunnels, which I've disabled as of this AM to see what happens. I ran a TCPDUMP IP6 for 30 minutes around yesterday's crash time and got nothing, so I don't see any IPv6 traffic that might be the cause (then again, it could've been something that just arrived and never got the chance to be made persistent in my log). Unfortunately, I'm heading out of town for a conference today and won't be back till Monday. So, I'm crossing my fingers that the box will reboot by itself after each episode and will survive until I get back. :-) Regards, M.