From owner-freebsd-stable@FreeBSD.ORG Tue May 27 15:45:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 040AE1065679 for ; Tue, 27 May 2008 15:45:21 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail3.secureworks.net (mail3.secureworks.net [65.114.32.155]) by mx1.freebsd.org (Postfix) with ESMTP id D1B638FC1B for ; Tue, 27 May 2008 15:45:20 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from localhost (localhost [127.0.0.1]) by mail3.secureworks.net (Postfix) with ESMTP id 1976F19E066; Tue, 27 May 2008 15:45:20 +0000 (GMT) X-Virus-Scanned: amavisd-new at secureworks.net Received: from mail3.secureworks.net ([127.0.0.1]) by localhost (mail3.secureworks.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rO8i9wMFgtrV; Tue, 27 May 2008 15:45:19 +0000 (GMT) Received: from [192.168.23.35] (mole1.secureworks.net [63.239.86.3]) by mail3.secureworks.net (Postfix) with ESMTP id CB4FF19E03B; Tue, 27 May 2008 15:45:19 +0000 (GMT) Message-ID: <483C2C8F.7070909@jellydonut.org> Date: Tue, 27 May 2008 11:45:19 -0400 From: Michael Proto User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.14) Gecko/20080502 Thunderbird/2.0.0.14 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Gerrit_K=FChn?= References: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de> In-Reply-To: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: "freebsd-stable@freebsd.org" Subject: Re: broken re(4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2008 15:45:21 -0000 Gerrit Kühn wrote: > Hi folks, > > I have four identical ITX boards from Jetway here, each having two re(4) > onboard nics: > > re0@pci0:0:9:0: class=0x020000 card=0x10ec16f3 chip=0x816710ec rev=0x10 > hdr=0x00 vendor = 'Realtek Semiconductor' > device = 'RTL8169/8110 Family Gigabit Ethernet NIC' > class = network > subclass = ethernet > re1@pci0:0:11:0: class=0x020000 card=0x10ec16f3 chip=0x816710ec > rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' > device = 'RTL8169/8110 Family Gigabit Ethernet NIC' > class = network > subclass = ethernet > atapci0@pci0:0:15:0: class=0x01018f card=0x31491106 chip=0x31491106 > rev=0x80 > > > I run FreeBSD 7-stable from early March 08 on three of these > machines and noticed no problems with networking with that so far. > Some days ago I installed a fourth machine with 7-stable from early May > (and some days later -because of the problems described below- to May > 17th). With this new machine I see several networking problems. The most > prominent are these two: > > - heavy networking traffic (in this case backup via tar & NFS) causes hangs > for about 10s-30s and sometimes also leads to watchdog timeouts: > May 27 09:04:07 protoserve kernel: re0: watchdog timeout > May 27 09:04:07 protoserve kernel: re0: link state changed to DOWN > May 27 09:04:10 protoserve kernel: re0: link state changed to UP > > - copying large files (more than some 100MB) via ssh/scp drops the > connection due to "corrupted MAC on input": > Disconnecting: Corrupted MAC on input. > lost connection > > In the latter case the networking traffic should actually not be that > high, because these are nanobsd systems which are transferring a new image > file (system update, 2GB) via ssh (so the bottleneck should be the write > speed of the CF card used to hold the system). > > > I do not see these problems with the old codebase from March 08 on my old > machines. The cvs shows a large MFC for the re-driver in April, so I > guessed something came in there which broke things here. Therefore I > downgraded the new system to a cvs codebase from March 1st, but the > problems persist. They also exist on both interfaces. memtest86 is running > for hours now without finding something wrong. > > Any hints what I should do next to find the culprit? > I'm running 6.3 on the exact same Jetway board at home, and while I haven't been bitten by the DOWN/UP issue I have seen the occasional "corrupted MAC on input" error when doing an ssh/scp. Seems to have simmered-down since moving from 6.3-RELEASE to 6.3-STABLE (last supped/rebuilt on 5/6/08). Note this is using only one of the 2 on-board NICs. I disabled the 2nd one in the BIOS as I don't need it at the moment. -Proto