From owner-freebsd-sparc64@FreeBSD.ORG Tue Mar 21 06:20:28 2006 Return-Path: X-Original-To: freebsd-sparc64@freebsd.org Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9DAA16A400 for ; Tue, 21 Mar 2006 06:20:28 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 297FB43D49 for ; Tue, 21 Mar 2006 06:20:27 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k2L6KQgB022792; Mon, 20 Mar 2006 23:20:26 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <441F9B28.7030602@samsco.org> Date: Mon, 20 Mar 2006 23:20:24 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joerg Wunsch References: <20060320211720.GB31216@uriah.heep.sax.de> <20060320235732.GA79203@cdnetworks.co.kr> <20060321061508.GK31216@uriah.heep.sax.de> In-Reply-To: <20060321061508.GK31216@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-sparc64@freebsd.org Subject: Re: hme(4) broken on non-sparc64 systems in -current X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2006 06:20:28 -0000 Joerg Wunsch wrote: > As Pyun YongHyeon wrote: > > >>How about backing out rev. 1.46(if_hme.c)? > > >>For the same patch sent to bard@OpenBSD I got a positive report >>so it's strange to me though.(brad@OpenBSD reported Rx checksum >>offload breakage on little endian systems.) > > > Yes, backing that out helps. I'm not sure what this change was trying > to fix. I've noticed before that tools like ethereal reported the > checksum as invalid but the traffic itself was unaffected. Anyway, as > it was now, the traffic was blocked, so perhaps there's more than one > spot where this needs to be fixed? > > I'll look a bit further into it tonight. Thanks! > When tx checksum offloading is enabled, you'll always get checksum errors when capturing the local end of the transmission. That expected, since the checksum never gets computed until long after the bpf tap has captured it. Scott