H3C Technologies H3C MSR 5600 - Manual (Page 242)

229
Kernel threads share resources. If a kernel thread monopolizes the CPU, other threads cannot run,
resulting in a deadloop.
This feature enables the device to detect deadloops. If a thread occupies the CPU for a specific interval,
the device considers that a deadloop has occurred. It generates a deadloop message and reboots to
remove the deadloop.
To configure kernel thread deadloop detection (MSR 2600/MSR 3600):
Step Command Remarks
1. Enter system view. system-view N/A
2. Enable kernel thread
deadloop detection.
monitor kernel deadloop enable
By default, the function is
enabled.
3. (Optional.) Set the interval
for identifying a kernel
thread deadloop.
monitor kernel deadloop time interval The default is 8 seconds.
4. (Optional.) Disable kernel
thread deadloop detection
for a kernel thread.
monitor kernel deadloop exclude-thread
tid
After enabled, kernel thread
deadloop detection monitors
all kernel threads by default.
To configure kernel thread deadloop detection (MSR 5600):
Step Command Remarks
1. Enter system view. system-view N/A
2. Enable kernel thread
deadloop detection. monitor kernel deadloop enable [ slot
slot-number ] By default, the function is
enabled.
3. (Optional.) Set the interval
for identifying a kernel
thread deadloop.
monitor kernel deadloop time interval [ slot
slot-number ]
The default is 8 seconds.
4. (Optional.) Disable kernel
thread deadloop detection
for a kernel thread.
monitor kernel deadloop exclude-thread
tid [ slot slot-number ]
After enabled, kernel thread
deadloop detection monitors
all kernel threads by default.
Configuring kernel thread starvation detection
CAUTION:
Inappropriate configuration of kernel thread starvation detection can cause service problems or system
breakdown. Make sure you understand the impact of this configuration on your network before you do it.
Starvation occurs when a thread is unable to access shared resources.
Kernel thread starvation detection enables the system to detect and report thread starvation. If a thread
is not executed within a specific interval, the system considers that a starvation has occurred, and
generates a starvation message.
Thread starvation does not impact system operation. A starved thread can automatically run when
certain conditions are met.
To configure kernel thread starvation detection (MSR 2600/MSR 3600):