From owner-freebsd-current@FreeBSD.ORG Fri Feb 22 22:18:08 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 83A3D16A407 for ; Fri, 22 Feb 2008 22:18:08 +0000 (UTC) (envelope-from raul@pop.isdefe.es) Received: from mail3.isdefe.es (mail3.isdefe.es [62.93.171.234]) by mx1.freebsd.org (Postfix) with ESMTP id 4CA6513C4D1 for ; Fri, 22 Feb 2008 22:18:08 +0000 (UTC) (envelope-from raul@pop.isdefe.es) Received: from [IPv6:::1] (unknown [194.15.213.238]) by mail3.isdefe.es (Postfix) with ESMTP id B1580564BE; Fri, 22 Feb 2008 23:18:06 +0100 (CET) Message-ID: <47BF4A20.6070304@pop.isdefe.es> Date: Fri, 22 Feb 2008 23:18:08 +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> In-Reply-To: <47BE9910.7030501@pop.isdefe.es> 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 22:18:08 -0000 Quoting myself after some more testing ... Raul escribió: [....] > the same behavior happens. I left the box by night compiling CURRENT and > this morning I've run my 'stress tests' (once again with re0) ... the > box break to gdb as far I remember (too sleepy, sorry). Well, at least > no garbage over the link BD. Really sleepy, it was not gdb, just a LOR. If is anybody interested on it, I'll can reproduce it after a bit more tests with RELENG_7_0. > 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 :|. That's still true at least for RELENG_7_0 and re0. Nothing new I guess. I can't reproduce it with em0. Sorry for the noise. I'm going to try the proposed if_re.c and if_rlreg.h as Christoph is doing ... Regards, Raul