From owner-freebsd-current@FreeBSD.ORG Tue Mar 27 04:52:54 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D002F16A400 for ; Tue, 27 Mar 2007 04:52:54 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (nagual.pp.ru [194.87.13.69]) by mx1.freebsd.org (Postfix) with ESMTP id 5519A13C458 for ; Tue, 27 Mar 2007 04:52:54 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.8/8.13.8) with ESMTP id l2R4qqYr011305; Tue, 27 Mar 2007 08:52:52 +0400 (MSD) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.8/8.13.8/Submit) id l2R4qqoB011304; Tue, 27 Mar 2007 08:52:52 +0400 (MSD) (envelope-from ache) Date: Tue, 27 Mar 2007 08:52:52 +0400 From: Andrey Chernov To: Andre Oppermann Message-ID: <20070327045252.GA3256@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Andre Oppermann , Giorgos Keramidas , freebsd-current@freebsd.org, Nicolas Blais References: <20070324124732.GA767@nagual.pp.ru> <200703251348.58972.nb_root@videotron.ca> <20070325194946.GC79938@kobe.laptop> <200703251620.20879.nb_root@videotron.ca> <20070325202749.GA1503@kobe.laptop> <460705AE.5040107@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <460705AE.5040107@freebsd.org> User-Agent: Mutt/1.5.14 (2007-02-12) Cc: freebsd-current@freebsd.org, Giorgos Keramidas , Nicolas Blais Subject: Re: Latest -current complete lockup (tcp changes?) 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: Tue, 27 Mar 2007 04:52:54 -0000 On Mon, Mar 26, 2007 at 01:28:46AM +0200, Andre Oppermann wrote: > Giorgos Keramidas wrote: > >Hi Andre, > > > >The attached thread below is a reply from Nicolas Blais which shows some > >problems with the recent SACK changes. Any idea how we can proceed from > >this point? > > Please update to rev. 1.36 of sys/netinet/tcp_sack.c. The KASSERT() was > too tight but actually caught a bug that would have caused a crash anyway. The problem is deeper than that ((( I still got the same lockup, just with more net activity. I even try to completely disable sack, with the same result, so probem is somewhere else. Last working kernel still from Mar 22. -- http://ache.pp.ru/