From owner-freebsd-current@FreeBSD.ORG Sat May 8 17:18:11 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 81036106564A for ; Sat, 8 May 2010 17:18:11 +0000 (UTC) (envelope-from joe@hostedcontent.com) Received: from mail01.fasti.net (mail01.fasti.net [216.105.91.156]) by mx1.freebsd.org (Postfix) with ESMTP id 56AAB8FC18 for ; Sat, 8 May 2010 17:18:11 +0000 (UTC) Received: from mail01.fasti.net (localhost [127.0.0.2]) by mail01.fasti.net (Postfix) with ESMTP id B039D94B1031; Sat, 8 May 2010 13:18:10 -0400 (EDT) X-Virus-Scanned: amavisd-new at fasti.net Received: from mail01.fasti.net ([127.0.0.2]) by mail01.fasti.net (mail01.fasti.net [127.0.0.2]) (amavisd-new, port 10024) with ESMTP id zvcDpY1usyV6; Sat, 8 May 2010 13:18:09 -0400 (EDT) Received: from [192.168.1.137] (69-165-175-27.dsl.teksavvy.com [69.165.175.27]) by mail01.fasti.net (Postfix) with ESMTPA id AC6F894B1030; Sat, 8 May 2010 13:18:09 -0400 (EDT) Message-ID: <4BE59434.9070308@hostedcontent.com> Date: Sat, 08 May 2010 12:41:24 -0400 From: joe User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Ian FREISLICH References: <4BE565E5.9030505@hostedcontent.com> <4BE5303B.8050409@hostedcontent.com> <4BE529FF.5000008@hostedcontent.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Fabien Thomas Subject: Re: igb broken? Unexplained weirdness with intel 82576 nics on a supermicro board. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 08 May 2010 17:18:11 -0000 On 05/08/2010 11:17 AM, Ian FREISLICH wrote: > joe wrote: >> On 05/08/2010 06:55 AM, Ian FREISLICH wrote: >>> joe wrote: >>>> I have just tried your suggeston and it has no effect for me ;( >>> >>> Do you have another brand of NIC that you can try? At least that >>> will isolate whether it's igb(4) or something else. >> >> I will grab a new nic today and try...my options are limited though. >> Here are the nics i can get my hands on >> >> TP-LINK TL-TG3468, 10/100/1000Mbps PCIe Adapter (supported by fbsd?) > > Based on the RTL8168B chip. Should be supported by the re(4) driver. > >> Intel (EXPI9301CT) Gigabit CT Desktop Adapter (yet another intel nic) > > i82574L chip. Should be supported by the em(4) driver. I have had > good performance in the past with this driver and less than > satisfactory performance with the igb(4) driver. > > That may not be your problem though. Before you go out and buy, > have a look at the amount of interrupt time your slow machine spends > in 'top' or 'systat -vm'. systat will also show the interrupt rate > for each driver, perhaps it's not doing interrupt moderation properly. > This will manifest as more than about a 1000 per second. There are > loader tunables for the driver to increase the number of transfer > descriptors and to tune interrupt moderation. > > You could try running trafshow (port) on the interface while > performing the transfer. Perhaps promiscuous mode will turn off > some hardware feature that will improve things. It may however > break hardware vlanning as it does on my 82575GB 4 port igb card. > > Ian > > -- > Ian Freislich I bought those two cards anyways, im in a rush to figure out this problem. That being said i am still encountering the exact same problem regardless on which network card i am running. I am at a complete loss. I am about to try a raid card to see if the problem might lay within the onboard sata ports. I did pull the server and brought it home so that i can test more things quicker. I am going to try using a raid card instead of the onboard sata ports and see if i still encounter the same problem. I would love any suggestions you may have on where to go from here to figure out where the problem might be. joe