kernel 3.5.5, 3.5.7 problem z siecią

[Grzesiek Pycia]

Na kernelu 3.5.7 (arch x86_64 proc intel Xeon E3-1230 sieciówka intel 
82574L) na sterowniku e1000e w wersji 2.0.0 występuje u mnie problem z 
siecią.

Ruch co kilka kilkanaście sekund "zwalnia" pingi do maszyny podskakują 
do 2-3 sekund czasami kilka ginie na dłuższą metę do loga leci:


Dec  2 01:53:25 kapitan kernel: [ 2367.171450] ------------[ cut here 
]------------
Dec  2 01:53:25 kapitan kernel: [ 2367.171459] WARNING: at 
/home/users/builder/rpm/BUILD/kernel-3.5.7/linux-3.5/net/sched/sch_generic.c:255 
dev_watchdog+0x25b/0x270()
Dec  2 01:53:25 kapitan kernel: [ 2367.171460] Hardware name: 
X9SCL-II/X9SCM-II
Dec  2 01:53:25 kapitan kernel: [ 2367.171462] NETDEV WATCHDOG: eth0 
(e1000e): transmit queue 0 timed out
Dec  2 01:53:25 kapitan kernel: [ 2367.171463] Modules linked in: 
ip6table_filter ip6_tables ipt_MASQUERADE ipt_REJECT xt_CHECKSUM bridge 
stp llc act_mirred cls_u32 sch_ingress ifb cls_fw sch_htb 
ip_set_bitmap_ip(O) ipt_ULOG sch_sfq xt_IPMARK(O) xt_length xt_CLASSIFY 
xt_ACCOUNT(O) compat_xtables(O) iptable_mangle ipt_REDIRECT iptable_nat 
nf_nat xt_LOG xt_limit xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_set(O) xt_multiport xt_conntrack nf_conntrack iptable_filter 
iptable_raw ip_tables x_tables ip_set_hash_net(O) ip_set_hash_ip(O) 
ip_set_bitmap_ipmac(O) ip_set(O) nfnetlink md_mod dm_mod vhost_net tun 
macvtap macvlan ipmi_devintf ipmi_si ipmi_msghandler joydev hid_generic 
evdev acpi_cpufreq mperf aesni_intel aes_x86_64 aes_generic 
ghash_clmulni_intel cryptd kvm_intel freq_table kvm coretemp hwmon 
crc32c_intel psmouse serio_raw pcspkr acpi_pad e1000e(O) video intel_agp 
button intel_gtt i2c_i801 processor lpc_ich mei i2c_core fan thermal 
sd_mod crc_t10dif usbhid hid ehci_hcd usbcore usb_common ahci libahci 
libata scsi_mod ext4 jbd2 mbcache crc16 [last unloaded: microcode]
Dec  2 01:53:25 kapitan kernel: [ 2367.171535] Pid: 0, comm: swapper/0 
xid: #0 Tainted: G           O 3.5.7-1 #1
Dec  2 01:53:25 kapitan kernel: [ 2367.171536] Call Trace:
Dec  2 01:53:25 kapitan kernel: [ 2367.171538]  <IRQ> 
[<ffffffff8104ce6a>] warn_slowpath_common+0x7a/0xb0
Dec  2 01:53:25 kapitan kernel: [ 2367.171547]  [<ffffffff8104cf41>] 
warn_slowpath_fmt+0x41/0x50
Dec  2 01:53:25 kapitan kernel: [ 2367.171552]  [<ffffffff813d2ecb>] 
dev_watchdog+0x25b/0x270
Dec  2 01:53:25 kapitan kernel: [ 2367.171564]  [<ffffffff813d2c70>] ? 
pfifo_fast_dequeue+0xe0/0xe0
Dec  2 01:53:25 kapitan kernel: [ 2367.171566]  [<ffffffff8105cfe1>] 
run_timer_softirq+0x141/0x340
Dec  2 01:53:25 kapitan kernel: [ 2367.171569]  [<ffffffff810a090f>] ? 
ktime_get+0x5f/0xe0
Dec  2 01:53:25 kapitan kernel: [ 2367.171571]  [<ffffffff81055678>] 
__do_softirq+0xa8/0x1b0
Dec  2 01:53:25 kapitan kernel: [ 2367.171573]  [<ffffffff810a7a8f>] ? 
tick_program_event+0x1f/0x30
Dec  2 01:53:25 kapitan kernel: [ 2367.171575]  [<ffffffff814c4adc>] 
call_softirq+0x1c/0x30
Dec  2 01:53:25 kapitan kernel: [ 2367.171577]  [<ffffffff81015105>] 
do_softirq+0x65/0xa0
Dec  2 01:53:25 kapitan kernel: [ 2367.171579]  [<ffffffff810559f6>] 
irq_exit+0x86/0xb0
Dec  2 01:53:25 kapitan kernel: [ 2367.171581]  [<ffffffff81032399>] 
smp_apic_timer_interrupt+0x69/0xa0
Dec  2 01:53:25 kapitan kernel: [ 2367.171582]  [<ffffffff814c418a>] 
apic_timer_interrupt+0x6a/0x70
Dec  2 01:53:25 kapitan kernel: [ 2367.171583]  <EOI> 
[<ffffffffa01e02a9>] ? acpi_idle_enter_bm+0x277/0x2bb [processor]
Dec  2 01:53:25 kapitan kernel: [ 2367.171590]  [<ffffffffa01e02a2>] ? 
acpi_idle_enter_bm+0x270/0x2bb [processor]
Dec  2 01:53:25 kapitan kernel: [ 2367.171593]  [<ffffffff81383c39>] 
cpuidle_enter+0x19/0x20
Dec  2 01:53:25 kapitan kernel: [ 2367.171594]  [<ffffffff81384251>] 
cpuidle_idle_call+0xa1/0x240
Dec  2 01:53:25 kapitan kernel: [ 2367.171596]  [<ffffffff8101bfaf>] 
cpu_idle+0xaf/0x120
Dec  2 01:53:25 kapitan kernel: [ 2367.171599]  [<ffffffff81496469>] 
rest_init+0x6d/0x74
Dec  2 01:53:25 kapitan kernel: [ 2367.171601]  [<ffffffff818a5c25>] 
start_kernel+0x3b2/0x3bf
Dec  2 01:53:25 kapitan kernel: [ 2367.171602]  [<ffffffff818a5672>] ? 
repair_env_string+0x5e/0x5e
Dec  2 01:53:25 kapitan kernel: [ 2367.171604]  [<ffffffff818a5356>] 
x86_64_start_reservations+0x131/0x135
Dec  2 01:53:25 kapitan kernel: [ 2367.171605]  [<ffffffff818a545a>] 
x86_64_start_kernel+0x100/0x10f
Dec  2 01:53:25 kapitan kernel: [ 2367.171606] ---[ end trace 
5b5c97964a30946a ]---
Dec  2 01:53:25 kapitan kernel: [ 2367.171613] e1000e 0000:02:00.0: 
eth0: Reset adapter
Dec  2 01:53:28 kapitan kernel: [ 2369.666253] e1000e 0000:02:00.0: 
eth0: Error reading PHY register
Dec  2 01:53:28 kapitan kernel: [ 2369.666743] e1000e 0000:02:00.0: 
eth0: Error reading PHY register
Dec  2 01:53:28 kapitan kernel: [ 2369.667231] e1000e 0000:02:00.0: 
eth0: Error reading PHY register
Dec  2 01:53:28 kapitan kernel: [ 2369.667711] e1000e 0000:02:00.0: 
eth0: Error reading PHY register
Dec  2 01:53:28 kapitan kernel: [ 2369.668190] e1000e 0000:02:00.0: 
eth0: Error reading PHY register
Dec  2 01:53:28 kapitan kernel: [ 2369.668671] e1000e 0000:02:00.0: 
eth0: Error reading PHY register
Dec  2 01:53:28 kapitan kernel: [ 2369.669150] e1000e 0000:02:00.0: 
eth0: Error reading PHY register
Dec  2 01:53:28 kapitan kernel: [ 2369.669631] e1000e 0000:02:00.0: 
eth0: Error reading PHY register
Dec  2 01:53:31 kapitan kernel: [ 2372.659104] e1000e 0000:02:00.0: 
eth0: Error reading PHY register


Downgrade do 3.5.5 nic nie zmienia, próbowałem sterownika e1000e w 
wersji 2.1.4 ale bez zmian.
Wróciłem do kernela 3.3.7 na tym wszystko jest ok.

Ktoś spotkał się z podobnymi problemami?