ESXi host fails with PSOD after upgrading to 6.5
search cancel

ESXi host fails with PSOD after upgrading to 6.5

book

Article ID: 317944

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • After upgrading to ESXi 6.5, the host experiences a PSOD.
  • The ESXi host is using a 10GB NIC.
  • You see a backtrace similar to:

    YYYY-MM-DDZ cpu6:65645)@BlueScreen: #PF Exception 14 in world 65645:HELPER_UPLIN IP 0x41802c496258 addr 0x0
    PTEs:0x292379a027;0x2efe54c027;0xbfffffffff001;
    YYYY-MM-DDZ cpu6:65645)Code start: 0x41802c200000 VMK uptime: 4:02:26:10.151
    YYYY-MM-DDZ cpu6:65645)0x4390c369bd00:[0x41802c496258]UplinkTreePackQueueFilters@vmkernel#nover+0x188 stack: 0xe15427000
    YYYY-MM-DDZ cpu6:65645)0x4390c369bd90:[0x41802c49e142]UplinkLB_LoadBalanceCB@vmkernel#nover+0x1e42 stack: 0x1
    YYYY-MM-DDZ cpu6:65645)0x4390c369bf20:[0x41802c4916f2]UplinkAsyncProcessCallsHelperCB@vmkernel#nover+0x116 stack: 0x43048761eac0
    YYYY-MM-DDZ cpu6:65645)0x4390c369bf50:[0x41802c2c9e0d]helpFunc@vmkernel#nover+0x3c5 stack: 0x4300b9b2a050
    YYYY-MM-DDZ cpu6:65645)0x4390c369bfe0:[0x41802c4c91b5]CpuSched_StartWorld@vmkernel#nover+0x99 stack: 0x0
    2YYYY-MM-DDZ cpu6:65645)base fs=0x0 gs=0x418041800000 Kgs=0x0

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


Environment

VMware vSphere ESXi 6.5

Cause

This issue occurs because the Netqueue commit phase abruptly stops due to a failure of hardware activation of a Rx queue. As a result, the Internal data structure of the Netqueue layer's could go out of sync causing a host PSOD.

Resolution

This issue is resolved in VMware ESXi 6.5 P02 (ESXi-6.5.0-20171204001-standard), available at VMware Downloads. 

To workaround this issue if you do not want to upgrade, perform one of these options:



Powered by Wolken Software