eth0 (e1000e): transmit queue 0 timed out

Bug #1346828 reported by Thomas
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux-lts-trusty (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

With new kernel from trusty and raring I get this:

[ 1101.004258] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
[ 1101.004258] TDH <28>
[ 1101.004258] TDT <44>
[ 1101.004258] next_to_use <44>
[ 1101.004258] next_to_clean <28>
[ 1101.004258] buffer_info[next_to_clean]:
[ 1101.004258] time_stamp <308ce>
[ 1101.004258] next_to_watch <2a>
[ 1101.004258] jiffies <30e3b>
[ 1101.004258] next_to_watch.status <0>
[ 1101.004258] MAC Status <80083>
[ 1101.004258] PHY Status <796d>
[ 1101.004258] PHY 1000BASE-T Status <3800>
[ 1101.004258] PHY Extended Status <3000>
[ 1101.004258] PCI Status <10>
[ 1102.016013] ------------[ cut here ]------------
[ 1102.016028] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-lts-trusty-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x1fa/0x210()
[ 1102.016036] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out
[ 1102.016039] Modules linked in: xt_nat xt_multiport xt_TCPMSS xt_state xt_REDIRECT xt_mac xt_tcpudp ipt_MASQUERADE iptable_mangle iptable_nat nf_nat_ipv4 iptable_filter nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_proto_gre nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables pppoe pppox snd_hda_codec_realtek i915 drm_kms_helper snd_hda_intel snd_hda_codec drm snd_hwdep snd_pcm gpio_ich i2c_algo_bit snd_timer ppdev snd mei_me video soundcore parport_pc mei snd_page_alloc lpc_ich serio_raw mac_hid lp parport raid10 raid456 async_raid6_recov async_pq pata_acpi hid_generic 8139too e1000e usbhid ptp raid6_pq ahci r8169 async_xor 8139cp hid libahci pata_jmicron mii xor pps_core async_memcpy async_tx raid1 raid0 multipath linear
[ 1102.016125] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-32-generic #57~precise1-Ubuntu
[ 1102.016128] Hardware name: Gigabyte Technology Co., Ltd. EQ45M-S2/EQ45M-S2, BIOS FEb 07/29/2010
[ 1102.016131] 00000000 00000000 f300bea4 c1680147 c190e584 f300bed4 c1059b14 c190e548
[ 1102.016139] f300bf00 00000000 c190e584 00000108 c15b502a c15b502a f64b0000 00000000
[ 1102.016147] fffcf5aa f300beec c1059bd3 00000009 f300bee4 c190e548 f300bf00 f300bf28
[ 1102.016155] Call Trace:
[ 1102.016162] [<c1680147>] dump_stack+0x41/0x52
[ 1102.016168] [<c1059b14>] warn_slowpath_common+0x84/0xa0
[ 1102.016173] [<c15b502a>] ? dev_watchdog+0x1fa/0x210
[ 1102.016177] [<c15b502a>] ? dev_watchdog+0x1fa/0x210
[ 1102.016182] [<c1059bd3>] warn_slowpath_fmt+0x33/0x40
[ 1102.016186] [<c15b502a>] dev_watchdog+0x1fa/0x210
[ 1102.016194] [<c1065770>] call_timer_fn+0x30/0x110
[ 1102.016199] [<c15b4e30>] ? pfifo_fast_dequeue+0xe0/0xe0
[ 1102.016203] [<c106687c>] run_timer_softirq+0x20c/0x270
[ 1102.016208] [<c15b4e30>] ? pfifo_fast_dequeue+0xe0/0xe0
[ 1102.016213] [<c105e4f0>] ? perf_trace_irq_handler_entry+0x120/0x120
[ 1102.016218] [<c105e4f0>] ? perf_trace_irq_handler_entry+0x120/0x120
[ 1102.016223] [<c105e59a>] __do_softirq+0xaa/0x230
[ 1102.016227] [<c105e4f0>] ? perf_trace_irq_handler_entry+0x120/0x120
[ 1102.016230] <IRQ> [<c105e9b6>] ? irq_exit+0x76/0xa0
[ 1102.016237] [<c169327b>] ? do_IRQ+0x4b/0xc0
[ 1102.016242] [<c107be4e>] ? hrtimer_reprogram.isra.21+0x8e/0xe0
[ 1102.016247] [<c1693033>] ? common_interrupt+0x33/0x38
[ 1102.016253] [<c15500e0>] ? pentium4_get_frequency+0x30/0xd0
[ 1102.016258] [<c10488a5>] ? native_safe_halt+0x5/0x10
[ 1102.016264] [<c13b01b8>] ? arch_safe_halt+0x8/0xb
[ 1102.016268] [<c13b0acd>] ? acpi_safe_halt+0x1b/0x23
[ 1102.016272] [<c13b0af1>] ? acpi_idle_do_entry+0x1c/0x2b
[ 1102.016276] [<c13b0bd2>] ? acpi_idle_enter_c1+0x50/0x69
[ 1102.016280] [<c15531f9>] ? cpuidle_enter_state+0x39/0x100
[ 1102.016285] [<c1553357>] ? cpuidle_idle_call+0x97/0x1d0
[ 1102.016290] [<c10188bd>] ? arch_cpu_idle+0xd/0x30
[ 1102.016295] [<c10aa892>] ? cpu_idle_loop+0x52/0x240
[ 1102.016299] [<c10aaa99>] ? cpu_startup_entry+0x19/0x60
[ 1102.016304] [<c10aaade>] ? cpu_startup_entry+0x5e/0x60
[ 1102.016308] [<c1670a62>] ? rest_init+0x62/0x70
[ 1102.016314] [<c19fbb0f>] ? start_kernel+0x34a/0x350
[ 1102.016318] [<c19fb677>] ? repair_env_string+0x51/0x51
[ 1102.016323] [<c19fb39e>] ? i386_start_kernel+0x139/0x13c
[ 1102.016325] ---[ end trace 331c32f8d9ee8bdb ]---
[ 1102.016547] e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly
[ 1105.356869] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

and the network interface interrupts connection.

a workaround is to run

ethtool -K eth0 tso off
ethtool -K eth0 gso off

in /etc/rc.local

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1
ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
Date: Tue Jul 22 11:39:39 2014
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release i386 (20120424.1)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-lts-trusty
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Thomas (t.c) wrote :
Thomas (t.c)
tags: added: timeout
tags: added: performance
Revision history for this message
Thomas (t.c) wrote :
description: updated
Revision history for this message
Thomas (t.c) wrote :
Revision history for this message
Thomas (t.c) wrote :
Thomas (t.c)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-lts-trusty (Ubuntu):
status: New → Confirmed
Revision history for this message
Tuomas Heino (iheino+ub) wrote :

Same symptoms on amd64 (trusty lts installation) Testing mentioned workaround. Vlans in use and vlan offload still on (by default).

Tuomas Heino (iheino+ub)
tags: added: amd64
tags: added: trusty
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.