Contributor
Contributor

PSOD #GP Exception 13 in world - ESXi 5.5 and BlueCoat SGOS 6.7.3.5 appliance

Reaching out to the community, as I have been unable to get a straight answer from VMWare Support, and unable to find anything related to this issue elsewhere.

I am experiencing a PSOD issue on ESXi 5.5 (Build: 7967571) platform with BlueCoat SGOS 6.7.3.5 SGW (Release: 213938) Appliance on Dell PowerEdge R630 hardware. Last thursday to friday, I experienced 4 PSOD's and had to turn off the Appliance and move it to a different cluster, with different hardware vendor. Since then, no PSOD.

The report back from VMware support recommends either turning off the appliance, or downgrading it to 6.7.1.2.

2018-04-26T13:38:31.387Z cpu5:38631)@BlueScreen: #GP Exception 13 in world 38631:vmm0:XXXXXX @ 0x4180071cde6d

2018-04-26T13:38:31.387Z cpu5:38631)Code start: 0x418007000000 VMK uptime: 0:03:59:03.288

2018-04-26T13:38:31.387Z cpu5:38631)0x41249b9dd8e8:[0x4180071cde6d]Vmxnet3VMKDevBuildPktHandles@vmkernel#nover+0x4ed stack: 0x0

2018-04-26T13:38:31.388Z cpu5:38631)0x41249b9dd9c8:[0x4180071ce7c6]Vmxnet3VMKDevPollTxQueue@vmkernel#nover+0x16a stack: 0x9b9dda48

2018-04-26T13:38:31.388Z cpu5:38631)0x41249b9dda58:[0x4180071cebfe]Vmxnet3VMKDevTQDoTx@vmkernel#nover+0x126 stack: 0x412400000000

2018-04-26T13:38:31.388Z cpu5:38631)0x41249b9ddac8:[0x4180071d2aa3]Vmxnet3VMKDev_AsyncTx@vmkernel#nover+0xa3 stack: 0x41249b9ddc48

2018-04-26T13:38:31.389Z cpu5:38631)0x41249b9ddb38:[0x4180071b1c90]NetWorldletPerVMCB@vmkernel#nover+0x218 stack: 0x0

2018-04-26T13:38:31.389Z cpu5:38631)0x41249b9ddc98:[0x4180070ec307]WorldletProcessQueue@vmkernel#nover+0xcf stack: 0x0

2018-04-26T13:38:31.389Z cpu5:38631)0x41249b9ddcd8:[0x4180070ecdcc]WorldletBHHandler@vmkernel#nover+0x54 stack: 0x4109a2057d20

2018-04-26T13:38:31.390Z cpu5:38631)0x41249b9ddd68:[0x41800702ec5f]BH_DrainAndDisableInterrupts@vmkernel#nover+0xf3 stack: 0x4109a1ff00

2018-04-26T13:38:31.390Z cpu5:38631)0x41249b9ddeb8:[0x41800725a6ea]CpuSchedDispatch@vmkernel#nover+0x1be6 stack: 0x4113d7be05c0

2018-04-26T13:38:31.390Z cpu5:38631)0x41249b9ddf28:[0x41800725b41b]CpuSchedWait@vmkernel#nover+0x237 stack: 0x412400000001

2018-04-26T13:38:31.391Z cpu5:38631)0x41249b9ddf98:[0x41800725b97b]CpuSched_VcpuHalt@vmkernel#nover+0x197 stack: 0x418000000000

2018-04-26T13:38:31.391Z cpu5:38631)0x41249b9ddfe8:[0x4180070cf3d0]VMMVMKCall_Call@vmkernel#nover+0x48c stack: 0x0

2018-04-26T13:38:31.391Z cpu5:38631)0x4180070ce9f4:[0xfffffffffc223bba]__vmk_symbol_ApeiEINJ_EndOperation@vmkernel#nover+0xf406d81a sta

2018-04-26T13:38:31.394Z cpu5:38631)base fs=0x0 gs=0x418041400000 Kgs=0x0

0 Kudos
1 Reply
Contributor
Contributor

Regardless of hardware platform, we just had another PSOD on our IBM platform, hosting a single VM, namely the SGOS Appliance.

0 Kudos