From owner-freebsd-net@FreeBSD.ORG Thu Jan 13 03:23:18 2011 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 4D5A910656AC for ; Thu, 13 Jan 2011 03:23:18 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (edge.tidalhosting.net [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id 04CD18FC1F for ; Thu, 13 Jan 2011 03:23:17 +0000 (UTC) Received: from jack.bspruce.com ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Wed, 12 Jan 2011 21:43:15 -0500 X-WatchGuard-Mail-Exception: Allow Message-ID: <4D2E66C4.5090607@greatbaysoftware.com> Date: Wed, 12 Jan 2011 21:43:16 -0500 From: Charles Owens MIME-Version: 1.0 To: Robin Sommer References: <20100729215649.GB2615@icir.org> <20110103210209.GA13091@icir.org> In-Reply-To: <20110103210209.GA13091@icir.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Cc: freebsd-net Subject: Re: igb watchdog timeouts 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: Thu, 13 Jan 2011 03:23:18 -0000 I'd like to report that we're running into this issue also, in our case on systems that are based on the Intel S5520UR Server Board, running 8.1-RELEASE. If the ichwd driver is loaded we see the same messages, and network communication via the igb nics is non-functional. Have you had any luck? Thanks, Charles Charles Owens Great Bay Software, Inc. On 1/3/11 4:02 PM, Robin Sommer wrote: > Hello all, > > quite a while ago I asked about the problem below. Unfortunately, I > haven't found a solution yet and I'm actually still seeing these > timeouts after just upgrading to 8.2-RC1. Any further ideas on what > could be triggering them, or how I could track down the cause? > > Thanks, > > Robin > > On Thu, Jul 29, 2010 at 14:56 -0700, I wrote: > >> Since upgrading from 8.0 to 8.1-RELEASE, I'm seeing lots of messages >> like those below on all my SuperMicro SBI-7425C-T3 blades. There's >> almost no traffic on those interfaces. >> >> Any idea? >> >> Thanks, >> >> Robin >> >> Jul 29 13:01:18 blade0 kernel: igb1: Watchdog timeout -- resetting >> Jul 29 13:01:18 blade0 kernel: igb1: Queue(0) tdh = 256, hw tdt = 266 >> Jul 29 13:01:18 blade0 kernel: igb1: TX(0) desc avail = 1013,Next TX to Clean = 255 >> Jul 29 13:01:18 blade0 kernel: igb1: link state changed to DOWN >> Jul 29 13:01:18 blade0 kernel: igb1: link state changed to UP >> Jul 29 13:01:29 blade0 kernel: igb1: Watchdog timeout -- resetting >> Jul 29 13:01:29 blade0 kernel: igb1: Queue(0) tdh = 0, hw tdt = 10 >> Jul 29 13:01:29 blade0 kernel: igb1: TX(0) desc avail = 1014,Next TX to Clean = 0 >> Jul 29 13:01:29 blade0 kernel: igb1: link state changed to DOWN >> Jul 29 13:01:29 blade0 kernel: igb1: link state changed to UP >> Jul 29 13:01:46 blade0 kernel: igb1: Watchdog timeout -- resetting >> Jul 29 13:01:46 blade0 kernel: igb1: Queue(0) tdh = 32, hw tdt = 33 >> Jul 29 13:01:46 blade0 kernel: igb1: TX(0) desc avail = 1022,Next TX to Clean = 31 >> Jul 29 13:01:46 blade0 kernel: igb1: link state changed to DOWN >> Jul 29 13:01:46 blade0 kernel: igb1: link state changed to UP >> Jul 29 13:01:57 blade0 kernel: igb1: Watchdog timeout -- resetting >> Jul 29 13:01:57 blade0 kernel: igb1: Queue(0) tdh = 0, hw tdt = 10 >> Jul 29 13:01:57 blade0 kernel: igb1: TX(0) desc avail = 1014,Next TX to Clean = 0 >> Jul 29 13:01:57 blade0 kernel: igb1: link state changed to DOWN >> Jul 29 13:01:58 blade0 kernel: igb1: link state changed to UP >> Jul 29 13:02:13 blade0 kernel: igb1: Watchdog timeout -- resetting >> >>> grep igb /var/run/dmesg.boot >> igb0: port 0x2000-0x201f mem 0xfc940000-0xfc95ffff,0xfc920000-0xfc93ffff,0xfc900000-0xfc903fff irq 16 at device 0.0 on pci4 >> igb0: [FILTER] >> igb0: Ethernet address: 00:30:48:9e:22:00 >> igb1: port 0x2020-0x203f mem 0xfc980000-0xfc99ffff,0xfc960000-0xfc97ffff,0xfc904000-0xfc907fff irq 17 at device 0.1 on pci4 >> igb1: [FILTER] >> igb1: Ethernet address: 00:30:48:9e:22:01 >> >>> pciconf -lv >> [...] >> igb0@pci0:4:0:0: class=0x020000 card=0x10a915d9 >> chip=0x10a98086 rev=0x02 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82575EB Gigabit Backplane Connection' >> class = network >> subclass = ethernet >> igb1@pci0:4:0:1: class=0x020000 card=0x10a915d9 >> chip=0x10a98086 rev=0x02 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82575EB Gigabit Backplane Connection' >> class = network >> subclass = ethernet >> [...]