From owner-freebsd-current@FreeBSD.ORG Sun Sep 12 06:42:09 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 212DC16A4CE for ; Sun, 12 Sep 2004 06:42:09 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D5E143D58 for ; Sun, 12 Sep 2004 06:42:08 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) i8C6g3rY049961 for ; Sun, 12 Sep 2004 02:42:03 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i8C6g3iC049958 for ; Sun, 12 Sep 2004 02:42:03 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 12 Sep 2004 02:42:03 -0400 (EDT) From: Andre Guibert de Bruet To: current@freebsd.org In-Reply-To: <20040911183823.W84468@alpha.siliconlandmark.com> Message-ID: <20040912022558.B84468@alpha.siliconlandmark.com> References: <20040911183823.W84468@alpha.siliconlandmark.com> 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 Subject: 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:42:09 -0000 Replying to myself... I made the cardinal sin of not including a uname -a... The system in question is: FreeBSD bling.home 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Sat Sep 11 18:31:59 EDT 2004 root@bling.home:/usr/CURRENT/sys/i386/compile/BLING i386 I have a fresh dmesg up at http://bling.properkernel.com/dmesg.boot.txt and a boot -v at http://bling.properkernel.com/boot-v.txt Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ > On Sat, 11 Sep 2004, Andre Guibert de Bruet wrote: > Anyone have any ideas on this one? > > # cvsupdate [...] > Updating collection src-all/cvs > TreeList failed: Network write failure: ChannelMux.ProtocolError > Will retry at 18:43:42 > ^C > > The machine in question is a dual Athlon with a custom SMP kernel config > which can be found at http://bling.properkernel.com/BLING . Reverting to > GENERIC does _not_ fix the problem. The interface in question is an > nge-compatible 64-bit Linksys card detected as: > > nge0@pci0:8:0: class=0x020000 card=0x10641737 chip=0x0022100b rev=0x00 > hdr=0x00 > vendor = 'National Semiconductor' > device = 'DP83820/1 10/100/1000 Gigabit Ethernet Adapter' > class = network > subclass = ethernet > > 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. > > Additional information on the system can be found online: > pciconf -vl: http://bling.properkernel.com/pciconf-vl.txt > kernel config: http://bling.properkernel.com/BLING > old dmesg (Can be updated): http://bling.properkernel.com/dmesg.boot.txt