Hi,
We are testing volume driver on a Windows 2012 R2 hosted as VM on ESX host. These are HCK tests because the OS is Windows 2012 R2.
The DF - Concurrent Hardware And Operating System (CHAOS) Test (Reliability) test is failing to give a crash dump that involves LSI_SAS.sys driver. Following is the output in WinDGB. Kindly advise how to get around this issue. Do the virtual machines need to be created using Para Virtual Driver (PVSCSI)? Any help is highly appreciated.
Thanks,
WinCPP
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000fe8f7060, Physical Device Object of the stack
Arg3: ffffd00141b731e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffcf8102034dc0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: lsi_sas.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5154810a
MODULE_NAME: lsi_sas
FAULTING_MODULE: fffff800e7e00000 lsi_sas
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
DPC_STACK_BASE: FFFFD00141B7BFB0
STACK_TEXT:
ffffd001`41b731a8 fffff802`fc20645e : 00000000`0000009f 00000000`00000003 ffffe000`fe8f7060 ffffd001`41b731e0 : nt!KeBugCheckEx
ffffd001`41b731b0 fffff802`fc20637e : ffffe000`ffd15cd0 ffffe001`00300880 ffffe000`ffd15d00 ffffe000`00000001 : nt!PopIrpWatchdogBugcheck+0xde
ffffd001`41b73210 fffff802`fc042a18 : 00000000`00000000 ffffd001`41b73360 ffffe000`ffd15d10 ffffd001`41b40180 : nt!PopIrpWatchdog+0x32
ffffd001`41b73260 fffff802`fc1561da : ffffd001`41b40180 ffffd001`41b40180 ffffd001`41b50380 ffffe000`ffa07080 : nt!KiRetireDpcList+0x4f8
ffffd001`41b734e0 00000000`00000000 : ffffd001`41b74000 ffffd001`41b6d000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_VRF_3_POWER_DOWN_disk_IMAGE_lsi_sas.sys
BUCKET_ID: 0x9F_VRF_3_POWER_DOWN_disk_IMAGE_lsi_sas.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_vrf_3_power_down_disk_image_lsi_sas.sys
FAILURE_ID_HASH: {a59dc375-a60a-a8cf-a2d0-406324e79da0}
Followup: MachineOwner
---------
1: kd> !devstack ffffe000fe8f7060
!DevObj !DrvObj !DevExt ObjectName
ffffe000feb78040 \Driver\partmgr ffffe000feb78190
ffffe000feb77560 \Driver\disk ffffe000feb776b0 DR0
> ffffe000fe8f7060 \Driver\LSI_SAS ffffe000fe8f71b0 0000002e
!DevNode ffffe000fe8f7910 :
DeviceInst is "SCSI\Disk&Ven_VMware&Prod_Virtual_disk\5&1982005&0&000000"
ServiceName is "disk"