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

On any HPE server running VMware ESXi 6.0 U3, VMware ESXi 6.5 or VMware ESXi 6.7 and configured with any of the HPE Broadcom-Based network adapters with bnxtnet driver version 212.0.119.0 (or prior) may experience a PSOD. (76441)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 12984Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

ESXi hosts running on HPE Custom Image 6.0 U3; 6.5 and 6.7 with below network card models and configured with any of the following HPE Broadcom-Based network adapters with bnxtnet driver version 212.0.119.0 (or prior) may experience a PSOD when high random I/O traffic is experienced:

HPE Ethernet 10/25Gb 2-port 631FLR-SFP28 Adapter
HPE Ethernet 10/25Gb 2-port 631SFP28 Adapter
HPE Ethernet 10Gb 2-port 535T Adapter
HPE Ethernet 10Gb 2-port 535FLR-T Adapter

The PSOD backtrace will have similar entries as below

2018-12-06T14:41:28.012Z cpu7:2271232)@BlueScreen: #PF Exception 14 in world 2271232:vmkload_mod IP 0x418010952f01 addr 0x4313f20de5c4
PTEs:0x2040079023;0x0;
2018-12-06T14:41:28.012Z cpu7:2271232)Code start: 0x418010800000 VMK uptime: 0:15:14:58.979
2018-12-06T14:41:28.013Z cpu7:2271232)0x451aabe9b420:[0x418010952f01]DLM_free@vmkernel#nover+0x115 stack: 0x4309f20de5d0
2018-12-06T14:41:28.013Z cpu7:2271232)0x451aabe9b440:[0x418010950630]Heap_Free@vmkernel#nover+0x115 stack: 0x1
2018-12-06T14:41:28.014Z cpu7:2271232)0x451aabe9b490:[0x4180111e015e][email-masked]#1+0x5b stack: 0x4cd74307c77a8257
2018-12-06T14:41:28.015Z cpu7:2271232)0x451aabe9b4b0:[0x4180111d4173][email-masked]#1+0x108 stack: 0x1
2018-12-06T14:41:28.015Z cpu7:2271232)0x451aabe9b510:[0x41801082d296]Driver_QuiesceDevice@vmkernel#nover+0x63 stack: 0x41801082d291
2018-12-06T14:41:28.016Z cpu7:2271232)0x451aabe9b550:[0x4180108287ec]DeviceQuiesce@vmkernel#nover+0xed stack: 0x418010828854
2018-12-06T14:41:28.016Z cpu7:2271232)0x451aabe9b580:[0x41801082a2ad]DeviceTreeWalk@vmkernel#nover+0x106 stack: 0x41801082896a
2018-12-06T14:41:28.016Z cpu7:2271232)0x451aabe9b5e0:[0x41801082af1b]Device_ModuleUnload@vmkernel#nover+0x174 stack: 0x4307c77be9e0
2018-12-06T14:41:28.017Z cpu7:2271232)0x451aabe9b640:[0x4180109058fc]Mod_Unload@vmkernel#nover+0x59 stack: 0x1700000000
2018-12-06T14:41:28.017Z cpu7:2271232)0x451aabe9b6b0:[0x418010fa5144]UW64VMKSyscallUnpackModUnload@(user)#<None>+0x41 stack: 0x418010b2bf7a
2018-12-06T14:41:28.018Z cpu7:2271232)0x451aabe9bed0:[0x418010f3b660]User_UWVMK64SyscallHandler@(user)#<None>+0x249 stack: 0x0
2018-12-06T14:41:28.018Z cpu7:2271232)0x451aabe9bf30:[0x41801095f648]SyscallUWVMK64@vmkernel#nover+0x90 stack: 0x0
2018-12-06T14:41:28.018Z cpu7:2271232)0x451aabe9bf38:[0x418010960066]gate_entry@vmkernel#nover+0x67 stack: 0x0
2018-12-06T14:41:28.021Z cpu7:2271232)base fs=0x0 gs=0x418041c00000 Kgs=0x0

The NIC driver and firmware versions that caused the issue

Firmware Version: 212.0.102.
bnxtnet driver Version: 212.0.119.0

Note:The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment.
Disclaimer:VMware is not responsible for the reliability of any data,opinions,advice or statements made on third-party websites.Inclusion of such links does not imply that VMware endorses,recommends or accepts any responsibility for the content of such sites

Cause

This PSOD is seen when high random I/O traffic is experienced on the reported NIC cards.

Impact / Risks

It requires reboot of ESXi hosts after installing the driver.

Resolution

To fix and prevent this issue, download and install for ESXi 6.0 and ESXi 6.5 bnxtnet version 214.0.190.0  and for ESXi 6.7 bnxtnet version 214.0.195.0 available as below

For VMware vSphere ESXi 6.0, go to Customer Connect Downloads

For VMware vSphere ESXi 6.5, go to Customer Connect Downloads

For VMware vSphere ESXi 6.7, go to Customer Connect Downloads

For steps to install the driver refer to VMware KB : How to download and install async drivers in ESXi 5.x/6.x

For more information refer to HPE Customer Advisory

Workaround

No  workaround  available to avoid this issue.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
Application Remote Collector が再起動後、7.5 から 8.0 に自動的にアップグレードされる (76412)

KB
•
Application Remote Collector 在重新引导后自动从 7.5 升级到 8.0 (76412)

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

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.x

Take Our Survey

Support Assistant