From owner-freebsd-stable@FreeBSD.ORG Tue May 27 15:23:47 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 CB514106564A for ; Tue, 27 May 2008 15:23:47 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 597788FC15 for ; Tue, 27 May 2008 15:23:47 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id m4REqWqs013408 for ; Tue, 27 May 2008 16:52:34 +0200 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id C7E951E5 for ; Tue, 27 May 2008 16:52:32 +0200 (CEST) Date: Tue, 27 May 2008 16:52:32 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: freebsd-stable@freebsd.org Message-Id: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2008.5.27.73739 Subject: 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:23:47 -0000 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? cu Gerrit