Date: Sun, 02 Oct 2005 16:52:38 +0100 From: gnn@FreeBSD.org To: Andre Oppermann <andre@FreeBSD.org> Cc: SUZUKI Shinsuke <suz@kame.net>, net@FreeBSD.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: ipv6 panic in 6.0 ([kris@FreeBSD.org: kern/85780: 'panic:bogus refcnt 0' in routing/ipv6]) Message-ID: <m21x33vruh.wl%gnn@neville-neil.com> In-Reply-To: <433ABC12.948DA54D@freebsd.org> References: <20050927222634.GA46375@xor.obsecurity.org> <x7psqtzyad.wl%suz@alaxala.net> <20050928151319.GA27347@xor.obsecurity.org> <433ABC12.948DA54D@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I am working, very slowly, through this bug, but in the hopes that others might know something and chime in the packet that caused this is an ICMPv6 packet for neighbor solicitation (type 135, code 0), directed at the machine which paniced, i.e. not broadcast or multicast and is attempting to look up a network route, or at least that's what it looks like. I say that it is looking up a network route because the target address portion of the packet includes only the first 8 bytes, which in this case are the 64 bits of prefix for the IPv6 network which the interface is on. I'll keep digging but figured I'd throw this out there to anyone who might have more clue. Later, George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m21x33vruh.wl%gnn>