From owner-freebsd-net@FreeBSD.ORG Tue Apr 29 00:45:12 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23B051065681 for ; Tue, 29 Apr 2008 00:45:12 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225]) by mx1.freebsd.org (Postfix) with ESMTP id DA2DD8FC0A for ; Tue, 29 Apr 2008 00:45:11 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3363220rvf.43 for ; Mon, 28 Apr 2008 17:45:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=4ze4jwFxOLTdY2ZP9SlQnCDkrLxnv4sHPrBzf3KcftI=; b=P/St5xWS/uIJxIj+7Jtdx0kvzZeAZnT5Hxe6xhRzwwtMRIjkaFimODqWM9VTgKdhQkePDid47zWACtrK15D7MDUSFeDJaXkHPva+PPaCVRLsqjH3XULupq8EtHUNccIHXABWml2Te92omdkZ55jXDrehBMlT00tq1rgHMj0fsys= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=DgRcp/JcvOpD58zlV2EXOZesdKgAK9REzTP/coYnIoAZ4jQKLgkXagCUtttKEdJx4YS53gr/bCx1qvzJmKP7BDO7WeGDQtfA9tLoA/juwfBsZF69SPLTY99tymkcbzZbBWNT0I1opPKrtoXC+NSvgzEE7wLBfJ6TwXFR2BfAibU= Received: by 10.140.88.11 with SMTP id l11mr565435rvb.74.1209429911357; Mon, 28 Apr 2008 17:45:11 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id k2sm7800167rvb.6.2008.04.28.17.45.08 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 28 Apr 2008 17:45:10 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m3T0j4Bg078358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Apr 2008 09:45:04 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m3T0j2WH078357; Tue, 29 Apr 2008 09:45:02 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 29 Apr 2008 09:45:02 +0900 From: Pyun YongHyeon To: Dewayne Geraghty Message-ID: <20080429004502.GB78140@cdnetworks.co.kr> References: <995276.92553.qm@web46006.mail.sp1.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <995276.92553.qm@web46006.mail.sp1.yahoo.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@FreeBSD.org Subject: Re: if_vge.c TX checksum errors on 6.3R-p2 7.0R-p1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2008 00:45:12 -0000 On Mon, Apr 28, 2008 at 02:19:17AM -0700, Dewayne Geraghty wrote: > Hi, I have four VIA motherboards each containing a vge0 device, three are misbehaving. > > On both the 7.0R-p1 and the 6.3Rp2 motherboards, the network cable needs to be unplugged and replugged into the motherboard, before ping will respond in either direction. The driver is issueing "incorrect" checksums during transmissions from the vge device, as observed from tcpdump -vvv. > > On 6.1R-p20 if_vge.c revision 1.14.2.7 is ok > On 6.3-p1 if_vge.c revision is 1.14.2.13 > On 7.0Rp1 if_vge.c revision is 1.31. > I don't see any changes that would break Tx checksum offload on 7.0R and 6.3R. By chance do you use VLAN? If you run tcpdump on Tx side(e.g. host with vge(4)) and see incorrect checksum it's completely normal(You should check the checksum on receiver). Hardware will insert computed checksum on the fly and tcpdump just see packets before the checksum insertion of hardware. > I'd like to know if other's have experiencing similar problems and which version of if_vge they had to go to as a quick workaround, unfortunately I can't revert to 6.1 as we really need 7.0R for the fantastic auditing and MAC enhancements. I'm happy to provide as much detail as needed to correct the problem - including ssh access to a crash burn machine (of course via an rl0 or vr0 NIC). > > The motherboard running 6.3R-p1 uses the VT6122 chip on a VT8237R Southbridge. (6.1R-p20 that works correctly uses this motherboard) > The motherboard running 7.0R-p1 is a VT6130 chipset on a VT8251 Southbridge. > > Regards, Dewayne. > -- Regards, Pyun YongHyeon