From owner-freebsd-stable@FreeBSD.ORG Mon Dec 6 22:57:20 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 C184816A4CE for ; Mon, 6 Dec 2004 22:57:20 +0000 (GMT) Received: from sb.santaba.com (sb.santaba.com [207.154.84.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A02E43D49 for ; Mon, 6 Dec 2004 22:57:20 +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 58C3C28433; Mon, 6 Dec 2004 14:57:20 -0800 (PST) Message-ID: <41B4E436.3090100@fastclick.com> Date: Mon, 06 Dec 2004 14:59:02 -0800 From: Jeff Behl User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <41B4CCFA.6070202@fastclick.com> <20041206215819.GA56582@xor.obsecurity.org> In-Reply-To: <20041206215819.GA56582@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org 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: Mon, 06 Dec 2004 22:57:20 -0000 Kris Kennaway wrote: >On Mon, Dec 06, 2004 at 01:19:54PM -0800, Jeff Behl wrote: > > >>I'm getting a kernel panic every time I start getting traffic (~ 20Mb/s >>total) to two squid processes. This was not happening with -RELEASE. I >>upgraded on the advice that STABLE would decrease the %cpu spent in >>system, which was much higher than that spent in user. The machine's >>only fucntion is as a reverse proxy (2 separate squid processes to take >>advante of both cpus). >> >>Let me know if a dump would be helpful, or if there's anything I can do >>to help. >> >> > >You really need to get a debugging traceback - see the chapter on >kernel debugging in the developers' handbook. > >Kris > > will do. in the mean time, i've disable SACK (someone mentioned trying this on another thread for a different problem...can't remember where) and the machine is no longer crashing.