From owner-freebsd-stable@FreeBSD.ORG Tue Dec 7 03:25:49 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4F3B16A4CE; Tue, 7 Dec 2004 03:25:49 +0000 (GMT) Received: from sb.santaba.com (sb.santaba.com [207.154.84.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id B943743D68; Tue, 7 Dec 2004 03:25:49 +0000 (GMT) (envelope-from jbehl@fastclick.com) Received: from [192.168.3.100] (unknown [205.180.85.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sb.santaba.com (Postfix) with ESMTP id 9353528433; Mon, 6 Dec 2004 19:25:49 -0800 (PST) Message-ID: <41B52324.9050001@fastclick.com> Date: Mon, 06 Dec 2004 19:27:32 -0800 From: Jeff Behl User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Paul Saab References: <41B4CCFA.6070202@fastclick.com> <41B4EFB2.3020704@freebsd.org> In-Reply-To: <41B4EFB2.3020704@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org cc: Arjan Van Leeuwen Subject: Re: reproducible kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 03:25:50 -0000 You're helpful reply doesn't seem to include any information on where to upload a crash dump, if that's what is being asked. I haven't dealt with them before. Perhaps you'd be so kind as to direct? A reply that helps work around a problem is always welcome, especially when it keeps a remotely located host from continuously rebooting. Paul Saab wrote: > Arjan Van Leeuwen wrote: > >> I had a panic that looked a lot like this (panic in swi, came up when >> >> I had some network traffic), and it's also been reported by other >> people than me. Turning of SACK seems to work for most people (at >> least it worked for me). Put net.inet.tcp.sack.enable=0 in >> /etc/sysctl.conf. >> >> > And how exactly is this supposed to help anyone fix the problem. If > you provide crashdumps then solving the problem becomes much easier, > but nothing will get fixed if you just turn it off.