From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 05:40:57 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 8C64A16A424 for ; Thu, 3 Nov 2005 05:40:57 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACC0E43D46 for ; Thu, 3 Nov 2005 05:40:56 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000027442.msg for ; Thu, 03 Nov 2005 11:40:47 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 88046, updated: 3.11.2005] To: freebsd-current@freebsd.org References: <20051027022313.R675@kushnir1.kiev.ua> <200511021035.22990.max@love2party.net> <20051103001509.C85422@kushnir1.kiev.ua> <200511030059.05946.max@love2party.net> <20051103020404.J85422@kushnir1.kiev.ua> From: Victor Snezhko Date: Thu, 03 Nov 2005 11:40:45 +0600 In-Reply-To: <20051103020404.J85422@kushnir1.kiev.ua> (Vladimir Kushnir's message of "Thu, 3 Nov 2005 02:08:51 +0200 (EET)") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Thu, 03 Nov 2005 11:40:47 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-VVS-Spam: false Cc: Max Laier 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 05:40:57 -0000 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? E.g, how can I know uptime from the kernel mode? -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru