VMware Cloud Community
Bhuvaneshjyothi
Contributor
Contributor
Jump to solution

Backtrace for current CPU

Hi Team,

ESXi host halts and displays a purple diagnostic screen with PF Exception 14. Please see the below details. Could you please help me to trace out this issue?

2018-09-26T15:08:17.668Z cpu15:37062)World: 8773: PRDA 0x418043c00000 ss 0x4018 ds 0x4018 es 0x4018 fs 0x0 gs 0x0

2018-09-26T15:08:17.668Z cpu15:37062)World: 8775: TR 0x4000 GDT 0xfffffffffc013000 (0xffff) IDT 0xfffffffffc043000 (0xffff)

2018-09-26T15:08:17.668Z cpu15:37062)World: 8776: CR0 0x80010033 CR3 0x128808000 CR4 0x42660

2018-09-26T15:08:17.718Z cpu15:37062)Backtrace for current CPU #15, worldID=37062, ebp=0x4123c319d4c8

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319d4c8:[0x41802ba10c57]E1000PollRxRing@vmkernel#nover+0xb73 stack: 0x3f4cdf9b089cc0, 0x4111

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319d538:[0x41802ba13bb5]E1000DevRx@vmkernel#nover+0x3a9 stack: 0x4123c319d578, 0x4108d797100

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319d5d8:[0x41802b992164]IOChain_Resume@vmkernel#nover+0x174 stack: 0x434cdf, 0x4123c67e7000,

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319d628:[0x41802b979e22]PortOutput@vmkernel#nover+0x136 stack: 0x4108d781f780, 0x4108d797150

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319d688:[0x41802bf24f58]EtherswitchForwardLeafPortsQuick@<None>#<None>+0x4c stack: 0x3600000

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319d8a8:[0x41802bf25f51]EtherswitchPortDispatch@<None>#<None>+0xe25 stack: 0x412300000013, 0

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319d918:[0x41802b97a7d2]Port_InputResume@vmkernel#nover+0x192 stack: 0x41084013ef80, 0x4108d

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319d968:[0x41802b97ba39]Port_Input_Committed@vmkernel#nover+0x25 stack: 0x12b82e254, 0x4123c

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319d9f8:[0x41802b9cad25]Vmxnet3VMKDevTQDoTx@vmkernel#nover+0x28d stack: 0xf00000000, 0x0, 0x

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319da68:[0x41802b9cec13]Vmxnet3VMKDev_AsyncTx@vmkernel#nover+0xa3 stack: 0x4123c319dbe8, 0x4

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319dad8:[0x41802b9add70]NetWorldletPerVMCB@vmkernel#nover+0x218 stack: 0x417feb8ee090, 0x412

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319dc38:[0x41802b8eae77]WorldletProcessQueue@vmkernel#nover+0xcf stack: 0x4123c319dc78, 0x20

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319dc78:[0x41802b8eb93c]WorldletBHHandler@vmkernel#nover+0x54 stack: 0x181bf4fb2f334, 0x417f

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319dce8:[0x41802b82e5b9]BH_Check@vmkernel#nover+0xc9 stack: 0xac1800, 0x4100067a4000, 0x200a

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319dd58:[0x41802ba4e72d]CpuSchedIdleLoopInt@vmkernel#nover+0x391 stack: 0x400000002, 0x0, 0x

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319deb8:[0x41802ba54930]CpuSchedDispatch@vmkernel#nover+0x1630 stack: 0x4123c319df28, 0x4123

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319df28:[0x41802ba55c65]CpuSchedWait@vmkernel#nover+0x245 stack: 0x1, 0x90c6, 0x412300002001

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319df98:[0x41802ba561cb]CpuSched_VcpuHalt@vmkernel#nover+0x197 stack: 0x418000000000, 0x4100

2018-09-26T15:08:17.718Z cpu15:37062)0x4123c319dfe8:[0x41802b8cde30]VMMVMKCall_Call@vmkernel#nover+0x48c stack: 0x0, 0x0, 0x0, 0x0, 0x0

2018-09-26T15:08:17.718Z cpu15:37062)0x41802b8cd484:[0xfffffffffc223baa]__vmk_symbol_NFSVolume_GetLocalPath@com.vmware.nfsmod#1.0.0.0+0x

2018-09-26T15:08:17.740Z cpu15:37062) [45m [33;1mVMware ESXi 5.5.0 [Releasebuild-1331820 x86_64] [0m

#PF Exception 14 in world 37062:vmm5:XX-AAA IP 0x41802ba10c57 addr 0x0

Reply
0 Kudos
1 Solution

Accepted Solutions
bluefirestorm
Champion
Champion
Jump to solution

Have a look at this https://kb.vmware.com/kb/2079094 and it looks like a known problem that has been resolved with later patches/releases of ESXi 5.5.

View solution in original post

3 Replies
bluefirestorm
Champion
Champion
Jump to solution

Have a look at this https://kb.vmware.com/kb/2079094 and it looks like a known problem that has been resolved with later patches/releases of ESXi 5.5.

Bhuvaneshjyothi
Contributor
Contributor
Jump to solution

Hi,

We use VMXNET3 virtual adapter for most of the VMs and still, we are facing the PSOD issue. That means I need to update the ESXi 5.5 with the latest patch.

I think the below-mentioned version might help me to get the issue resolved.

VMware vSphere 5: Private Cloud Computing, Server and Data Center Virtualization

Description Cisco Custom Image for ESXi 5.5.0 U3 GA

Version 5.5 U3

Documentation: Blade Servers Rack Servers E-Series Blades Support Matrix

Release Date 2018-09-21

Reply
0 Kudos
RajeevVCP4
Expert
Expert
Jump to solution

Your current build is ESXi 5.5 GA

You required upgrade it by ESXi 5.5 Patch 2 ( 1892794)

Please follow this KB

VMware Knowledge Base

VMware Knowledge Base

Rajeev Chauhan
VCIX-DCV6.5/VSAN/VXRAIL
Please mark help full or correct if my answer is use full for you
Reply
0 Kudos