From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 14:50:01 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 59F8616A41F for ; Thu, 3 Nov 2005 14:50:01 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B02743D48 for ; Thu, 3 Nov 2005 14:50:00 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1303365 for multiple; Thu, 03 Nov 2005 09:48:00 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA3EnpCO065662; Thu, 3 Nov 2005 09:49:54 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 3 Nov 2005 09:49:00 -0500 User-Agent: KMail/1.8.2 References: <20051027022313.R675@kushnir1.kiev.ua> <20051103020404.J85422@kushnir1.kiev.ua> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511030949.01726.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=100 Cc: Max Laier , Victor Snezhko Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 03 Nov 2005 14:50:01 -0000 On Thursday 03 November 2005 12:40 am, Victor Snezhko wrote: > Vladimir Kushnir writes: > > On Thu, 3 Nov 2005, Max Laier wrote: > >>> Here it is: right before panic it prints > >>> > >>> For 0xffffff0017531100 -1 ticks > >>> For 0xffffff0017531100 -1 ticks > >> > >> This results in two consecutive callout_stop() calls, but shouldn't hurt > >> as callout_stop is protected against that. > >> > >> Do you get a dump for this? Can you compare this pointer to the global > >> llinfo_nd6 and see if "c" from the softclock() frame is related (or > >> maybe the previous item in the list TAILQ). > > > > Sorry I'm not very goot at debugging. Would you please give me some > > instructions (lamer's level, preferably :-)). And anyway I'll be able > > to do it tomorrow only. > > In the meantime, I want to debug this too. I would insert a panic() > call somewhere in the beginning of nd6_llinfo_settimer(), but there is > a problem. nd6_llinfo_settimer() is called not only when I start ppp, > but at bootup too (at bootup - once, I think that this is due to > initializing lo0 interface, which has a default ipv6 address). Could I > somehow make the kernel not panic at boot time and panic later, when I > call ppp? You can either add a sysctl that starts off as 0 and only panic if the sysctl is 1. You can then boot, change the sysctl to 1, and then run ppp. Alternatively, you could use kdb_enter() to enter the debugger instead of panic(). You could then just continue using 'c' when you drop into ddb during boot. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org