From owner-freebsd-current@FreeBSD.ORG Wed Sep 8 04:44:30 2010 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 4F5F910656C1; Wed, 8 Sep 2010 04:44:30 +0000 (UTC) (envelope-from bw@exodus.desync.com) Received: from exodus.desync.com (exodus.desync.com [IPv6:2607:f178::164]) by mx1.freebsd.org (Postfix) with ESMTP id 035518FC14; Wed, 8 Sep 2010 04:44:29 +0000 (UTC) Received: from exodus.desync.com (localhost [127.0.0.1]) by exodus.desync.com (8.14.4/8.14.4) with ESMTP id o884huW0012877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Sep 2010 00:44:13 -0400 (EDT) (envelope-from bw@exodus.desync.com) Received: (from bw@localhost) by exodus.desync.com (8.14.4/8.14.4/Submit) id o884hsrh012876; Wed, 8 Sep 2010 00:43:54 -0400 (EDT) (envelope-from bw) Date: Wed, 8 Sep 2010 00:43:53 -0400 From: ben wilber To: Andre Oppermann Message-ID: <20100908044353.GA12865@exodus.desync.com> References: <20100831231314.GA9637@exodus.desync.com> <4C7E4DC0.5040608@freebsd.org> <137CFFE2-6783-449E-A2EC-8415F9287D97@desync.com> <4C80AD79.8070307@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C80AD79.8070307@freebsd.org> X-Angst-Level: High Cc: FreeBSD Current Subject: Re: TSO panic 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, 08 Sep 2010 04:44:30 -0000 On Fri, Sep 03, 2010 at 10:10:33AM +0200, Andre Oppermann wrote: > On 02.09.2010 00:11, ben wilber wrote: > > On Sep 1, 2010, at 8:57 AM, Andre Oppermann wrote: > > > >> On 01.09.2010 01:13, ben wilber wrote: > >>> Hi, > >>> > >>> I just upgraded from r210042 to r212073 and keep getting the panic > >>> introduced in r211317: > >>> > >>> panic: tcp_output: len<= tso_segsz > >> > >> Please try the attached patch and report back whether it > >> fixes the issue. > > > > The system ran for 8 hours or so before I received the same panic. Previously, it would panic within 20 minutes. > > Attached is an updated patch that should fix the panic. > Please try. Running for almost three days now with no problem. Looks good!