Because disabled routines do not take interrupts, a disabled loop is not visible in the system trace output. Normally, a disabled loop results in a spin loop in a multiprocessor environment.

If disabled loops persist, they can result in a system outage. Therefore, you are typically working with a stand-alone dump. When analyzing a stand-alone dump for a disabled loop, use the stored status data to determine the module involved in the loop.