From owner-freebsd-stable@FreeBSD.ORG Thu Oct 1 21:07:06 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BC611065672 for ; Thu, 1 Oct 2009 21:07:06 +0000 (UTC) (envelope-from crapsh@monkeybrains.net) Received: from ape.monkeybrains.net (mail.monkeybrains.net [208.69.40.9]) by mx1.freebsd.org (Postfix) with ESMTP id 44B9B8FC15 for ; Thu, 1 Oct 2009 21:07:06 +0000 (UTC) Received: from Computer-of-Penelope.local (adsl-76-195-160-241.dsl.pltn13.sbcglobal.net [76.195.160.241]) (authenticated bits=0) by ape.monkeybrains.net (8.14.3/8.14.1) with ESMTP id n91L706U046582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Oct 2009 14:07:00 -0700 (PDT) (envelope-from crapsh@monkeybrains.net) Message-ID: <4AC5198E.7030609@monkeybrains.net> Date: Thu, 01 Oct 2009 14:05:18 -0700 From: "Rudy (bulk)" User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 To: Jack Vogel References: <4AB9638B.8040607@monkeybrains.net> <4AC318E2.70306@monkeybrains.net> <4AC3DB8F.7010602@monkeybrains.net> <2a41acea0909301556g1df7dbafv813f5924553c8bfb@mail.gmail.com> In-Reply-To: <2a41acea0909301556g1df7dbafv813f5924553c8bfb@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.95.1 at pita.monkeybrains.net X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: em0 watchdog timeouts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Oct 2009 21:07:06 -0000 I have rxd and txd set to 1024. How high can I safely go? # add more descriptors to em devices. hw.em.rxd=1024 hw.em.txd=1024 ### other settings... I have tried rx_int_delay=0 and 32 ... doesn't seem to make the watchdogs go away. dev.em.4.rx_int_delay: 32 dev.em.4.tx_int_delay: 66 dev.em.4.rx_abs_int_delay: 66 dev.em.4.tx_abs_int_delay: 66 dev.em.4.rx_processing_limit: 300 I am using a PCI-Express (x8) PCI-e slot according to the motherboard specs: http://supermicro.com/products/motherboard/Xeon3000/3210/X7SBi.cfm Rudy Jack Vogel wrote: > Increase the size of your TX ring, meaning the number of TX descriptors. > > You said this is a quad port card, what size PCI E slot are you in? On > some motherboards slot connectors might suggest its of a certain size > but its not really wired fully. If you are not in a x8 lane slot move it to > one. > > What about system tuning? > > Some ideas, let me know how it goes. > > Jack > > > On Wed, Sep 30, 2009 at 3:28 PM, Rudy wrote: > > >> Rudy wrote: >> >> >>> Rudy wrote: >>> >>> >>>> I am having watchdog timeout issues >>>> >>>> >> Oh, here is some more info from 'pciconf -lcv'. >> >> I offloaded half the traffic from em0 to em5 and there has only been one >> watchdog timeout today (on em5) vs. 10 watchdog timeouts yesterday. We do >> streaming out of our network and the 3 second outage really messes things >> up... >> >> >> em0@pci0:5:0:0: class=0x020000 card=0x10a48086 chip=0x10a48086 rev=0x06 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82571EB Gigabit Ethernet Controller' >> class = network >> subclass = ethernet >> cap 01[c8] = powerspec 2 supports D0 D3 current D0 >> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message >> cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) >> em1@pci0:5:0:1: class=0x020000 card=0x10a48086 chip=0x10a48086 rev=0x06 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82571EB Gigabit Ethernet Controller' >> class = network >> subclass = ethernet >> cap 01[c8] = powerspec 2 supports D0 D3 current D0 >> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message >> cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) >> em2@pci0:6:0:0: class=0x020000 card=0x10a48086 chip=0x10a48086 rev=0x06 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82571EB Gigabit Ethernet Controller' >> class = network >> subclass = ethernet >> cap 01[c8] = powerspec 2 supports D0 D3 current D0 >> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message >> cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) >> em3@pci0:6:0:1: class=0x020000 card=0x10a48086 chip=0x10a48086 rev=0x06 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82571EB Gigabit Ethernet Controller' >> class = network >> subclass = ethernet >> cap 01[c8] = powerspec 2 supports D0 D3 current D0 >> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message >> cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4) >> em4@pci0:13:0:0: class=0x020000 card=0x108c15d9 chip=0x108c8086 >> rev=0x03 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82573E Intel Corporation 82573E Gigabit Ethernet >> Controller (Copper)' >> class = network >> subclass = ethernet >> cap 01[c8] = powerspec 2 supports D0 D3 current D0 >> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message >> cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) >> em5@pci0:15:0:0: class=0x020000 card=0x109a15d9 chip=0x109a8086 >> rev=0x00 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82573L Intel PRO/1000 PL Network Adaptor' >> class = network >> subclass = ethernet >> cap 01[c8] = powerspec 2 supports D0 D3 current D0 >> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message >> cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) >> vgapci0@pci0:17:3:0: class=0x030000 card=0xd18015d9 chip=0x515e1002 >> rev=0x02 >> >> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > >