Hi.. Follow the solution according CISCO TAC:     Problem Analysis     PID | Runtime  | Invoked | uSecs  | 5 Sec  | 1 Min   | 5 Min   | TTY | Process          |   ----|----------|---------|--------|--------|---------|---------|-----|------------------ |   07  |  1387785 |  44268  |  31349 | 31.04% |  38.93% |  43.97% |  0  | HRPC qos request    >>>>> |   89  |  25526   |  2333   |  10941 | 18.24% |  9.88%  |  4.93%  |  2  | SSH Process      |   90  |  536742  |  62298  |  8615  | 16.32% |  15.52% |  14.82% |  0  | Hulc LED Process |   88  |  225845  |  36715  |  6151  | 7.36%  |  5.66%  |  5.74%  |  0  | RedEarth Tx Mana |   87  |  145830  |  63226  |  2306  | 5.28%  |  4.30%  |  4.42%  |  0  | RedEarth I2C dri     This process is used for communication between stacked switches when programming qos entries and therefore if we have a link constantly flapping this would cause the "HRPC qos request" process to be invoked frequently leading to high cpu   --Shutting down gi4/0/5 resolved the issue   Dec  8 05:55:55.523: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/5, changed state to up Dec  8 05:55:56.933: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/5, changed state to up Dec  8 05:55:59.189: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/5, changed state to down Dec  8 05:55:59.550: %LINK-5-CHANGED: Interface FastEthernet0, changed state to administratively down Dec  8 05:56:00.145: %LINK-3-UPDOWN: Interface GigabitEthernet4/0/5, changed state to down Dec  8 05:56:03.316: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/5, changed state to up Dec  8 05:57:53.098: %SYS-1-CPURISINGTHRESHOLD: Threshold: Total CPU Utilization(Total/Intr): 94%/9%, Top 3 processes(Pid/Util):  383/24%, 214/20%, 190/20% Dec  8 05:58:18.004: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/5, changed state to down Dec  8 05:58:20.126: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/0/5, changed state to up       As a work around could you please try to shut the interface gi4/0/5 and check the improvement in CPU.   -  Gi4/0/5 was responsible for the high cpu utilization we were seeing due to the "HRPC qos request" process. This process is used for communication between stacked switches when programming qos entries and therefore if we have a link constantly flapping this would cause the "HRPC qos request" process to be invoked frequently leading to high cpu --Shutting down gi4/0/5 resolved the issue ... View more