Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
ESXi host fails with a purple diagnostic screenYou see a backtrace similar to: <YYYY-MM-DD><time>Z cpu39:36948)@BlueScreen: #PF Exception 14 in world 36948:vmm0:UPEAPON IP 0x418020922744 addr 0x41ffb4cd9da0</time> <YYYY-MM-DD><time>Z cpu39:36948)Code start: 0x418020000000 VMK uptime: 11:05:11:07.817</time> callout_reset@<None>#<None>+0xd8 stack: 0x0</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151d650:[0x418020980efe]tcp_do_segment@<None>#<None>+0x52e stack: 0x410b00000000</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151d7b0:[0x418020984067]tcp_input@<None>#<None>+0xd03 stack: 0x41244151d800</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151d7c0:[0x41802092879b]netisr_dispatch@<None>#<None>+0x1b stack: 0x4136c4841a08</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151d800:[0x41802094d4a9]ether_demux@<None>#<None>+0x20d stack: 0x41244151d8af</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151d850:[0x41802094d6ff]ether_input@<None>#<None>+0x183 stack: 0x1</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151d8e0:[0x418020914d5a]TcpipRx@<None>#<None>+0x16a stack: 0xa471</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151d900:[0x41802091352b]TcpipRxDispatch@<None>#<None>+0x4b stack: 0x41097bae4d00</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151d960:[0x418020913c52]TcpipDispatch@<None>#<None>+0x1ae stack: 0x0</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151dac0:[0x4180200ec17e]WorldletProcessQueue@vmkernel#nover+0x776 stack: 0x41240000014b</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151db00:[0x4180200ec59c]WorldletBHHandler@vmkernel#nover+0x54 stack: 0x0</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151db90:[0x41802002eb3f]BH_DrainAndDisableInterrupts@vmkernel#nover+0xf3 stack: 0x0</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151dbd0:[0x418020064327]IDT_IntrHandler@vmkernel#nover+0x1af stack: 0x41244151dcf8</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151dbe0:[0x4180200f2064]gate_entry@vmkernel#nover+0x64 stack: 0x0</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151dcf8:[0x4180203a92ea]Power_HaltPCPU@vmkernel#nover+0x1fe stack: 0x0</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151dd68:[0x418020253451]CpuSchedIdleLoopInt@vmkernel#nover+0x4c5 stack: 0x410961ee8948</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151deb8:[0x4180202593e2]CpuSchedDispatch@vmkernel#nover+0x17be stack: 0x41244151df28</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151df28:[0x41802025a53b]CpuSchedWait@vmkernel#nover+0x237 stack: 0x412400000001</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151df98:[0x41802025aa9b]CpuSched_VcpuHalt@vmkernel#nover+0x197 stack: 0x418000000000</time> <YYYY-MM-DD><time>Z cpu39:36948)0x41244151dfe8:[0x4180200ced40]VMMVMKCall_Call@vmkernel#nover+0x48c stack: 0x0</time> <YYYY-MM-DD><time>Z cpu39:36948)0x4180200ce364:[0xfffffffffc223baa]__vmk_versionInfo_str@<None>#<None>+0xdb34d30a stack: 0x0</time> Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This issue occurs due to a race condition on ESXi 5.5 and 6.0 hosts when a world is trying to destroy dvfilter socket function. This may or may not cause a purple diagnostic screen to appear;
This issue is resolved in ESXi 5.5 Patch 8 (build 4179633), for more information, see VMware ESXi 5.5, Patch Release ESXi550-201608001 (2144359) ESXi 6.0 Patch 4 (build 4600944), for more information, see VMware ESXi 6.0, Patch Release ESXi600-201611401-BG (2146985)
ESXi 5.5 ホストに障害が発生して紫色の診断画面が表示され、次のエラーが報告される: tcp_input