ffhelllskjdje Posted January 16, 2018 Share Posted January 16, 2018 Woke up this morning to a call trace error. Any ideas what this could be? Hopefully it's just a one off. Jan 15 17:44:50 Tower kernel: Call Trace: Jan 15 17:44:50 Tower kernel: <IRQ> Jan 15 17:44:50 Tower kernel: ? qdisc_rcu_free+0x39/0x39 Jan 15 17:44:50 Tower kernel: ? qdisc_rcu_free+0x39/0x39 Jan 15 17:44:50 Tower kernel: call_timer_fn.isra.4+0x11/0x6d Jan 15 17:44:50 Tower kernel: expire_timers+0x82/0x95 Jan 15 17:44:50 Tower kernel: run_timer_softirq+0x62/0xe5 Jan 15 17:44:50 Tower kernel: ? tick_sched_timer+0x33/0x61 Jan 15 17:44:50 Tower kernel: ? __hrtimer_run_queues+0x85/0xc5 Jan 15 17:44:50 Tower kernel: ? ktime_get+0x37/0x8a Jan 15 17:44:50 Tower kernel: __do_softirq+0xc7/0x1bc Jan 15 17:44:50 Tower kernel: irq_exit+0x4f/0x8e Jan 15 17:44:50 Tower kernel: smp_apic_timer_interrupt+0x6e/0x79 Jan 15 17:44:50 Tower kernel: apic_timer_interrupt+0x98/0xa0 Jan 15 17:44:50 Tower kernel: </IRQ> tower-diagnostics-20180116-0641.zip Link to comment
JorgeB Posted January 16, 2018 Share Posted January 16, 2018 It's NIC related: Jan 15 17:44:50 Tower kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Looks to be mostly harmlessness, unless you notice any LAN issues. Link to comment
ffhelllskjdje Posted January 16, 2018 Author Share Posted January 16, 2018 Cool. No didn't notice anything Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.