From owner-freebsd-net@FreeBSD.ORG Tue Jun 17 21:27:11 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C51F8106567C for ; Tue, 17 Jun 2008 21:27:11 +0000 (UTC) (envelope-from crapsh@monkeybrains.net) Received: from ape.monkeybrains.net (ape.monkeybrains.net [208.69.40.11]) by mx1.freebsd.org (Postfix) with ESMTP id A6CD08FC13 for ; Tue, 17 Jun 2008 21:27:11 +0000 (UTC) (envelope-from crapsh@monkeybrains.net) Received: from monchichi.monkeybrains.net (adsl-75-63-17-233.dsl.pltn13.sbcglobal.net [75.63.17.233]) (authenticated bits=0) by ape.monkeybrains.net (8.14.1/8.14.1) with ESMTP id m5HLRBh9069036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 17 Jun 2008 14:27:11 -0700 (PDT) (envelope-from crapsh@monkeybrains.net) Message-ID: <48582C29.8030307@monkeybrains.net> Date: Tue, 17 Jun 2008 14:27:05 -0700 From: Rudy User-Agent: Thunderbird 2.0.0.12 (X11/20080310) MIME-Version: 1.0 To: freebsd-net@freebsd.org References: <20080516185813.H866@logos.sky.od.ua> <2a41acea0805160904g7dcf9f58rf69ca5d0612945cc@mail.gmail.com> <4853055C.2030303@MonkeyBrains.NET> <48535A11.4020003@monkeybrains.net> In-Reply-To: <48535A11.4020003@monkeybrains.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on pita.monkeybrains.net X-Virus-Status: Clean Subject: Seeking help understanding my "emX: watchdog timeout" messages X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2008 21:27:11 -0000 I am getting these messages: Jun 17 08:53:14 example kernel: em2: watchdog timeout -- resetting Jun 17 08:53:14 example kernel: em2: link state changed to DOWN Jun 17 08:53:17 example kernel: em2: link state changed to UP Jun 17 11:07:38 example kernel: em2: watchdog timeout -- resetting Jun 17 11:07:38 example kernel: em2: link state changed to DOWN Jun 17 11:07:41 example kernel: em2: link state changed to UP on an interface that does about 100Mbps all day. [1] should I worry about it (only happens a couple of times a day)? [2] will setting dev.em.2.rx_int_delay help? couldn't find too much documentation on it... Best I could get: http://www.intel.com/support/network/sb/cs-009209.htm [3] what, in you best estimation, is causing these wathdog events? sysctl dev.em.2.stats=1 Jun 17 13:23:22 example kernel: em2: Excessive collisions = 0 Jun 17 13:23:22 example kernel: em2: Sequence errors = 0 Jun 17 13:23:22 example kernel: em2: Defer count = 0 Jun 17 13:23:22 example kernel: em2: Missed Packets = 81518 Jun 17 13:23:22 example kernel: em2: Receive No Buffers = 1226 Jun 17 13:23:22 example kernel: em2: Receive Length Errors = 0 Jun 17 13:23:22 example kernel: em2: Receive errors = 0 Jun 17 13:23:22 example kernel: em2: Crc errors = 0 Jun 17 13:23:22 example kernel: em2: Alignment errors = 0 Jun 17 13:23:22 example kernel: em2: Collision/Carrier extension errors = 0 Jun 17 13:23:22 example kernel: em2: RX overruns = 0 Jun 17 13:23:22 example kernel: em2: watchdog timeouts = 20 Jun 17 13:23:22 example kernel: em2: RX MSIX IRQ = 0 TX MSIX IRQ = 0 LINK MSIX IRQ = 0 Jun 17 13:23:22 example kernel: em2: XON Rcvd = 0 Jun 17 13:23:22 example kernel: em2: XON Xmtd = 0 Jun 17 13:23:22 example kernel: em2: XOFF Rcvd = 0 Jun 17 13:23:22 example kernel: em2: XOFF Xmtd = 0 Jun 17 13:23:22 example kernel: em2: Good Packets Rcvd = 2515504832 Jun 17 13:23:22 example kernel: em2: Good Packets Xmtd = 4543057019 Jun 17 13:23:22 example kernel: em2: TSO Contexts Xmtd = 8 Jun 17 13:23:22 example kernel: em2: TSO Contexts Failed = 0 sysctl dev.em.2.debug=1 Jun 17 13:28:48 example kernel: em2: Adapter hardware address = 0xc4d91224 Jun 17 13:28:48 example kernel: em2: CTRL = 0x400c0241 RCTL = 0x8002 Jun 17 13:28:48 example kernel: em2: Packet buffer = Tx=16k Rx=32k Jun 17 13:28:48 example kernel: em2: Flow control watermarks high = 30720 low = 29220 Jun 17 13:28:48 example kernel: em2: tx_int_delay = 66, tx_abs_int_delay = 66 Jun 17 13:28:48 example kernel: em2: rx_int_delay = 0, rx_abs_int_delay = 66 Jun 17 13:28:48 example kernel: em2: fifo workaround = 0, fifo_reset_count = 0 Jun 17 13:28:48 example kernel: em2: hw tdh = 116, hw tdt = 116 Jun 17 13:28:48 example kernel: em2: hw rdh = 175, hw rdt = 174 Jun 17 13:28:48 example kernel: em2: Num Tx descriptors avail = 256 Jun 17 13:28:48 example kernel: em2: Tx Descriptors not avail1 = 20 Jun 17 13:28:48 example kernel: em2: Tx Descriptors not avail2 = 0 Jun 17 13:28:48 example kernel: em2: Std mbuf failed = 0 Jun 17 13:28:48 example kernel: em2: Std mbuf cluster failed = 0 Jun 17 13:28:48 example kernel: em2: Driver dropped packets = 0 Jun 17 13:28:48 example kernel: em2: Driver tx dma failure in encap = 0 sysctl dev.em.2 dev.em.2.%desc: Intel(R) PRO/1000 Network Connection 6.9.5 dev.em.2.%driver: em dev.em.2.%location: slot=0 function=0 dev.em.2.%pnpinfo: vendor=0x8086 device=0x10a4 subvendor=0x8086 subdevice=0x10a4 class=0x020000 dev.em.2.%parent: pci6 dev.em.2.debug: -1 dev.em.2.stats: -1 dev.em.2.rx_int_delay: 0 dev.em.2.tx_int_delay: 66 dev.em.2.rx_abs_int_delay: 66 dev.em.2.tx_abs_int_delay: 66 dev.em.2.rx_processing_limit: 100 Polling related sysctl settings: kern.polling.idlepoll_sleeping: 1 kern.polling.stalled: 82 kern.polling.suspect: 6266 kern.polling.phase: 0 kern.polling.enable: 1 kern.polling.handlers: 6 kern.polling.residual_burst: 0 kern.polling.pending_polls: 1 kern.polling.lost_polls: 371823 kern.polling.short_ticks: 4795 kern.polling.reg_frac: 20 kern.polling.user_frac: 33 kern.polling.idle_poll: 0 kern.polling.each_burst: 5 kern.polling.burst_max: 350 kern.polling.burst: 350 kern.clockrate: { hz = 2500, tick = 400, profhz = 1666, stathz = 333 } hadware is a quad Intel 1000 Pro PT card. Thanks!!!! Rudy