Network driver problem e1000e [proxmox 4.1-34]

[Nemesiz]

Yesterday I upgraded Proxmox to:

# pveversion -v
proxmox-ve: 4.1-34 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-5 (running version: 4.1-5/f910ef5c)
pve-kernel-4.2.6-1-pve: 4.2.6-34
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.2.3-2-pve: 4.2.3-22
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-30
qemu-server: 4.0-46
pve-firmware: 1.1-7
libpve-common-perl: 4.0-43
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-21
pve-container: 1.0-37
pve-firewall: 2.0-15
pve-ha-manager: 1.0-18
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve3
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie
openvswitch-switch: 2.3.2-2

and intel network driver starts to hang

Feb 7 10:02:07 nmz-lt kernel: [ 4066.632556] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out
Feb 7 10:02:07 nmz-lt kernel: [ 4066.632635] 0000000000000000 06637e768174b2fb ffff880c3fd03d58 ffffffff818013c8
Feb 7 10:02:07 nmz-lt kernel: [ 4066.632648] [<ffffffff8107b66a>] warn_slowpath_common+0x8a/0xc0
Feb 7 10:02:07 nmz-lt kernel: [ 4066.632656] [<ffffffff8170e830>] ? dev_deactivate_queue.constprop.34+0x70/0x70
Feb 7 10:02:07 nmz-lt kernel: [ 4066.632665] [<ffffffff818091db>] apic_timer_interrupt+0x6b/0x70
Feb 7 10:02:07 nmz-lt kernel: [ 4066.632674] [<ffffffff810bdbeb>] call_cpuidle+0x3b/0x70
Feb 7 10:02:07 nmz-lt kernel: [ 4066.632688] e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly
Feb 7 10:02:55 nmz-lt systemd-timesyncd[5631]: interval/delta/delay/jitter/drift 2048s/-0.043s/0.010s/0.019s/+12ppm
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] TDH <ee>
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] TDT <7>
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] next_to_use <7>
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] next_to_clean <ec>
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] buffer_info[next_to_clean]:
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] time_stamp <1000ea06d>
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] next_to_watch <ee>
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] jiffies <1000ea3df>
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] next_to_watch.status <0>
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] MAC Status <40080083>
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] PHY Status <796d>
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] PHY 1000BASE-T Status <7800>
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] PHY Extended Status <3000>
Feb 7 10:03:14 nmz-lt kernel: [ 4133.605646] PCI Status <10>
Feb 7 10:03:17 nmz-lt kernel: [ 4136.614184] e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly

The strange thing is that current kernel 4.2.6-34 use the same driver version as kernel 4.2.3-22 which had no problem

filename: /lib/modules/4.2.6-1-pve/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
version: 3.2.7.1-NAPI
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>
srcversion: 6D593AEFF69A2B7D8256288

filename: /lib/modules/4.2.3-2-pve/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
version: 3.2.7.1-NAPI
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>
srcversion: 6D593AEFF69A2B7D8256288

My Ethernet controller

00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05)

Does anyone else have similar problem ?

 

[Nemesiz]

filename: /lib/modules/4.2.6-1-pve/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
version: 3.3.3-NAPI
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>
srcversion: BC7D8BD3880A3E5F62C57D7

Not helped.

Feb 8 11:39:21 nmz-lt kernel: [96212.457859] e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly