Reset Search
 

 

Article

WS-C5210: Controller Crashed, then got into a hung state which required a manual reset

« Go Back

Information

 
TitleWS-C5210: Controller Crashed, then got into a hung state which required a manual reset
Symptoms
  • WS-C5210: Controller Crashed, then got into a hung state which required a manual reset
01/13/19 14:49:05   Critical    Startup Manager                 Initiating Reboot.  Cause: System Health Mon. Thread Not Running.
01/13/19 14:44:04   Critical    Startup Manager                 Initiating Reboot.  Cause: MU Session Manager Not Responding.
  • Error message seen prior to the reboot is:
    kernel: INFO: rcu_sched self-detected stall on CPU
Environment
  • ExtremeWireless
  • 5210 
  • Firmware 10.41.13 or below
  • CPU Stalls
Cause
CPU gets stuck in a deep loop.
Resolution
Resolved in firmware 10.41.14 or higher
Additional notes
Release Note: wns0021598 - Incorporated changes to flow handler robustness to improve AP and Controller stability.

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255