From owner-freebsd-current@FreeBSD.ORG Sun Sep 12 06:44:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 3DBFD16A4CF; Sun, 12 Sep 2004 06:44:16 +0000 (GMT) Date: Sun, 12 Sep 2004 06:44:16 +0000 From: Kris Kennaway To: Andre Guibert de Bruet Message-ID: <20040912064416.GA89882@hub.freebsd.org> References: <20040911183823.W84468@alpha.siliconlandmark.com> <20040912022558.B84468@alpha.siliconlandmark.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040912022558.B84468@alpha.siliconlandmark.com> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: 6-CURRENT Network stack issues w/SMP? (Was: Re: TreeList failed: Network write failure: ChannelMux.ProtocolError) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sun, 12 Sep 2004 06:44:16 -0000 On Sun, Sep 12, 2004 at 02:42:03AM -0400, Andre Guibert de Bruet wrote: > >I've also noticed data corruption in the form of failed CRCs (And hence > >dropped SSH connections) while transferring large amounts of data via SSH > >over gige to a machine on its subnet. These problems started occuring > >after the giant-less networking megacommit. Older kernels check out > >without any such issues. Does it go away if you turn off debug.mpsafenet? If not, it's probably not related to that commit. Kris