From owner-freebsd-stable@FreeBSD.ORG Fri Oct 2 20:36:13 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 0C82710656A6 for ; Fri, 2 Oct 2009 20:36:13 +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 CD1688FC16 for ; Fri, 2 Oct 2009 20:36:12 +0000 (UTC) Received: from [10.17.45.149] (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 n92Ka6fF058037 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Oct 2009 13:36:07 -0700 (PDT) (envelope-from crapsh@monkeybrains.net) Message-ID: <4AC66437.4040704@monkeybrains.net> Date: Fri, 02 Oct 2009 13:36:07 -0700 From: Rudy User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Jack Vogel References: <4AB9638B.8040607@monkeybrains.net> <4AC318E2.70306@monkeybrains.net> <4AC3DB8F.7010602@monkeybrains.net> <2a41acea0909301556g1df7dbafv813f5924553c8bfb@mail.gmail.com> <4AC5198E.7030609@monkeybrains.net> <4AC51B4C.7080905@monkeybrains.net> <2a41acea0910011450v41590f3dn112f367f26faed2d@mail.gmail.com> <4AC64835.3060107@monkeybrains.net> <2a41acea0910021237w415efa2cs4354a0f99aef8f6@mail.gmail.com> In-Reply-To: <2a41acea0910021237w415efa2cs4354a0f99aef8f6@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 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: Fri, 02 Oct 2009 20:36:13 -0000 Ah, I'll stop messing with them. I just set them all to 0 to see if that will help and noticed the card was leaving tx_int_delay=1. # sysctl dev.em.4.debug=1 Oct 2 13:26:07 mango kernel: em4: tx_int_delay = 1, tx_abs_int_delay = 0 Oct 2 13:26:07 mango kernel: em4: rx_int_delay = 0, rx_abs_int_delay = 0 # sysctl dev.em.4 dev.em.4.%desc: Intel(R) PRO/1000 Network Connection 6.9.12 dev.em.4.rx_int_delay: 0 dev.em.4.tx_int_delay: 0 dev.em.4.rx_abs_int_delay: 0 dev.em.4.tx_abs_int_delay: 0 Splitting traffic to different ports has brought down the watchdog events to once a day. ... essentially, I have a quad 30Mbps (not quad 1Gbps) card. heheh. Would turning off net.inet.ip.fastforwarding or any other setting help? Today, I set net.inet.ip.fw.enable=0 and I'll see if that helps. I have a feeling that isn't related to the NIC at all, but I'm not sure what else to try. Rudy Jack Vogel wrote: > Watchdog resets the adapter. Messing with these values is of dubious value > anyway. > > Jack > > > On Fri, Oct 2, 2009 at 11:36 AM, Rudy wrote: > > >> I noticed something interesting. >> >> I set the rc_int_delay to 0: >> sysctl dev.em.5.rx_int_delay=0 >> >> Chcking via sysctl dev.em.5.debug=1 shows ex_int_delay is indeed 0: >> Oct 1 17:32:41 mango kernel: em5: rx_int_delay = 0, rx_abs_int_delay = 66 >> >> After a watchdog event, sysctl dev.em.5.debug=1 shows ex_int_delay is >> now 32: >> Oct 2 11:29:49 mango kernel: em5: rx_int_delay = 32, rx_abs_int_delay = >> 66 >> >> However, running sysctl dev.em.5 shows it as 0: >> dev.em.5.rx_int_delay: 0 >> dev.em.5.tx_int_delay: 66 >> >> Seems like the adapter and the kernel don't agree on the rx_int_delay >> value. >> >> Rudy >> >> > >