Date: Thu, 3 Nov 2005 02:08:51 +0200 (EET) From: Vladimir Kushnir <vkushnir@i.kiev.ua> To: Max Laier <max@love2party.net> Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic Message-ID: <20051103020404.J85422@kushnir1.kiev.ua> In-Reply-To: <200511030059.05946.max@love2party.net> References: <20051027022313.R675@kushnir1.kiev.ua> <200511021035.22990.max@love2party.net> <20051103001509.C85422@kushnir1.kiev.ua> <200511030059.05946.max@love2party.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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. TIA, Vladimir
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051103020404.J85422>