From owner-freebsd-net@FreeBSD.ORG Thu Jan 6 05:20:50 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 D092D106564A for ; Thu, 6 Jan 2011 05:20:50 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2-b.corp.re1.yahoo.com (mrout2-b.corp.re1.yahoo.com [69.147.107.21]) by mx1.freebsd.org (Postfix) with ESMTP id 8B7C78FC0A for ; Thu, 6 Jan 2011 05:20:50 +0000 (UTC) Received: from [127.0.0.1] (proxy8.corp.yahoo.com [216.145.48.13]) by mrout2-b.corp.re1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p065KTT7091232; Wed, 5 Jan 2011 21:20:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=yahoo-inc.com; s=cobra; t=1294291229; bh=6NcpOL28i2huoxdzH7NhnB7GHYPr9cvnfe7scirZwUs=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=MZ4NpR2AVadiBnErDGY/TO4dRMEYyNetrgexosn9iB+2HSRbCDUOOqZF51OUSZxJv 7Vm2er9LvyWScqkvK2byiE7IBB2b+S6y3TtHt+/Eo1O4QNPwOskMM9ISyd5zakianv EyccoUioeREEHr241Op81Msax+coa0JCSE5dZzBk= From: Sean Bruno To: Robin Sommer In-Reply-To: <20110103210209.GA13091@icir.org> References: <20100729215649.GB2615@icir.org> <20110103210209.GA13091@icir.org> Content-Type: text/plain; charset="UTF-8" Date: Wed, 05 Jan 2011 21:20:28 -0800 Message-ID: <1294291228.2225.0.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 (2.32.1-1.fc14) Content-Transfer-Encoding: 7bit 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, 06 Jan 2011 05:20:51 -0000 On Mon, 2011-01-03 at 13:02 -0800, 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 > > [...] > I don't suppose you have ASPM enabled? If so, turn it off. That seemed to make things go much better here at Yahoo. Sean