Date: Thu, 02 Jul 2009 00:31:53 +0100 From: Lawrence Stewart <lstewart@freebsd.org> To: Kamigishi Rei <spambox@haruhiism.net> Cc: freebsd-current@freebsd.org Subject: Re: r194546 amd64: kernel panic in tcp_sack.c Message-ID: <4A4BF1E9.8030609@freebsd.org> In-Reply-To: <4A4BF0CE.2070203@haruhiism.net> References: <4A45ABB1.7040506@haruhiism.net> <4A48CE02.5000200@freebsd.org> <4A48D4A2.8010207@haruhiism.net> <4A48DA31.5010900@freebsd.org> <4A4BE438.5060203@haruhiism.net> <4A4BEC3A.2060108@freebsd.org> <4A4BF0CE.2070203@haruhiism.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Kamigishi Rei wrote: > Lawrence Stewart wrote: >> hmmm, handy. What is generating the TCP load on this machine? Serving >> to clients on the Internet? Or machines on a local lan? Is there lots >> of load? Little bit? > I've forgot to mention that in both cases with this tcp_sack conditional > panic the uptime was approximately 40 hours. You didn't mention whether the clients being served were local lan or remote. I ask because tcp_timer_rexmt() is in the backtrace indicating you're getting TCP RTOs firing on the connection that's triggering the panic. Cheers, Lawrence
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A4BF1E9.8030609>