From owner-freebsd-hackers@FreeBSD.ORG  Sat Jan 24 19:02:15 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 06EC716A4CE; Sat, 24 Jan 2004 19:02:15 -0800 (PST)
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1833E43D41; Sat, 24 Jan 2004 19:02:14 -0800 (PST)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com (localhost [127.0.0.1])
	i0P32B82039882;	Sat, 24 Jan 2004 19:02:11 -0800 (PST)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id i0P32BON039881;
	Sat, 24 Jan 2004 19:02:11 -0800 (PST)
	(envelope-from dillon)
Date: Sat, 24 Jan 2004 19:02:11 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <200401250302.i0P32BON039881@apollo.backplane.com>
To: Max Laier <max@love2party.net>
References: <Pine.NEB.3.96L.1040124104814.297K-100000@fledge.watson.org>
	<200401241739.51107.max@love2party.net>
cc: hackers@freebsd.org
cc: Robert Watson <rwatson@freebsd.org>
Subject: Re: XL driver checksum producing corrupted but checksum-correct
	packets
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Jan 2004 03:02:15 -0000

    Well, I tried to tcpdump a session.  I managed to hit the error three
    times but in all three cases the tcpdump on the server dropped the
    particular packet I was looking for.  I'm only able to get a 70%
    retention rate in the tcpdump output on the server... its just trying
    to record too much for the machine to handle at the rate the NFS requests
    are coming in.

    I'm going to give up trying to characterize the corruption for now.
    It could very well be the PCI latency timer as previously discussed
    but I can't test that right now.

						-Matt