Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

"LINT1 motherboard interrupt" error in an ESX/ESXi host (1804)

Last Updated: 1/22/2021Categories: TroubleshootingTotal Views: 156453Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglishGerman

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Details

ESXi/ESX hosts are unstable and may fail with a purple diagnostic screens citing an NMI, Non-Maskable, or LINT1 Interrupt.

The console displays an entry similar to:

LINT1/NMI (motherboard nonmaskable interrupt), undiagnosed. This may be a hardware problem; please contact your hardware vendor.

You may experience a purple screen when passing through a device to a virtual machine and when reviewing the vmkernel core dump, you see these events:

WARNING: IOMMUIntel: 2211: IOMMU Unit # 0: R/W = 1, Device 007:00.0 Faulting PA = 0xdf63e000 Fault Reason = 6

Note: NMI log entries appear in the /var/log/vmkernel.log file, on the console, or in the VMkernel core dump file if the condition triggers a VMkernel purple diagnostic screen.

Solution

An NMI is a physical hardware event. It is typically the result of a non-recoverable condition (in the context of continued operation during that specific boot cycle) that the system BIOS and/or management chipset encounters.

NMI events

NMI events are routed by the CPU through the Advanced Programmable Interrupt Controller (APIC) to the operating system (in this case, the ESXi host) through the operating system kernel (in this case, the VMkernel).

An NMI event occurs due to hardware issues such as:

A PCI bus error, typically caused by a misbehaving I/O device or an electrical glitch.

A bad memory module or processor.

Severe thermal cycling of a critical component, usually after an extended downtime or a cooling component failure.

Components running out-of-specification, such as an over-voltage or under-voltage condition due to hardware fault involving a voltage regulator module.

Unapproved or incompatible components, such as an active memory backplane whose design revision is too early for the chassis.

A firmware, BIOS or other component mismatch. For example, such as option-card of revision X requiring a minimum option-card firmware revision Y and a minimum chassis BIOS revision Z.

On some systems, the CPU IOMMU feature that is used to map the DMA memory for a device from the host operating system to the guest operating system is configured by firmware to raise an NMI when it encounters an error, instead of allowing the operating system to catch and diagnose the error.  IOMMU errors are typically caused by misbehaving I/O device drivers or firmware.

If you experience an NMI event:

Identify the virtual machines (if any) were powered on at the time of the NMI event.

Check if powering on a specific virtual machine trigger an NMI event.

Reseat the PCI cards and/or move them to different slots.

To resolve the NMI event, contact the hardware vendor and provide these data:

Timeframe that the event happened.

At least 10 minutes of logs leading up to the event.

Chassis diagnostics log output and management chipset log output.

Chassis vital product data.

A copy of the vm-support output.

The relevant VMware Service Request number, if opened.

Notes:

Chassis management chipsets often function as an intelligent handler for chassis faults and can capture significant amounts of information during an NMI event.

The IBM xSeries chassis includes a BIOS option of Reboot on System NMI. When enabled, this results in an immediate chassis-reboot rather than a chassis-halt. In this event the ESXi host logs do not mention the NMI. Other enterprise hardware vendors may offer a similar BIOS option.

Related Information

For translated versions of this article, see:

VMware Skyline Health Diagnostics for vSphere - FAQ

Español: Identificar y abordar eventos de interrupciones no enmascarables en un host ESX/ESXi (2073165)

Português: Identificando e resolvendo eventos de interrupção não mascarável em um host ESX/ESXi (2130004)

日本語: ESX/ESXi ホスト上でマスク不可能割り込みイベントを特定および処理する (2076746)

简体中文: 确定并解决 ESX/ESXi 主机上的不可屏蔽中断事件 (2077552)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglishGerman

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
VMkernel ログで次のメッセージが表示される：長い VMFS3 rsv 時間 (1025299)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

VMware ESX Server

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX Server 2.5.x

VMware ESX Server 2.1.x

VMware ESX Server 2.0.x

VMware ESX Server 1.x

VMware ESX Server 1.x

VMware ESX Server 1.5.x

VMware ESX Server 1.5.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant