Article ID: 000026932 Content Type: Error Messages Last Reviewed: 07/08/2021

Nodes Crash with "Critical Interrupt Chipset Err"

Environment

Rack Scale Design Direct

osindependent

BUILT IN - ARTICLE INTRO SECOND COMPONENT
Summary

Check with ParTec before contacting your computer manufacturer.

Description

Various Knights Landing (KNL) nodes crashed showing 'Critical Interrupt Chipset Err' in the SEL.

The following is a log example:

{{{
2 | 12/10/2017 | 21:45:35 | Critical Interrupt Chipset Err | PCI PERR (PCI PERR |PCI bus:00 device:05 function:2) | Asserted
3 | 12/10/2017 | 21:45:35 | Unknown Err Reg Pointer | | Asserted
4 | 12/10/2017 | 21:45:35 | Unknown Err Reg Pointer | | Asserted
5 | 12/10/2017 | 21:45:35 | Critical Interrupt Chipset Err | PCI PERR (PCI PERR |PCI bus:00 device:05 function:0) | Asserted
6 | 12/10/2017 | 21:45:35 | Unknown Err Reg Pointer | | Asserted
}}}

 

Resolution

Check on the following before contacting your computer manufacturer:

  1. Was the BIOS - Basic Input/Output System (BIOS) updated to the latest version?
  2. Was System Event Log (SEL) cleared and the node power-cycled?
  3. Was the node rebooted and checked?

Contact Support with the system event log* for diagnosis should you need further assistance.

* Related Topic: How to Extract and Read the System Event Log (SEL) for Intel® Server Boards
 

Related Products

This article applies to 1 products