What is the version of your ixgbe driver and you're kernel version? Also do you have FC enabled and are you see a large amount of pause frames? (i.e. ethtool -S output)
Thanks, -Don Skidmore <donald.c.skidm...@intel.com> p.s. I'll be out of town for a few days and don't know how often I'll be able to get to my email so I might be slow getting back to you. > -----Original Message----- > From: Viktor Khomyuk [mailto:v.khom...@office.ngs.ru] > Sent: Tuesday, November 26, 2013 8:22 PM > To: Skidmore, Donald C; e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] ETDEV WATCHDOG: eth0 (ixgbe): transmit queue > 0 timed out > > I see this message when one ospf neighbor fails and routes for his network > gone for maximum 3 seconds. > After 20 seconds something happens and this machine loose all network > connections Before this message i see Nov 22 11:06:38 egw4-1 ospfd[9419]: > nsm_change_state(195.93.186.253, Full -> Deleted): scheduling new router- > LSA origination Nov 22 11:06:58 egw4-1 kernel: [3010351.323607] ------------[ > cut here > ]------------ > Nov 22 11:06:58 egw4-1 kernel: [3010351.323619] WARNING: at > /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 > dev_watchdog+0x262/0x270() > Nov 22 11:06:58 egw4-1 kernel: [3010351.323623] Hardware name: X8SIE > > lspci and ethtool in attachment > > > > 26.11.2013 0:43, Skidmore, Donald C пишет: > > Those last "fake Tx Hang" messages from the driver show that the upper > stack is timing out while the driver doesn't think it has anything to do. The > stack dump previous to this is most likely the culprit. Since we don't see > any > ixgbe call's in the trace I wonder what is going on with the rest of the > network stack. When do you see this happening, at boot time, heavy traffic > loads? > > > > I would also be interested in seeing the device's statics (i.e. ethtool > > -S), as > well as the pci layout (i.e. lspci -vvv). Is there anything prior to this > stack > dump in the log that would imply something strange is going on? > > > > Thanks, > > -Don Skidmore <donald.c.skidm...@intel.com> > > > > > >> -----Original Message----- > >> From: Viktor Khomyuk [mailto:v.khom...@office.ngs.ru] > >> Sent: Sunday, November 24, 2013 8:12 PM > >> To: e1000-devel@lists.sourceforge.net > >> Subject: [E1000-devel] ETDEV WATCHDOG: eth0 (ixgbe): transmit queue 0 > >> timed out > >> > >> Hello! > >> I got this message. Is this a problem of driver or network card? > >> > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323607] ------------[ cut > >> here > >> ]------------ > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323619] WARNING: at > >> /build/buildd/linux-2.6.32/net/sched/sch_generic.c:261 > >> dev_watchdog+0x262/0x270() > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323623] Hardware name: X8SIE > >> Nov > >> 22 11:06:58 egw4-1 kernel: [3010351.323625] NETDEV WATCHDOG: eth0 > >> (ixgbe): transmit queue 0 timed out > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323628] Modules linked in: > >> ipt_NETFLOW ipt_LOG ipt_set xt_multiport iptable_filter xt_geoip > >> xt_comment xt_tcpudp xt_NOTRACK iptable_raw iptable_nat nf_nat > >> nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_mangle > >> ip_tables ip_set_iphash ip_set_nethash x_tables ip_set ip_vs ipmi_si > >> ipmi_devintf ipmi_msghandler 8021q garp stp ip_gre lp ixgbe parport > >> fbcon tileblit font bitblit softcursor vga16fb dca vgastate psmouse > >> serio_raw joydev usbhid hid megaraid_sas e1000e [last unloaded: > >> ipt_NETFLOW] Nov 22 11:06:58 egw4-1 > >> kernel: [3010351.323669] Pid: 0, comm: swapper Not tainted > >> 2.6.32-41-server #94-Ubuntu Nov 22 11:06:58 egw4-1 kernel: > [3010351.323672] Call Trace: > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323674] <IRQ> > >> [<ffffffff81067c8b>] > >> warn_slowpath_common+0x7b/0xc0 Nov 22 11:06:58 egw4-1 kernel: > >> [3010351.323686] [<ffffffff81067d31>] > >> warn_slowpath_fmt+0x41/0x50 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323691] [<ffffffff814925d2>] > >> dev_watchdog+0x262/0x270 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323695] [<ffffffff81081c37>] ? > >> insert_work+0x77/0xc0 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323703] [<ffffffff81039889>] ? > >> default_spin_lock_flags+0x9/0x10 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323710] [<ffffffff81094114>] ? > >> clockevents_program_event+0x54/0xa0 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323715] [<ffffffff81492370>] ? > >> dev_watchdog+0x0/0x270 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323720] [<ffffffff810785fb>] > >> run_timer_softirq+0x19b/0x340 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323725] [<ffffffff8109589a>] ? > >> tick_program_event+0x2a/0x30 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323731] [<ffffffff8106f347>] > >> __do_softirq+0xb7/0x1f0 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323737] [<ffffffff810c6960>] ? > >> handle_IRQ_event+0x60/0x170 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323742] [<ffffffff810142ac>] > >> call_softirq+0x1c/0x30 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323747] [<ffffffff81015c75>] > >> do_softirq+0x65/0xa0 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323750] [<ffffffff8106f145>] > >> irq_exit+0x85/0x90 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323757] [<ffffffff81565f45>] > >> do_IRQ+0x75/0xf0 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323761] [<ffffffff81013ad3>] > >> ret_from_intr+0x0/0x11 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323764] <EOI> > >> [<ffffffff8101b64f>] ? mwait_idle+0x6f/0xd0 Nov 22 11:06:58 egw4-1 > >> kernel: [3010351.323774] [<ffffffff81563b7a>] ? > >> atomic_notifier_call_chain+0x1a/0x20 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323779] [<ffffffff81011e43>] ? > >> cpu_idle+0xb3/0x110 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323785] [<ffffffff81548667>] ? > >> rest_init+0x77/0x80 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323793] [<ffffffff8188ddf7>] ? > >> start_kernel+0x36d/0x376 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323799] [<ffffffff8188d33a>] ? > >> x86_64_start_reservations+0x125/0x129 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323804] [<ffffffff8188d438>] ? > >> x86_64_start_kernel+0xfa/0x109 > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323807] ---[ end trace > >> 90d7fc0f54b55b35 ]--- > >> Nov 22 11:06:58 egw4-1 kernel: [3010351.323812] ixgbe 0000:01:00.0: > >> eth0: Fake Tx hang detected with timeout of 5 seconds Nov 22 11:06:58 > >> egw4-1 kernel: [3010361.307897] ixgbe 0000:01:00.0: > >> eth0: Fake Tx hang detected with timeout of 10 seconds Nov 22 > >> 11:06:58 > >> egw4-1 kernel: [3010381.276465] ixgbe 0000:01:00.0: > >> eth0: Fake Tx hang detected with timeout of 20 seconds > >> > >> --------------------------------------------------------------------- > >> --------- Shape the Mobile Experience: Free Subscription Software > >> experts and > >> developers: Be at the forefront of tech innovation. > >> Intel(R) Software Adrenaline delivers strategic insight and > >> game-changing conversations that shape the rapidly evolving mobile > landscape. Sign up now. > >> > http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg. > >> clk > >> trk > >> _______________________________________________ > >> E1000-devel mailing list > >> E1000-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/e1000-devel > >> To learn more about Intel® Ethernet, visit > >> http://communities.intel.com/community/wired ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
