cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 

X460-G2-10GE4...Epm application wdg timer warning - 50 sec, kepc 0xffffffff805f9d24(__cond_resched+0x20/0x44) uepc 0x2abcc

X460-G2-10GE4...Epm application wdg timer warning - 50 sec, kepc 0xffffffff805f9d24(__cond_resched+0x20/0x44) uepc 0x2abcc

Rod_Robertson2
Contributor
At this time eaps appears to have stopped working and placed a possible loop on the network ( 2 things happened at the same ) open to discussion what caused what !!!

Recently seen , when saving on X460-G2-10GE4...Epm application wdg timer warning - 50 sec, kepc 0xffffffff805f9d24(__cond_resched+0x20/0x44) uepc 0x2abcce48. CPU 0: soft watchdog expiration warning EPC ffffffff80600704(_spin_lock+0xc/0x38) at 2 seconds.

Epm application wdg timer warning - 50 sec, kepc 0xffffffff805f9d24(__cond_resched+0x20/0x44) uepc 0x2abcce48.CPU 0: soft watchdog expiration warning EPC ffffffff80600704(_spin_lock+0xc/0x38) at 2 seconds.
CPU 0: Kernel thread was stuck for 3.01 seconds, jiffies: 5736315018
Epm application wdg timer warning - 63 sec, kepc 0xffffffff805f9d24(__cond_resched+0x20/0x44) uepc 0x2abcce48.
CPU 1: soft watchdog expiration warning EPC ffffffff80600704(_spin_lock+0xc/0x38) at 2 seconds.
CPU 1: Kernel thread was stuck for 4.16 seconds, jiffies: 5736315322
CPU 0: soft watchdog expiration warning EPC ffffffff8032d34c(try_to_free_pages+0x26c/0x350) at 3 seconds.
CPU 1: soft watchdog expiration warning EPC ffffffff803d9714(nfs_access_cache_shrinker+0x54/0x2c8) at 2 seconds.
CPU 1: Kernel thread was stuck for 3.48 seconds, jiffies: 5736315867
CPU 0: soft watchdog expiration warning EPC ffffffff803d9820(nfs_access_cache_shrinker+0x160/0x2c8) at 8 seconds.
CPU 0: Kernel thread was stuck for 9.95 seconds, jiffies: 5736316020
Epm application wdg timer warning - 73 sec, kepc 0xffffffff805f9d24(__cond_resched+0x20/0x44) uepc 0x2abcce48.
CPU 1: soft watchdog expiration warning EPC ffffffff8032b404(shrink_slab+0x184/0x200) at 3 seconds.
CPU 0: soft watchdog expiration warning EPC ffffffff806007f0(_spin_unlock_irqrestore+0x30/0x38) at 2 seconds.
CPU 0: Kernel thread was stuck for 3.23 seconds, jiffies: 5736316521
CPU 1: soft watchdog expiration warning EPC ffffffff803590d0(shrink_dcache_memory+0x10/0x2e8) at 8 seconds.
CPU 1: Kernel thread was stuck for 8.97 seconds, jiffies: 5736316771
CPU 0: soft watchdog expiration warning EPC ffffffff8035d7ec(shrink_icache_memory+0xc/0x348) at 3 seconds.
CPU 0: Kernel thread was stuck for 5.81 seconds, jiffies: 5736317109
Epm application wdg timer warning - 84 sec, kepc 0xffffffff805f9d24(__cond_resched+0x20/0x44) uepc 0x2abcce48.
CPU 1: soft watchdog expiration warning EPC ffffffff8032b400(shrink_slab+0x180/0x200) at 2 seconds.
CPU 0: soft watchdog expiration warning EPC ffffffff8032b2f4(shrink_slab+0x74/0x200) at 3 seconds.
CPU 0: Kernel thread was stuck for 3.89 seconds, jiffies: 5736317505
CPU 1: Kernel thread was stuck for 5.01 seconds, jiffies: 5736317523
CPU 0: Kernel thread was stuck for 3.84 seconds, jiffies: 5736317896
Epm application wdg timer warning - 94 sec, kepc 0xffffffff805f9d24(__cond_resched+0x20/0x44) uepc 0x2abcce48.
^C

Plus a number of the same

Any thoughts ?

Rebooted the stack , sorted the issue, loop removed from network.

2 REPLIES 2

Rod_Robertson2
Contributor
There was a loop on the network as I had not added the control vlan ports !! šŸ™‚
The system is up and working , so I will monitor it for the time being..

Karthik_Mohando
Extreme Employee
Hi Rod, I would suggest to open up a case with GTAC for further investigation. With the below logs and information. "show tech" "show log messages nvram" Syslogs if available for the two days prior to the instance. Any other logs collected during the issue like "top" "show cpu-monitoring" Was there a change in the configuration before the loop. Does the loop issue got resolved after a save and reboot? Or there was a physical loop in the network which was removed after the stack reboot?
GTM-P2G8KFN