ESXi Host with EMC RecoverPoint Installed may PSOD (purple screen of death) during shutdown
search cancel

ESXi Host with EMC RecoverPoint Installed may PSOD (purple screen of death) during shutdown

book

Article ID: 318009

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

  • ESXi host running EMC RecoverPoint IO filter daemon may PSOD during shutdown
  • VIB Name: RP-Splitter RPESX-00.5.2.2.0.0.m.128.000 EMC_Recoverpoint 
  • Backtrace shows similar entries

2019-08-12T14:30:42.139Z cpu0:2097309)World: 3015: PRDA 0x418040000000 ss 0x0 ds 0xfd0 es 0xfd0 fs 0xfd0 gs 0xfd0
2019-08-12T14:30:42.139Z cpu0:2097309)World: 3017: TR 0xfd8 GDT 0x4509c4200000 (0xfe7) IDT 0x41801a965000 (0xfff)
2019-08-12T14:30:42.139Z cpu0:2097309)World: 3018: CR0 0x8001003d CR3 0x3f85000 CR4 0x10216c
2019-08-12T14:30:42.186Z cpu0:2097309)Backtrace for current CPU #0, worldID=2097309, fp=0x417fdabb9320
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9beb0:[0x41801a863465]FDS_CloseDevice@vmkernel#nover+0x9 stack: 0x417fdabb9320, 0x41801b73f84c, 0x4301073a5160, 0x41801b72f069, 0x43065da875b8
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9bed0:[0x41801b73f84b]FS3_RebootCleanup@esx#nover+0x7c stack: 0x43065da875b8, 0x41801a90e5ed, 0x0, 0x1, 0x3
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9bee0:[0x41801b72f068]FS3RebootHandler@esx#nover+0x5d stack: 0x0, 0x1, 0x3, 0x41801a8ed9ce, 0x43065da87070
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9bef0:[0x41801a90e5ec]Reboot_RunHandlers@vmkernel#nover+0x41 stack: 0x3, 0x41801a8ed9ce, 0x43065da87070, 0x31a6a222dd9, 0x43065da87570
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9bf10:[0x41801a8ed9cd]Init_VMKernelShutdownHelper@vmkernel#nover+0x2de stack: 0x43065da87570, 0x41801a8eb1f3, 0x43065da87088, 0x0, 0x43065da870b8
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9bf30:[0x41801a8eb1f2]HelperQueueFunc@vmkernel#nover+0x30f stack: 0x43065da870b8, 0x43065da870a8, 0x43065da870e0, 0x451a44ea3000, 0x43065da870b8
2019-08-12T14:30:42.186Z cpu0:2097309)0x451a44e9bfe0:[0x41801ab0e322]CpuSched_StartWorld@vmkernel#nover+0x77 stack: 0x0, 0x0, 0x0, 0x0, 0x0
2019-08-12T14:30:42.208Z cpu0:2097309)

VMware ESXi 6.7.0 [Releasebuild-13981272 x86_64]
2019-08-12T14:30:42.210Z cpu0:2097309)@BlueScreen: #PF Exception 14 in world 2097309:HELPER_MISC_ IP 0x41801a863465 addr 0x18PTEs:0x0;
2019-08-12T14:30:42.210Z cpu0:2097309)Code start: 0x41801a800000 VMK uptime: 0:00:28:52.427
2019-08-12T14:30:42.211Z cpu0:2097309)0x451a44e9beb0:[0x41801a863465]FDS_CloseDevice@vmkernel#nover+0x9 stack: 0x417fdabb9320
2019-08-12T14:30:42.211Z cpu0:2097309)0x451a44e9bed0:[0x41801b73f84b]FS3_RebootCleanup@esx#nover+0x7c stack: 0x43065da875b8
2019-08-12T14:30:42.211Z cpu0:2097309)0x451a44e9bee0:[0x41801b72f068]FS3RebootHandler@esx#nover+0x5d stack: 0x0
2019-08-12T14:30:42.212Z cpu0:2097309)0x451a44e9bef0:[0x41801a90e5ec]Reboot_RunHandlers@vmkernel#nover+0x41 stack: 0x3
2019-08-12T14:30:42.212Z cpu0:2097309)0x451a44e9bf10:[0x41801a8ed9cd]Init_VMKernelShutdownHelper@vmkernel#nover+0x2de stack: 0x43065da87570
2019-08-12T14:30:42.213Z cpu0:2097309)0x451a44e9bf30:[0x41801a8eb1f2]HelperQueueFunc@vmkernel#nover+0x30f stack: 0x43065da870b8
2019-08-12T14:30:42.213Z cpu0:2097309)0x451a44e9bfe0:[0x41801ab0e322]CpuSched_StartWorld@vmkernel#nover+0x77 stack: 0x0
2019-08-12T14:30:42.217Z cpu0:2097309)base fs=0x0 gs=0x418040000000 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.7

Cause

There is a race between volume open and shutdown. The volume open is triggered by an splitterThread
splitterThread should not open volumes in the shutdown path.

Resolution

This is not a VMware issue.
For further information please contact DellEMC Recover Point .