From owner-freebsd-stable@FreeBSD.ORG Fri Oct 2 00:38:37 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 0BBD81065698 for ; Fri, 2 Oct 2009 00:38:37 +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 E84508FC1B for ; Fri, 2 Oct 2009 00:38:36 +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 n920cVep098543 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Oct 2009 17:38:31 -0700 (PDT) (envelope-from crapsh@monkeybrains.net) Message-ID: <4AC54B87.2030604@monkeybrains.net> Date: Thu, 01 Oct 2009 17:38:31 -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> In-Reply-To: <2a41acea0910011450v41590f3dn112f367f26faed2d@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 00:38:37 -0000 > What about system load, perhaps something is bogging the thing down so that > it cannot adequately service the network interrupts?? > Hardly anything is running on the box... Only things on the box: zebra bgpd (3 peers...) sshd snmpd Here is the top of 'top': load averages: 0.06, 0.08, 0.07 up 7+01:08:16 17:26:39 15 processes: 1 running, 14 sleeping CPU: 0.0% user, 0.0% nice, 4.5% system, 0.0% interrupt, 95.5% idle Mem: 193M Active, 42M Inact, 156M Wired, 196K Cache, 83M Buf, 1610M Free > The specs of the motherboard are respectable, how much memory does it have? > > Another thought, are you using the out-of-band management features (like > IPMI)? > If you are not then go into the BIOS and disable that stuff. > No IPMI card added to that motherboard (you have to add a daughter card). > Have you run netstat or some other resource monitor to see if you run out of > anything that might coincide with the watchdogs... What should I look for? # netstat -s 4105/4610/8715 mbufs in use (current/cache/total) 4103/2303/6406/25600 mbuf clusters in use (current/cache/total/max) 4103/2297 mbuf+clusters out of packet secondary zone in use (current/cache) 0/44/44/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 9232K/5934K/15166K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/6/6656 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines Are there specific router-only tunings that may help? Here are my sysctl settings: kern.ipc.somaxconn=256 kern.random.sys.harvest.interrupt=0 kern.random.sys.harvest.ethernet=0 kern.ipc.nmbcluster=32768 net.inet.icmp.icmplim=1000 net.inet.ip.fastforwarding=1 net.inet.ip.intr_queue_maxlen=92 net.inet.icmp.drop_redirect=1 dev.em.0.rx_processing_limit=200 dev.em.1.rx_processing_limit=200 dev.em.2.rx_processing_limit=200 #dev.em.4.rx_processing_limit=200 # test setting processing limit up to 300 dev.em.4.rx_processing_limit=300 dev.em.5.rx_processing_limit=200 Thanks, Rudy