From owner-freebsd-net  Mon Oct 14 13:59:12 2002
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CA46D37B401
	for <net@freebsd.org>; Mon, 14 Oct 2002 13:59:11 -0700 (PDT)
Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EB1C843EA3
	for <net@freebsd.org>; Mon, 14 Oct 2002 13:59:10 -0700 (PDT)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g9EKx3x08301;
	Mon, 14 Oct 2002 13:59:04 -0700 (PDT)
	(envelope-from jdp@vashon.polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.12.5/8.12.5/Submit) id g9EKx0sY022550;
	Mon, 14 Oct 2002 13:59:00 -0700 (PDT)
	(envelope-from jdp)
Date: Mon, 14 Oct 2002 13:59:00 -0700 (PDT)
Message-Id: <200210142059.g9EKx0sY022550@vashon.polstra.com>
To: net@freebsd.org
From: John Polstra <jdp@polstra.com>
Cc: hykim@cs.rice.edu
Subject: Re: Tigon 3 bad checksums on TCP packets
In-Reply-To: <Pine.GSO.4.33.0210111723110.9821-100000@frosty.cs.rice.edu>
References: <Pine.GSO.4.33.0210111723110.9821-100000@frosty.cs.rice.edu>
Organization: Polstra & Co., Seattle, WA
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org

In article <Pine.GSO.4.33.0210111723110.9821-100000@frosty.cs.rice.edu>,
Hyong-Youb Kim  <hykim@cs.rice.edu> wrote:
> 
> Thanks. I resolved the issue by forcing BGE_PCI_WRITE_BNDRY_16BYTES
> in BGE_PCI_DMA_RW_CTL register. The linux driver apparently has a DMA test
> code and sets this value depending on the test results. I have no clue as
> to why this configuration messes up TCP receive packets and not UDP
> packets.

I notice that everybody who's reported this problem has an Athlon.  I
guess there must be a bad interaction with the Athlon chipsets.  I
don't know why you're seeing the problem only on TCP packets.

John
-- 
  John Polstra
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message