From owner-freebsd-stable@FreeBSD.ORG Tue Dec 7 08:55:44 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 DEA7A16A4CE for ; Tue, 7 Dec 2004 08:55:44 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40BAD43D66 for ; Tue, 7 Dec 2004 08:55:44 +0000 (GMT) (envelope-from avleeuwen@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so66333rns for ; Tue, 07 Dec 2004 00:55:25 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=FG2Kj6dOuZT0XjdraKduNeYURNRLTzbcs0PW9EF/8qr76hANX/NcLjZRnE3tkh/1na95kRu3ccelc/n5QSX1v9N3F9EZG/8F/alOu35rey0egBxdqIIIutO1hYVNLn8AZ7mZnbGOix23bDGPf5ixV6okGBWbklCnLvCHULktjJ4= Received: by 10.38.8.40 with SMTP id 40mr1791702rnh; Tue, 07 Dec 2004 00:55:14 -0800 (PST) Received: by 10.38.206.16 with HTTP; Tue, 7 Dec 2004 00:55:13 -0800 (PST) Message-ID: Date: Tue, 7 Dec 2004 09:55:13 +0100 From: Arjan Van Leeuwen To: Paul Saab In-Reply-To: <41B4EFB2.3020704@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41B4CCFA.6070202@fastclick.com> <41B4EFB2.3020704@freebsd.org> cc: Jeff Behl cc: freebsd-stable@freebsd.org Subject: Re: reproducible kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Arjan Van Leeuwen 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 08:55:45 -0000 On Mon, 06 Dec 2004 15:48:02 -0800, 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. > Please read the original thread: http://lists.freebsd.org/mailman/htdig/freebsd-stable/2004-November/009307.html I couldn't get a crashdump on this machine, but I provided a lot of information (traces) in that thread. Since no one replied to my last post in that thread, I didn't know what else to do. But if you tell me what else you want, I'll get it for you immediately.