hope someone will have time to look at this..  maybe advise what can be the issue..

 

Nov 5 00:45:16 Tower kernel: Call Trace:

Nov 5 00:45:16 Tower kernel: <IRQ>

Nov 5 00:45:16 Tower kernel: ? qdisc_rcu_free+0x39/0x39

Nov 5 00:45:16 Tower kernel: call_timer_fn.isra.4+0x14/0x70

Nov 5 00:45:16 Tower kernel: expire_timers+0x83/0x92

Nov 5 00:45:16 Tower kernel: run_timer_softirq+0x62/0xf7

Nov 5 00:45:16 Tower kernel: ? __do_softirq+0x65/0x1c2

Nov 5 00:45:16 Tower kernel: __do_softirq+0xcd/0x1c2

Nov 5 00:45:16 Tower kernel: irq_exit+0x4f/0x8e

Nov 5 00:45:16 Tower kernel: smp_apic_timer_interrupt+0x7a/0x85

Nov 5 00:45:16 Tower kernel: apic_timer_interrupt+0x7d/0x90

Nov 5 00:45:16 Tower kernel: </IRQ>

Nov 5 00:45:16 Tower kernel: RIP: 0010:cpuidle_enter_state+0xe0/0x135

Nov 5 00:45:16 Tower kernel: RSP: 0018:ffffffff81c03ec8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff10

Nov 5 00:45:16 Tower kernel: RAX: ffff88085fa20840 RBX: 0000000000000000 RCX: 000000000000001f

Nov 5 00:45:16 Tower kernel: RDX: 00006b6bb88b4881 RSI: 0000000000020040 RDI: 0000000000000000

Nov 5 00:45:16 Tower kernel: RBP: ffff88085fa28900 R08: 000117664783f882 R09: 0000000000000048

Nov 5 00:45:16 Tower kernel: R10: ffffffff81c03ea8 R11: 00000000000024d8 R12: 0000000000000002

Nov 5 00:45:16 Tower kernel: R13: 00006b6bb88b4881 R14: ffffffff81c56558 R15: 00006b6bb8344626

Nov 5 00:45:16 Tower kernel: ? cpuidle_enter_state+0xbb/0x135

Nov 5 00:45:16 Tower kernel: do_idle+0x11a/0x179

Nov 5 00:45:16 Tower kernel: cpu_startup_entry+0x18/0x1a

Nov 5 00:45:16 Tower kernel: start_kernel+0x3dc/0x3e4

Nov 5 00:45:16 Tower kernel: secondary_startup_64+0xa5/0xb0

Nov 5 00:45:16 Tower kernel: Code: 3d 33 43 7c 00 00 75 36 48 89 df c6 05 27 43 7c 00 01 e8 23 2e fe ff 89 e9 48 89 de 48 c7 c7 fd 72 b8 81 48 89 c2 e8 ec 86 ba ff <0f> 0b eb 0f ff c5 48 81 c2 40 01 00 00 39 cd 75 9c eb 13 48 8b

Nov 5 00:45:16 Tower kernel: ---[ end trace 6dc730056491aa6b ]---

tower-diagnostics-20181107-1950.zip

It looks as though one of your NICs suffered a glitch, was reset and continued where it left off. Interestingly it's an Intel one, not the usual suspect (Realtek). Incidentally, the syslog snippet you posted was completely useless. The event that caused the call trace happened a couple of dozen lines earlier:

Nov  5 00:45:16 Tower kernel: NETDEV WATCHDOG: eth0 (igb): transmit queue 4 timed out
Nov  5 00:45:16 Tower kernel: ------------[ cut here ]------------
Nov  5 00:45:16 Tower kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:320 dev_watchdog+0x158/0x1ba