Call Traces have been found

Hi Everyone,

Happy unRAID user for a few months now and today i got a message about a call trace on my server. Looking through the logs i found the following. Any interprtation?

Mar  6 17:17:29 Tower kernel: ------------[ cut here ]------------
Mar  6 17:17:29 Tower kernel: WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:316 dev_watchdog+0x181/0x1dc
Mar  6 17:17:29 Tower kernel: NETDEV WATCHDOG: eth0 (igb): transmit queue 2 timed out
Mar  6 17:17:29 Tower kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod nct6775 hwmon_vid bonding igb ptp pps_core i2c_algo_bit x86_pkg_temp_thermal coretemp kvm_intel i2c_i801 i2c_smbus ahci i2c_core kvm libahci video backlight [last unloaded: md_mod]
Mar  6 17:17:29 Tower kernel: CPU: 4 PID: 0 Comm: swapper/4 Not tainted 4.9.10-unRAID #1
Mar  6 17:17:29 Tower kernel: Hardware name: ASUSTeK COMPUTER INC. P10S-M WS Series/P10S-M WS Series, BIOS 3105 12/15/2016
Mar  6 17:17:29 Tower kernel: ffff88087fd03db0 ffffffff813a353e ffff88087fd03e00 ffffffff819a9b99
Mar  6 17:17:29 Tower kernel: ffff88087fd03df0 ffffffff8104d00c 0000013c7fd03e68 ffff880857c20000
Mar  6 17:17:29 Tower kernel: ffff8808574798c0 ffff880857c203a0 0000000000000004 0000000000000008
Mar  6 17:17:29 Tower kernel: Call Trace:
Mar  6 17:17:29 Tower kernel: <IRQ> 
Mar  6 17:17:29 Tower kernel: [<ffffffff813a353e>] dump_stack+0x61/0x7e
Mar  6 17:17:29 Tower kernel: [<ffffffff8104d00c>] __warn+0xb8/0xd3
Mar  6 17:17:29 Tower kernel: [<ffffffff8104d06d>] warn_slowpath_fmt+0x46/0x4e
Mar  6 17:17:29 Tower kernel: [<ffffffff815a6434>] dev_watchdog+0x181/0x1dc
Mar  6 17:17:29 Tower kernel: [<ffffffff815a62b3>] ? qdisc_rcu_free+0x39/0x39
Mar  6 17:17:29 Tower kernel: [<ffffffff815a62b3>] ? qdisc_rcu_free+0x39/0x39
Mar  6 17:17:29 Tower kernel: [<ffffffff81090b9c>] call_timer_fn.isra.5+0x17/0x6b
Mar  6 17:17:29 Tower kernel: [<ffffffff81090c75>] expire_timers+0x85/0x98
Mar  6 17:17:29 Tower kernel: [<ffffffff81090d75>] run_timer_softirq+0x69/0x8f
Mar  6 17:17:29 Tower kernel: [<ffffffff810363ab>] ? lapic_next_deadline+0x21/0x27
Mar  6 17:17:29 Tower kernel: [<ffffffff8109b217>] ? clockevents_program_event+0xd0/0xe8
Mar  6 17:17:29 Tower kernel: [<ffffffff81050e8a>] __do_softirq+0xbb/0x1af
Mar  6 17:17:29 Tower kernel: [<ffffffff8105112e>] irq_exit+0x53/0x94
Mar  6 17:17:29 Tower kernel: [<ffffffff81036d99>] smp_trace_apic_timer_interrupt+0x7b/0x88
Mar  6 17:17:29 Tower kernel: [<ffffffff81036daf>] smp_apic_timer_interrupt+0x9/0xb
Mar  6 17:17:29 Tower kernel: [<ffffffff8167def2>] apic_timer_interrupt+0x82/0x90
Mar  6 17:17:29 Tower kernel: <EOI> 
Mar  6 17:17:29 Tower kernel: [<ffffffff81551541>] ? cpuidle_enter_state+0xfe/0x156
Mar  6 17:17:29 Tower kernel: [<ffffffff815515bb>] cpuidle_enter+0x12/0x14
Mar  6 17:17:29 Tower kernel: [<ffffffff8107c415>] call_cpuidle+0x33/0x35
Mar  6 17:17:29 Tower kernel: [<ffffffff8107c5f7>] cpu_startup_entry+0x13a/0x1b2
Mar  6 17:17:29 Tower kernel: [<ffffffff81035402>] start_secondary+0xf5/0xf8
Mar  6 17:17:29 Tower kernel: ---[ end trace 8e3003a199ca1cdc ]---

Attached are the diagnostics.

Thanks!

tower-diagnostics-20170312-0931.zip

Edited March 12, 20179 yr by draggonguy
diagnostics attached