Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

ESXi host with a CD-ROM drive model DU-8A5LH can cause PSOD with vmhci_driver backtrace (67560)

Last Updated: 2/27/2024Categories: Known IssueTotal Views: 13183Language:
English

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Symptoms

ESXi Host using CD-ROM drive model DU-8A5LH  fails with PSOD referencing vmw_ahci with lines such as:

PanicvPanicInt@vmkernel#nover+0x545 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Panic_WithBacktrace@vmkernel#nover+0x56 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Heartbeat_DetectCPULockups@vmkernel#nover+0x4be xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Timer_BHHandler@vmkernel#nover+0xdc stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
BH_DrainAndDisableInterrupts@vmkernel#nover+0x7b stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
IntrCookie_VmkernelInterrupt@vmkernel#nover+0xc6 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
IDT_IntrHandler@vmkernel#nover+0x9d stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
gate_entry_@vmkernel#nover+0x0 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Power_ArchSetCState@vmkernel#nover+0x10a stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
CpuSchedIdleLoopInt@vmkernel#nover+0x39b stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
CpuSchedDispatch@vmkernel#nover+0x114a stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
CpuSchedWait@vmkernel#nover+0x27a stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
CpuSchedTimedWaitInt@vmkernel#nover+0xa8 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
CpuSched_EventQueueWaitShared@vmkernel#nover+0x2c stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
UserThread_QueueWait@(user)#<None>+0x34 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
LinuxThread_Futex@(user)#<None>+0x273 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
User_LinuxSyscallHandler@(user)#<None>+0x113 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
User_LinuxSyscallHandler@vmkernel#nover+0x1d stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
gate_entry_@vmkernel#nover+0x0 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

and

Util_FormatTimestampUTC@vmkernel#nover+0x1e stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
LogFormatStringV@vmkernel#nover+0x9c stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
LogWarningWithPcpu@vmkernel#nover+0x40f stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
vmk_vLogNoLevel@vmkernel#nover+0x63 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
vmk_LogNoLevel@vmkernel#nover+0x3e stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
CompletionBottomHalf@(vmw_ahci)#<None>+0x69b stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
HBAIntrHandler@(vmw_ahci)#<None>+0x84 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
AHCI_EdgeIntrHandler@(vmw_ahci)#<None>+0x20 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
IntrCookieBH@vmkernel#nover+0x1e0 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
BH_Check@vmkernel#nover+0xfe stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
CpuSchedDispatch@vmkernel#nover+0xed4 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
CpuSchedWait@vmkernel#nover+0x27a stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
CpuSched_NoEvqWait@vmkernel#nover+0x19 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
vmk_WorldWait@vmkernel#nover+0x65 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ExceptionHandlerWorld@(vmw_ahci)#<None>+0x9b stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
vmkWorldFunc@vmkernel#nover+0x4f stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
CpuSched_StartWorld@vmkernel#nover+0x99 stack: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

vmkernel.log entries such as:

2018-12-14T13:51:11.701Z cpu11:66006)vmw_ahci[00000017]: CompletionBottomHalf:PORT_IRQ_UNK_FIS exception.
2018-12-14T13:51:11.701Z cpu11:66006)vmw_ahci[00000017]: LogExceptionSignal:Port 7, Signal:  --|--|--|--|--|--|IR|--|--|--|--|-- (0x0040) Curr: --|--|--|--|--|--|IR|--|--|--|--|-- (0x0040)
2018-12-14T13:51:11.701Z cpu11:66006)vmw_ahci[00000017]: CompletionBottomHalf:strange irq(s), 0x10
2018-12-14T13:51:11.701Z cpu11:66006)vmw_ahci[00000017]: CompletionBottomHalf:PORT_IRQ_UNK_FIS exception.
2018-12-14T13:51:11.701Z cpu11:66006)vmw_ahci[00000017]: LogExceptionSignal:Port 7, Signal:  --|--|--|--|--|--|IR|--|--|--|--|-- (0x0040) Curr: --|--|--|--|--|--|IR|--|--|--|--|-- (0x0040)
2018-12-14T13:51:11.701Z cpu11:66006)vmw_ahci[00000017]: CompletionBottomHalf:strange irq(s), 0x10
2018-12-14T13:51:11.701Z cpu11:66006)vmw_ahci[00000017]: CompletionBottomHalf:PORT_IRQ_UNK_FIS exception.
2018-12-14T13:51:11.701Z cpu11:66006)vmw_ahci[00000017]: LogExceptionSignal:Port 7, Signal:  --|--|--|--|--|--|IR|--|--|--|--|-- (0x0040) Curr: --|--|--|--|--|--|IR|--|--|--|--|-- (0x0040)
2018-12-14T13:51:11.701Z cpu11:66006)vmw_ahci[00000017]: HBAIntrHandler:new interrupts coming, PxIS = 0x10, no repeat
2018-12-14T13:51:11.701Z cpu11:66006)vmw_ahci[00000017]: CompletionBottomHalf:strange irq(s), 0x10

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Purpose

To avoid the PSOD.

Cause

ESXi host with a CD-ROM drive model DU-8A5LH, the CD-ROM drive might report an unknown File Interchange Service (FIS) exception. The vmw_ahci driver does not handle the exception properly and creates repeated PORT_IRQ_UNK_FIS exception logs in the kernel. The repeated logs cause lack of physical CPU heartbeat

Impact / Risks

No Impact

Resolution

VMware Engineering are aware of this issue.

Workaround

Disable vmw_ahci via the following command from the ESXi cmdline:

esxcli system module set -e false -m vmw_ahci

Reboot the host

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

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 vSphere

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere 7.0.x

Take Our Survey

Support Assistant