Date: Wed, 02 Nov 2005 23:08:45 +0600 From: Victor Snezhko <snezhko@indorsoft.ru> To: Max Laier <max@love2party.net> Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic Message-ID: <uek5zc6zm.fsf@indorsoft.ru> In-Reply-To: <200511021035.22990.max@love2party.net> (Max Laier's message of "Wed, 2 Nov 2005 10:35:05 %2B0100") References: <20051027022313.R675@kushnir1.kiev.ua> <200510311231.33322.jhb@freebsd.org> <20051102014239.O654@kushnir1.kiev.ua> <200511021035.22990.max@love2party.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Max Laier <max@love2party.net> writes: >> > suz 2005-10-21 16:23:01 UTC >> > >> > FreeBSD src repository >> > >> > Modified files: >> > sys/netinet icmp6.h >> > sys/netinet6 icmp6.c in6.c in6.h in6_ifattach.c >> > in6_ifattach.h in6_var.h ip6_output.c >> > mld6.c mld6_var.h nd6.c nd6.h nd6_nbr.c >> > nd6_rtr.c >> > share/doc/IPv6 IMPLEMENTATION >> >> This was when panics begun. And they're still here. > > That brings me back to ln_timer_ch as the culprit. Could you please build > with this patch and get me the console output shortly before the panic? I built with this patch and have two identical kernel output strings before the panic (and one more during bootup): For 0xc188ee80 1 ticks For 0xc188ee80 1 ticks Sorry, can't analyze a crashdump yet to show what 0xc188ee80 is. When I synchronize my world with the new kernel I probably will be able to. -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?uek5zc6zm.fsf>