From owner-freebsd-current@FreeBSD.ORG Sat Feb 14 23:22:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F50B16A4CE for ; Sat, 14 Feb 2004 23:22:52 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4469F43D1D for ; Sat, 14 Feb 2004 23:22:52 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 72FCF65476 for ; Sun, 15 Feb 2004 07:22:51 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01964-01-5 for ; Sun, 15 Feb 2004 07:22:51 +0000 (GMT) Received: from saboteur.dek.spc.org (82-147-17-88.dsl.uk.rapidplay.com [82.147.17.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 085F66543E for ; Sun, 15 Feb 2004 07:22:51 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 47DD12B; Sun, 15 Feb 2004 07:22:50 +0000 (GMT) Date: Sun, 15 Feb 2004 07:22:50 +0000 From: Bruce M Simpson To: freebsd-current@freebsd.org Message-ID: <20040215072250.GE22136@saboteur.dek.spc.org> Mail-Followup-To: freebsd-current@freebsd.org References: <20040215072046.GD22136@saboteur.dek.spc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040215072046.GD22136@saboteur.dek.spc.org> Subject: Re: Unusual fxp behaviour with link0 flag X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2004 07:22:52 -0000 D'oh! Pardon my lack of sleep. On Sun, Feb 15, 2004 at 07:20:46AM +0000, Bruce M Simpson wrote: > I just noticed some unusual behaviour when running an fxp with the link0 > flag set (interrupt coalescing microcode enable). It might help if I mentioned what it was! Truncated IP datagrams. That is, only the first 40 bytes or so of every packet were making it through. This had the effect that I could ping the box, but TCP segments were mysteriously Going Nowhere, and tcpdump revealed a lot of [|ip]. BMS