Date: Sat, 24 Jan 2004 21:12:23 +0000 (GMT) From: Sam Smith <S@mSmith.net> To: Robert Watson <rwatson@freebsd.org> Cc: hackers@freebsd.org Subject: Re: XL driver checksum producing corrupted but checksum-correct packets Message-ID: <Pine.BSO.4.58.0401242104080.13755@sebastian.foriru.co.uk> In-Reply-To: <Pine.NEB.3.96L.1040124133352.62871C-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1040124133352.62871C-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 24 Jan 2004, Robert Watson wrote: > On Sat, 24 Jan 2004, Max Laier wrote: > > On Saturday 24 January 2004 17:06, Robert Watson wrote: > > > On Fri, 23 Jan 2004, Matthew Dillon wrote: > > > > I tracked down an occassional buildworld failure on DragonFly to > > > > my XL driver, which is synchronized to 4.x's XL driver. > > > > FYI: This was reproduced on OpenBSD as well (w/ ftp and scp): > > http://marc.theaimsgroup.com/?l=openbsd-tech&m=107494884327698&w=2 > > Two thoughts on other things to try, with that in mind: The thread on the OpenBSD list now contains a patch which seems to fix the problem (for me, on OpenBSD, shifting data by both NFS and ftp doing md5 checksums on the files at both ends). Although it doesn't seem to turn off hardware checksums (which is what I think it should do). Regards Sam -- Murphy's revenge: The more reliable you make a system, the longer it will take you to figure out what's wrong when it breaks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSO.4.58.0401242104080.13755>