After Update to SLE10 SP2/SP3, an NMI is received on servers with ServerEngines "Pilot 2" graphics adapter
This document (7000420) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 10 Service Pack 2
SUSE Linux Enterprise Server 10 Service Pack 3
Hardware:
Intel based server with ServerEngines "Pilot 2" graphics adapter, for example: Fujitsu Siemens Computers PRIMERGY RX/TX200S4, RX/TX300S4
SUSE Linux Enterprise Server 10 Service Pack 3
Hardware:
Intel based server with ServerEngines "Pilot 2" graphics adapter, for example: Fujitsu Siemens Computers PRIMERGY RX/TX200S4, RX/TX300S4
Situation
After installation of (or update to) SLES10 SP2/SP3, an NMI is received. This can have several visible consequences:
1. System Global Error LED blinks red (on PRIMERGY systems)
2. System Event Log entry "BIOS fatal NMI" (on PRIMERGY systems)
3. Error message in /var/log/messages:
Uhhuh. NMI received. Dazed and confused, but trying to continue
You probably have a hardware problem with your RAM chips
In certain situations, a system freeze may occur later.
1. System Global Error LED blinks red (on PRIMERGY systems)
2. System Event Log entry "BIOS fatal NMI" (on PRIMERGY systems)
3. Error message in /var/log/messages:
Uhhuh. NMI received. Dazed and confused, but trying to continue
You probably have a hardware problem with your RAM chips
In certain situations, a system freeze may occur later.
Resolution
For SLES 10 SP2: After installation/update to SP2, immediately update the kernel again to version 2.6.16.60-0.23 or higher, and add the kernel boot parameter "aerdriver.off=1" in /boot/grub/menu.lst.
The aerdriver kernel parameter is only available after installing the update kernel. The original SP2 kernel will not recognize the option.
For SLES 10 SP3: Similar to the solution mentioned above, add the kernel boot parameter "aerdriver.off=1" in /boot/grub/menu.lst.
The aerdriver kernel parameter is only available after installing the update kernel. The original SP2 kernel will not recognize the option.
For SLES 10 SP3: Similar to the solution mentioned above, add the kernel boot parameter "aerdriver.off=1" in /boot/grub/menu.lst.
Additional Information
Background
Depending on the selected video mode (text or graphics), different memory pages of the VGA Video RAM (0xa0000 - 0xbffff) are active. Accesses to inactive pages of the Video RAM can cause a PCI-Express Error on the Pilot 2 graphics adapter. These errors are non-fatal and used not to be reported in earlier SLES10 releases.
SLES10 SP2 is the first Linux Enterprise distribution that introduces the "PCI Express Advanced Error Reporting" (AER) feature. This causes the PCI-Express error from the VGA chip to be reported to the chip set, and ultimately causes the NMI.
The resolution above disables AER, reverting back to the behavior of SLES10 SP1.
Depending on the selected video mode (text or graphics), different memory pages of the VGA Video RAM (0xa0000 - 0xbffff) are active. Accesses to inactive pages of the Video RAM can cause a PCI-Express Error on the Pilot 2 graphics adapter. These errors are non-fatal and used not to be reported in earlier SLES10 releases.
SLES10 SP2 is the first Linux Enterprise distribution that introduces the "PCI Express Advanced Error Reporting" (AER) feature. This causes the PCI-Express error from the VGA chip to be reported to the chip set, and ultimately causes the NMI.
The resolution above disables AER, reverting back to the behavior of SLES10 SP1.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7000420
- Creation Date: 19-May-2008
- Modified Date:03-Mar-2020
-
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Real Time Extension
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
