%SYS-SP-3-CPUHOG

[halima.naboulsi]

Hello,

I had these error messages on both my Cisco 2851 and on my Cisco Catalyst 6506.

On Cisco 2851:

%SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (4/4),process = SEA write CF process.
-Traceback= 40B1DA9C 40B1DC08 40B20178 40B20084 40B409CC 40B3FE20 40B408E0 40CFE150 40CF4478 40CFF8A4 40CFFB44 40CF4FCC 40CE9670 40CE97D0 40CE8A88 40CE6FE8
%SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (16/16),process = SEA write CF process.
-Traceback= 40B1DC44 40B20178 40B20084 40B409CC 40B3FE20 40B408E0 40CFE16C 40CF4478 40CFF8A4 40CFFB44 40CF4FCC 40CE9670 40CE97D0 40CE8A88 40CE6FE8 40D029DC
%SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (16/16),process = SEA write CF process.
%SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (23/23),process = DFS flush periodic.
-Traceback= 40B1DD08 40B20178 40B20084 40B409CC 40B3FE20 40B408E0 40CFE150 40CF4478 40CFF8A4 40CFFB44 40CF4FCC 40CFB448 4088E6C0 4088E6AC
%SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (11/11),process = DFS flush periodic.

And on 6506:

Dec 27 15:20:55 MET: %SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (129/129),process = SEA write CF process.
-Traceback= 40B1DCE4 40B20178 40B20084 40B409CC 40B3FE20 40B40894 40CFE09C 40CF43A0 40D01B18 40D011FC 40CF4B4C 40CF3C2C 40CF2730 40CE8AC0 40CE7368 40D02ADC
Dec 27 15:21:15 MET: %SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (20/20),process = SEA write CF process.
-Traceback= 40B1DD08 40B20178 40B20084 40B409CC 40B3FE20 40B408E0 40CFE16C 40CF42A0 40CFF8A4 40CFFB44 40CF4EF4 40CE9670 40CE97D0 40CE8A88 40CE6FE8 40D029DC
Dec 27 15:21:17 MET: %SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (13/13),process = SEA write CF process.
-Traceback= 40B1DCE4 40B20178 40B20084 40B409CC 40B3FE20 40B408E0 40CFE150 40CF4478 40CFF8A4 40CFFB44 40CF4FCC 40CE9670 40CE97D0 40CE8A88 40CE6FE8 40D029DC
Dec 27 15:21:27 MET: %SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (29/28),process = SEA write CF process.
-Traceback= 40B2005C 40B409CC 40B3FE20 40B40894 40CFE09C 40CF43A0 40D01B18 40D011FC 40CF4B4C 40CF3C2C 40CF2730 40CE8AC0 40CE7368 40D02ADC 403EA1CC 4138DA28
Dec 27 15:21:33 MET: %SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (40/40),process = SEA write CF process.
-Traceback= 40B1DCE4 40B20178 40B20084 40B409CC 40B3FE20 40B408E0 40CFE16C 40CF42A0 40CFF8A4 40CFFB44 40CF4EF4 40CE9670 40CE97D0 40CE8A88 40CE6FE8 40D029DC
Dec 27 15:21:36 MET: %SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (11/11),process = SEA write CF process.
-Traceback= 40B1DA9C 40B1DC08 40B20178 40B20084 40B409CC 40B3FE20 40B408E0 40CFE150 40CF4478 40CFF8A4 40CFFB44 40CF4FCC 40CE9670 40CE97D0 40CE8A88 40CE6FE8
Dec 27 15:21:46 MET: %SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (30/30),process = SEA write CF process.
-Traceback= 40B1DCE4 40B20178 40B20084 40B409CC 40B3FE20 40B408E0 40CFE150 40CF42A0 40CFF8A4 40CFFB44 40CF4EF4 40CE9670 40CE97D0 40CE8A88 40CE6FE8 40D029DC
Dec 27 15:21:50 MET: %SYS-SP-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (27/27),process = SEA write CF process.
-Traceback= 40B1DA9C 40B1DC08 40B20178 40B20084 40B409CC 40B3FE20 40B408E0 40CFE150 40CF4478 40CFF8A4 40CFFB44 40CF4FCC 40CE9670 40CE97D0 40CE8A88 40CE6FE8

I have these IOs verions on my Cisco:

Cisco 2851: 15.0(1)M4

Cisco 6506: 12.2(33)SXI

Could you help please?

[Mahesh Gohil]

Hello Halima,

CU hog message is created when schedular periodically poll different process and found that some process eating cpu resources

from longer time.

This is to ensure that the system does not become unresponsive or completely lock up due to the total consumption of the CPU by any process.

In your case process:SEA write CF process is running for more than 2000msec which generates cpu hog messages

In my view you should log case with cisco with required output

Regards

Mahesh

[halima.naboulsi]

Hello Mahesh,

Thank you for your help.

I'll contact the Cisco support for more actions.

Regards,

[virtualoffis]

Did you get any further with this issue...??