e1000e_cyclecounter_read NIC causing kernel panics

Issue

• System panic with hardlockup while waiting for value from Hardware (Ethernet card) in module e1000e at "e1000e_cyclecounter_read+0x1d/0xd0 [e1000e] "

------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x26b/0x280() (Not tainted)                  <<<<<<<<<<<<<<<<<<
Hardware name: FWA-3210
NETDEV WATCHDOG: eth1 (e1000e): transmit queue 0 timed out
Modules linked in: autofs4 sunrpc ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ftp ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 ipmi_si ipmi_msghandler sg microcode serio_raw iTCO_wdt iTCO_vendor_support e1000e ptp pps_core i2c_i801 lpc_ich mfd_core shpchp ext4 jbd2 mbcache sd_mod crc_t10dif ahci i915 drm_kms_helper drm i2c_algo_bit i2c_core video output dm_mirror dm_region_hash dm_log dm_mod [last unloaded: speedstep_lib]
Pid: 0, comm: swapper Not tainted 2.6.32-573.7.1.el6.x86_64 #1
Call Trace:
 <IRQ>  [<ffffffff81077461>] ? warn_slowpath_common+0x91/0xe0
 [<ffffffff81077566>] ? warn_slowpath_fmt+0x46/0x60
 [<ffffffff8148cbbb>] ? dev_watchdog+0x26b/0x280
 [<ffffffff81089815>] ? internal_add_timer+0xb5/0x110
 [<ffffffff8148c950>] ? dev_watchdog+0x0/0x280
 [<ffffffff8108a4a7>] ? run_timer_softirq+0x197/0x340
 [<ffffffff8103574d>] ? lapic_next_event+0x1d/0x30
 [<ffffffff8107ffa1>] ? __do_softirq+0xc1/0x1e0
 [<ffffffff810b2e4f>] ? tick_program_event+0x2f/0x40
 [<ffffffff8100c38c>] ? call_softirq+0x1c/0x30
 [<ffffffff8100fbd5>] ? do_softirq+0x65/0xa0
 [<ffffffff8107fe55>] ? irq_exit+0x85/0x90
 [<ffffffff8154279a>] ? smp_apic_timer_interrupt+0x4a/0x60
 [<ffffffff8100bc13>] ? apic_timer_interrupt+0x13/0x20
 <EOI>  [<ffffffff812f109e>] ? intel_idle+0xfe/0x1b0
 [<ffffffff812f1081>] ? intel_idle+0xe1/0x1b0
 [<ffffffff8143376a>] ? cpuidle_idle_call+0x7a/0xe0
 [<ffffffff81009fe6>] ? cpu_idle+0xb6/0x110
 [<ffffffff81531b22>] ? start_secondary+0x2c0/0x316
---[ end trace 66ef4356c1f6acd6 ]---
e1000e 0000:02:00.0: eth1: Reset adapter unexpectedly                        <<<<<<<<<<<<<<<<<<
e1000e 0000:02:00.0: eth1: Timesync Rx Control register not set as expected  <<<<<<<<<<<<<<<<<<
Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 1           <<<<<<<<<<<<<<<<<<
Pid: 20, comm: events/1 Tainted: G        W  -- ------------    2.6.32-573.7.1.el6.x86_64 #1
Call Trace:
 <NMI>  [<ffffffff81537e44>] ? panic+0xa7/0x16f
 [<ffffffff810149c9>] ? sched_clock+0x9/0x10
 [<ffffffff810ed45d>] ? watchdog_overflow_callback+0xcd/0xd0
 [<ffffffff81123fd7>] ? __perf_event_overflow+0xa7/0x240
 [<ffffffff8101dc54>] ? x86_perf_event_set_period+0xf4/0x180
 [<ffffffff81124624>] ? perf_event_overflow+0x14/0x20
 [<ffffffff81024a02>] ? intel_pmu_handle_irq+0x202/0x3f0
 [<ffffffff8153d149>] ? perf_event_nmi_handler+0x39/0xb0
 [<ffffffff8153ec05>] ? notifier_call_chain+0x55/0x80
 [<ffffffff8153ec6a>] ? atomic_notifier_call_chain+0x1a/0x20
 [<ffffffff810a783e>] ? notify_die+0x2e/0x30
 [<ffffffff8153c8c3>] ? do_nmi+0x1c3/0x350
 [<ffffffff8153c180>] ? nmi+0x20/0x30
 [<ffffffffa02af35d>] ? e1000e_cyclecounter_read+0x1d/0xd0 [e1000e]     
 <<EOE>>  [<ffffffff810ae2f9>] ? timecounter_read+0x19/0x50
 [<ffffffffa02ba00a>] ? e1000e_phc_gettime+0x4a/0xa0 [e1000e]
 [<ffffffffa02b9ea0>] ? e1000e_systim_overflow_work+0x0/0xa0 [e1000e]
 [<ffffffffa02b9ed0>] ? e1000e_systim_overflow_work+0x30/0xa0 [e1000e]
 [<ffffffff8109b80b>] ? schedule_delayed_work+0x1b/0x20
 [<ffffffff8109a780>] ? worker_thread+0x170/0x2a0
 [<ffffffff810a1460>] ? autoremove_wake_function+0x0/0x40
 [<ffffffff8109a610>] ? worker_thread+0x0/0x2a0
 [<ffffffff810a0fce>] ? kthread+0x9e/0xc0
 [<ffffffff8100c28a>] ? child_rip+0xa/0x20
 [<ffffffff810a0f30>] ? kthread+0x0/0xc0
 [<ffffffff8100c280>] ? child_rip+0x0/0x20