From owner-freebsd-current@FreeBSD.ORG Wed Jul 1 23:07:57 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A85F1065670; Wed, 1 Jul 2009 23:07:57 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id DE2418FC14; Wed, 1 Jul 2009 23:07:56 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lstewart-laptop.caia.swin.edu.au (host86-150-124-14.range86-150.btcentralplus.com [86.150.124.14]) (authenticated bits=0) by lauren.room52.net (8.14.3/8.14.3) with ESMTP id n61N7kg2027881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Jul 2009 09:07:49 +1000 (EST) (envelope-from lstewart@freebsd.org) Message-ID: <4A4BEC3A.2060108@freebsd.org> Date: Thu, 02 Jul 2009 00:07:38 +0100 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.22 (X11/20090626) MIME-Version: 1.0 To: Kamigishi Rei References: <4A45ABB1.7040506@haruhiism.net> <4A48CE02.5000200@freebsd.org> <4A48D4A2.8010207@haruhiism.net> <4A48DA31.5010900@freebsd.org> <4A4BE438.5060203@haruhiism.net> In-Reply-To: <4A4BE438.5060203@haruhiism.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RDNS_DYNAMIC,SPF_SOFTFAIL autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lauren.room52.net Cc: freebsd-current@freebsd.org, Robert Watson Subject: Re: r194546 amd64: kernel panic in tcp_sack.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2009 23:07:57 -0000 Kamigishi Rei wrote: > Lawrence Stewart wrote: >> Ok. I'm working on a patch to address a different TCP/SACK issue, but >> it may in fact be partially relevant to the cause of your panic... >> can't promise when I'll be able to take a close look at this but I'm >> aware of it now so that's a start. If you run into it again or find >> the trigger for the panic, please let me know. > Reproduced. I don't know what was the trigger this time. The system runs > lighttpd, fastcgi python and php, mysql and postgresql. 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? > Also, in this core somehow everything looks quite similar (looks like > another page fault but with panic() called prior to getting into fatal > trap 12) to my two earlier dumps: > http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008777.html > http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008781.html > so maybe it's not really a problem with tcp_sack.c or netisr.c. > No, the two earlier panics look like the same issue as one another, but they are unrelated to this SACK panic. I've CC'd Robert who might have thoughts on the netisr related panics. > Should I attach the core.txt as well? Yes, send it to me directly and I'll take a look. Cheers, Lawrence