Date: Fri, 20 Jun 2008 13:11:51 -0700 From: Rudy <crapsh@monkeybrains.net> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: Seeking help understanding my "emX: watchdog timeout" messages Message-ID: <485C0F07.7000408@monkeybrains.net> In-Reply-To: <2a41acea0806191055w5e112b8bsa57a8db2b177adbe@mail.gmail.com> References: <20080516185813.H866@logos.sky.od.ua> <2a41acea0805160904g7dcf9f58rf69ca5d0612945cc@mail.gmail.com> <4853055C.2030303@MonkeyBrains.NET> <48535A11.4020003@monkeybrains.net> <48582C29.8030307@monkeybrains.net> <2a41acea0806191055w5e112b8bsa57a8db2b177adbe@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jack Vogel wrote: > Watchdog reset is an indication that the TX completion did not happen > within a reasonable time, it can the symptom of a variety of problems. > > You list a bunch of settings for polling, is this interface in POLLING > mode? > Yes, DEVICE_POLLING is in the kernel and kern.polling.enable=1. I did not issue a "ifconfig em2 polling" and I see it running, so I assume that it is in POLLING mode. em2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=1db<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,POLLING,VLAN_HWCSUM,TSO4> ether 00:15:17:78:99:72 inet 64.215.30.154 netmask 0xfffffffc broadcast 64.215.30.155 media: Ethernet autoselect (1000baseTX <full-duplex>) status: active Interestingly, I also get the watchdog timeouts on my em4 (motherboard 82573E NIC). In a 24 hour period, I see 8 'watchdog timeout' events. 4 on em2 and 4 on em4. Both are uplinks to different cisco switches which vlan those ports to fiber uplinks. Thank you for your time Jack, Rudy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?485C0F07.7000408>