From owner-freebsd-current@FreeBSD.ORG Fri Feb 22 13:56:59 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8251416A402 for ; Fri, 22 Feb 2008 13:56:59 +0000 (UTC) (envelope-from raul@pop.isdefe.es) Received: from mail1.isdefe.es (mail1.isdefe.es [194.15.213.239]) by mx1.freebsd.org (Postfix) with ESMTP id 490A113C4CC for ; Fri, 22 Feb 2008 13:56:59 +0000 (UTC) (envelope-from raul@pop.isdefe.es) Received: from [10.100.147.125] (opera.isdefe.es [194.15.213.193]) by mail1.isdefe.es (Postfix) with ESMTP id 333405C35; Fri, 22 Feb 2008 14:56:57 +0100 (CET) Message-ID: <47BED4A9.1020901@pop.isdefe.es> Date: Fri, 22 Feb 2008 14:56:57 +0100 From: Raul User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Christoph Schug References: <20080221035014.GB26427@cdnetworks.co.kr> <20080221050635.GC26427@cdnetworks.co.kr> <20080221143748.GE10726@lega.schug.net> <47BE9910.7030501@pop.isdefe.es> <20080222103642.GB45806@lega.schug.net> In-Reply-To: <20080222103642.GB45806@lega.schug.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: Pyun YongHyeon , FreeBSD Current , Robert Backhaus Subject: Re: Packet corruption in re0 (and em0 too) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 22 Feb 2008 13:56:59 -0000 Christoph Schug escribió: >> The fastest method I found to reproduce the problem is receive a >> compresed tar (with good compression ratio) over the network (using nc, >> 100 Mbps fdx), pipe through tar that decompress and write it on disk (a >> lot of MB/s and tps looking at 'systat -vm'). The source tar file is >> about 5Gb and link always fails before EOF :|. [....] > Up to now, no problems, but I certainly need more uptime to be sure. > Maybe I can tell more later that day. My box used to also need a couple or three days to exhibit the problem until I realize that my previous example made it happen in minutes: RELENG_7_0 i386 - em0 - dot1q - switch - clear - re0 - RELENG_7_0 amd64 on the i386: cat files_with_lots_of_zeros.tgz | nc -l 3000 on the amd64: nc i386_box_address 3000 | tar xzvf - My files_with_lots_of_zeros.tgz is about 5Gb, and the i386 box flood the re0 link (1000baseTX vs 100baseTX). I've never seen the end of the file on the re0 side. No problem on the i386 side, just to illustrate my setup. I see the same behavior on the amd64 box using an em0 card (pci one). No clue if my problem differs from yours but in my case it doesn't look like only a re0 problem :/. Regards, Raul