Date: Sun, 13 Nov 2005 13:50:45 -0500 From: Jason <jason@monsterjam.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: stable@FreeBSD.org Subject: Re: can someone please let me know what this crash means? Message-ID: <20051113185045.GA63704@monsterjam.org> In-Reply-To: <20051113174635.L90423@fledge.watson.org> References: <20051113134951.GA3965@monsterjam.org> <20051113144034.S88008@fledge.watson.org> <20051113161744.GB3965@monsterjam.org> <20051113174635.L90423@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Do you use IPv6 on this box, and in particular, TCP over IPv6? Do you use > tcpdrop(8) to kill TCP connections? no ipv6 at all.. and no, I havent used tcpdrop that I know of.. > > There appears to be one bug fix since the revision you're using relating > to tcpdrop(8) on TCP connections in the TIMEWAIT state that might result > in a panic like the one you're seeing. The panic and trace look familiar, > but without the panic message it's hard to confirm. If the machine has > not already been reset, you might try showing the message buffer in DDB, > which would have the effect of printing out the ring buffer that likely > contains the panic message. sorry, I had to reboot already.. ;) > > There have also been a number of fixes relating to raw sockets which may > also apply to ipdivert related configurations, but I'm not sure they could > lead to this particular panic easily. This strikes me a a pcb/tcp race of > some sort. I am running ipfw on this box and do have $fwcmd add divert natd all from any to any via fxp0 hmm, I guess its time to upgrade to 6.0? Jason
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051113185045.GA63704>