Date: Wed, 05 Jan 2011 21:20:28 -0800 From: Sean Bruno <seanbru@yahoo-inc.com> To: Robin Sommer <robin@icir.org> Cc: freebsd-net <freebsd-net@freebsd.org> Subject: Re: igb watchdog timeouts Message-ID: <1294291228.2225.0.camel@hitfishpass-lx.corp.yahoo.com> In-Reply-To: <20110103210209.GA13091@icir.org> References: <20100729215649.GB2615@icir.org> <20110103210209.GA13091@icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <Intel(R) PRO/1000 Network Connection version - 1.9.5> 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: <Intel(R) PRO/1000 Network Connection version - 1.9.5> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1294291228.2225.0.camel>