[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#727149: linux-image-3.10-3-amd64: Network adapter (Intel 82579V) hangs during TX, causing reset and undetected data corruption at the other side



I don't know, because until now I have been using the workaround (i.e. always disable TSO).

I just re-enabled it to see if this error will still occur with the latest kernel. I'll report again in a week or so whether it is stable now.

Unfortunately, the bug still occurs. See the log below.

Cheers,

Timo

-----


[133754.072957] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.16-3-amd64 #1 Debian 3.16.5-1 [133754.072959] Hardware name: /DB75EN, BIOS ENB7510H.86A.0046.2013.0704.1354 07/04/2013 [133754.072961] 0000000000000009 ffffffff815066c3 ffff88021e203e28 ffffffff81065717 [133754.072964] 0000000000000000 ffff88021e203e78 0000000000000001 0000000000000000 [133754.072967] ffff880212c24000 ffffffff8106577c ffffffff81775de8 ffffffff00000030
[133754.072970] Call Trace:
[133754.072972]  <IRQ>  [<ffffffff815066c3>] ? dump_stack+0x41/0x51
[133754.072982]  [<ffffffff81065717>] ? warn_slowpath_common+0x77/0x90
[133754.072985]  [<ffffffff8106577c>] ? warn_slowpath_fmt+0x4c/0x50
[133754.072990]  [<ffffffff81072667>] ? mod_timer+0x127/0x1e0
[133754.072995]  [<ffffffff8143a0c6>] ? dev_watchdog+0x236/0x240
[133754.072998]  [<ffffffff81439e90>] ? dev_graft_qdisc+0x70/0x70
[133754.073001]  [<ffffffff810709d1>] ? call_timer_fn+0x31/0x100
[133754.073004]  [<ffffffff81439e90>] ? dev_graft_qdisc+0x70/0x70
[133754.073007]  [<ffffffff81072009>] ? run_timer_softirq+0x209/0x2f0
[133754.073012]  [<ffffffff8106a5b1>] ? __do_softirq+0xf1/0x290
[133754.073015]  [<ffffffff8106a985>] ? irq_exit+0x95/0xa0
[133754.073019]  [<ffffffff8150f695>] ? smp_apic_timer_interrupt+0x45/0x60
[133754.073022]  [<ffffffff8150d79d>] ? apic_timer_interrupt+0x6d/0x80
[133754.073023] <EOI> [<ffffffff81072916>] ? get_next_timer_interrupt+0x1d6/0x250
[133754.073031]  [<ffffffff813d9cbf>] ? cpuidle_enter_state+0x4f/0xc0
[133754.073034]  [<ffffffff813d9cb8>] ? cpuidle_enter_state+0x48/0xc0
[133754.073038]  [<ffffffff810a5d38>] ? cpu_startup_entry+0x2f8/0x400
[133754.073043]  [<ffffffff8190305a>] ? start_kernel+0x47b/0x486
[133754.073046]  [<ffffffff81902a04>] ? set_init_arg+0x4e/0x4e
[133754.073050]  [<ffffffff81902120>] ? early_idt_handlers+0x120/0x120
[133754.073054]  [<ffffffff8190271f>] ? x86_64_start_kernel+0x14d/0x15c
[133754.073056] ---[ end trace a9b0eebac757b4ab ]---
[133754.073096] e1000e 0000:00:19.0 eth2: Reset adapter unexpectedly
[133757.816772] e1000e: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[134277.894290] e1000e 0000:00:19.0 eth2: Detected Hardware Unit Hang:
[134277.894290]   TDH                  <5b>
[134277.894290]   TDT                  <71>
[134277.894290]   next_to_use          <71>
[134277.894290]   next_to_clean        <5b>
[134277.894290] buffer_info[next_to_clean]:
[134277.894290]   time_stamp           <101ff3d7b>
[134277.894290]   next_to_watch        <5b>
[134277.894290]   jiffies              <101ff3fb5>
[134277.894290]   next_to_watch.status <0>
[134277.894290] MAC Status             <40080083>
[134277.894290] PHY Status             <796d>
[134277.894290] PHY 1000BASE-T Status  <3800>
[134277.894290] PHY Extended Status    <3000>
[134277.894290] PCI Status             <10>


Reply to: