IBM JS20 Hardware Maintenance Manual - Page 151

Service request number A1D-37x A1D-38x A1D-40x A24-000 A24-xxx A1D-50x SRN source G G G G G G Description A non-critical error has been detected: Clock or PLL Error. A non-critical error has been detected: Hardware Scan or Initialization Error. A non-critical error has been detected: Presence/Detect Error (Mis-Plugged). Spurious interrupts on shared interrupt level have exceeded threshold Spurious interrupts have exceeded threshold. Recoverable errors on resource indicate a trend toward an unrecoverable error. However, the resource could not be deconfigured and is still in use. The system is operating with the potential for an unrecoverable error. FRU/action 1. Check the BladeCenter management module event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 2. If no entry is found, replace the system board. 1. Check the BladeCenter management module event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 2. If no entry is found, replace the system board. 1. Check the BladeCenter management module event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 2. If no entry is found, replace the system board. 1. Check the BladeCenter management module event log. If an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 2. Replace part numbers reported by the diagnostic program. 3. If no entry is found, replace the system board. 1. heck the BladeCenter management module event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 2. Replace part numbers reported by the diagnostic program. 3. If no entry is found, replace the system board. 1. If repair is not immediately available, reboot and the resource will be deconfigured; operations can continue in a degraded mode. 2. Check the BladeCenter management module event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, "Symptom-to-FRU index," on page 93. 3. If no entry is found, replace the system board. Failing Function Codes (FFCs) Failing function codes represent functions within the system unit. Note: When replacing a FRU, use the following procedure to verify the fix: Chapter 10. Symptom-to-FRU index 141