From owner-freebsd-current@FreeBSD.ORG Thu Feb 21 07:43:20 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 3453216A402 for ; Thu, 21 Feb 2008 07:43:20 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.189]) by mx1.freebsd.org (Postfix) with ESMTP id 0B89913C461 for ; Thu, 21 Feb 2008 07:43:19 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by rv-out-0910.google.com with SMTP id g13so2281076rvb.43 for ; Wed, 20 Feb 2008 23:43:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=zR+F7scFSXbNRvjs262RwhYyFXuvHgFj19mI3Xk40cQ=; b=IBeFuFSl1dXmB2GBso8INdxR5B5Ut45RrI1SI4hA8tHFgz4RZMlOA/Hw/iGtr7/vFrqrE98KnURV76yT/UengHUud0V04DkxylvoaYs06qKKmk7DyC5s8fJ4Qdspjv1gRujNcoEZwV9a5qCTNNkFJ9GUjy6ECUfrMEUX+qQQ+Yw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=VuHylDL9QSKeIA/IhcUX9ptAEc7uykZZQCJvt+JFtib11P0dC8zVgAEBzwhUqtxNULgxrZzif7N35eOG/ZRQfT/WLsZZ0jUxlXCabDKEl2L/kiWAllfRlDO+lJ+IKcm6VJKrGR81/sYNRC3KBqzJDwcd+HmHwH1dPXkSIL8NUMo= Received: by 10.140.163.3 with SMTP id l3mr6436510rve.253.1203579799061; Wed, 20 Feb 2008 23:43:19 -0800 (PST) Received: by 10.141.170.18 with HTTP; Wed, 20 Feb 2008 23:43:18 -0800 (PST) Message-ID: <2e77fc10802202343j2ac419bay89a2442a4832b2d@mail.gmail.com> Date: Thu, 21 Feb 2008 07:43:18 +0000 From: "Niki Denev" Sender: ndenev@gmail.com To: "Eric L. Chen" In-Reply-To: <1203570954.1696.2.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1203570954.1696.2.camel@localhost> X-Google-Sender-Auth: b7c147a00f0455bb Cc: FreeBSD Current , Robert Backhaus Subject: Re: Packet corruption in re0 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: Thu, 21 Feb 2008 07:43:20 -0000 On Thu, Feb 21, 2008 at 5:15 AM, Eric L. Chen wrote: > > > On Thu, 2008-02-21 at 11:03 +1000, Robert Backhaus wrote: > > I am experiencing roughly 15% packet corruption on the re interface on > > my freebsd 7/amd64 box. > > > > FreeBSD gw.flexi.robbak.com 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #8: > > Tue Feb 5 09:49:55 EST 2008 > > root@gw.flexi.robbak.com:/usr/obj/usr/src/sys/GW amd64 > > > > The attached 3 files demonstrate the problem: "ping" shows the output > > of ping -c 100, and shows 15% packet loss. "tcpdump" shows the packets > > leaving, and some of the lost packets being returned with addresses, > > ports and data corrupted. The data in these packets seems to be coming > > from other packets passing through other interfaces at the time. > > "remote-tcpdump" shows the packets being received and returned from > > the other machine. Note that some packets are being corrupted on the > > way out, too. > > > > Just to make troubleshooting difficult, this problem only shows up > > after the system has been up for roughly 36 hours, depending on the > > amount of traffic. > > > > I am using the latest bios that I am aware of. The bios that I > > recently applied did include a firmware update for the realtek > > interface, but this did not affect the problem. > > _______________________________________________ > > I disabled some hw features and works fine. > like this (/etc/rc.conf) > ifconfig_re0="inet 192.168.1.10 netmask 255.255.255.0 -rxcsum -txcsum > -tso -lr > o" > > /Eric > I experienced the same problems shortly after upgrading to 7.0-PRE After about a day and something of uptime my ssh shells began to drop with messages about corrupted/mismatched checksums. I "fixed" the problem by putting an em(4) interface in the machine, because I need it to be online and accessible remotely at all times. --Niki