From owner-freebsd-net@FreeBSD.ORG Thu May 12 14:25:25 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 189F616A4CE; Thu, 12 May 2005 14:25:25 +0000 (GMT) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id A651143D72; Thu, 12 May 2005 14:25:24 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from ocean.jinmei.org (unknown [2001:200:0:4819:200:39ff:fed7:e2e4]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 15A0B1521A; Thu, 12 May 2005 23:27:16 +0900 (JST) Date: Thu, 12 May 2005 23:26:16 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: "Mark Klein" In-Reply-To: References: User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII cc: gnn@freebsd.org cc: freebsd-net@freebsd.org cc: kame 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 14:25:25 -0000 >>>>> On Thu, 12 May 2005 06:57:32 -0700, >>>>> "Mark Klein" said: >> 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. Hmm, this really sounds strange, since the sequence of nd6_timer()->in6_purgeaddr(), which was an entry point of the crash, could take place only when an IPv6 address with a finite lifetime expires. This could not happen if IPv6 is "NOT explicitly used". (link-local addresses are automatically assigned unless the INET6 option is removed from the kernel configuration options, but these addresses have an infinite lifetime and cannot be the cause of this trouble). It would be helpful if you can provide the result of "ifconfig -a" under the configuration that can cause the crash. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp