From owner-freebsd-current@FreeBSD.ORG Mon Oct 11 19:33:16 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 249D316A4CE for ; Mon, 11 Oct 2004 19:33:16 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB11543D1F for ; Mon, 11 Oct 2004 19:33:15 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id i9BJVgfg053767; Mon, 11 Oct 2004 15:31:42 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i9BJVgZN053764; Mon, 11 Oct 2004 15:31:42 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 11 Oct 2004 15:31:42 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Sean McNeil In-Reply-To: <1097517044.1795.12.camel@server> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: 20% packet loss with re0 in gigE mode vs. 0% in 100BT 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: Mon, 11 Oct 2004 19:33:16 -0000 On Mon, 11 Oct 2004, Sean McNeil wrote: > > Assuming you're not filling the send buffer, it would definitely suggest a > > driver, configuration, or hardware bug. There have recently been a number > > of changes to the if_re driver to fix support for jumbo frames, etc. It > > would be interesting to know whether backing out to earlier revisions of > > the if_re driver affect the problem you're seeing. In particular, > > ifre.c:1.35 was the jumbo frame change, so 1.34 would be interesting, and > > 1.31 is before some other related changes. Likewise, you could try > > backing out to before locking was introduced by setting debug.mpsafenet=0 > > in loader.conf and then backing out to if_re.c:1.29. I might be generally > > useful to try setting debug.mpsafenet=0 with the current driver to > > eliminate that as a possible concern. > > These are good suggestions as well, but I have heard from another user > that has seen this kind of thing over all of these versions. It is less > likely then that the jumbo or locking changes caused the issue. Have you tried 4.x to see if the same problem occurs there? Have you tried the normal juggling of ACPI, APIC, and other configuration variables? It sounds like things work fine at minimal bandwidth rates, so that probably rules out interrupt problems and the like, but I figured it was worth asking. I assume you've probably looked at substituting the switch, forcing auto-negotiation to 1gb, etc? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research