From owner-freebsd-current@FreeBSD.ORG Sun Sep 12 06:53:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9A8816A4CE; Sun, 12 Sep 2004 06:53:06 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 622C743D45; Sun, 12 Sep 2004 06:53:06 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) i8C6r5Gk050034; Sun, 12 Sep 2004 02:53:05 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i8C6r5lj050031; Sun, 12 Sep 2004 02:53:05 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 12 Sep 2004 02:53:05 -0400 (EDT) From: Andre Guibert de Bruet To: Kris Kennaway In-Reply-To: <20040912064416.GA89882@hub.freebsd.org> Message-ID: <20040912025037.Y84468@alpha.siliconlandmark.com> References: <20040911183823.W84468@alpha.siliconlandmark.com> <20040912064416.GA89882@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: current@FreeBSD.ORG Subject: Re: 6-CURRENT Network stack issues w/SMP? (Was: Re: TreeListfailed: 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:53:06 -0000 On Sun, 12 Sep 2004, Kris Kennaway wrote: > 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. Setting debug.mpsafenet to 0 allows the SSH transfers to complete. The MD5 checksums and sizes match. Where do we go from here? Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ >