Help with CPUHOG event caused by UDLD

[Mahomed Hussein]

Hi

I wonder if anyone could please provide me with some help/direction on troubleshooting the following event.

Mar  3 20:43:42.900 GMT: %SYS-SP-3-CPUHOG: Task is running for (32)msecs, more than (28)msecs (33/32),process = UDLD Pseudo Preemption Process.
-Traceback= 40F3120C 409ECFB0 409EF3E0 409EF4B4 40ED3BA4 40A0CEB0 40A0CE9C

This event came up on one of our 6509E chassis last night. UDLD has been running fine and there don't appear to be any other errors or events related to it around that time. UDLD has been running fine on this device for more than 6 months (at least) without this error coming up.

I understand that the log entry is telling me that the process ran for more than 28msecs. What I'm trying to understand/find out is whether this was caused by something else and whether it could cause any problems. The last thing we want is for this to incorrectly shutdown one of our 10G ports.

The device is running IOS 15.1(2)SY (ADVIPSERVICES).

I'm not sure what other information is required in order to help me with this question, so please ask if there's any other info I can provide and I'll do my best to provide it.

Thanks in advance for any assistance.

[invermaesolutions2010]

Hello,

I have this problem in a 6509-E chassis with SUP720-3BXL too.

Feb 26 07:58:50 6509-e 1018: *Feb 26 05:59:13.871: %SYS-SPSTBY-3-CPUHOG: Task is running for (52)msecs, more than (28)msecs (26/25),process = UDLD Pseudo Preemption Process.
Feb 26 07:58:51 6509-e 1019: -Traceback= 417C62A0 417C63D0 408EDBAC 40CA4CA4 408A4328 408A4314

My ios version is:

Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXI14, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Thu 04-Sep-14 00:37 by prod_rel_team

Thanks

[Mark Malone]

Hi

Looks like hitting an issue , tracebacks indicate a problem usually in software and Cisco uses these codes with the developers to identify the issues exactly

There not available to the public , you can upgrade to try and see if it fixes it or open a case with TAC and see exactly what the traceback is

: -Traceback= 417C62A0 417C63D0 408EDBAC 40CA4CA4