[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] IRP_MN_SET_POWER - will do some more digging.
Okay, well regardless of discussion about the power model, we still see these occasionally, it's an open question at the moment as to whether it's the IRP handling (which you have nicely serialized), or whether pci is expecting some different ordering somewhere. I can probably find time to do some more digging. 0: 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: ffffc70d76838060, Physical Device Object of the stack Arg3: fffff80372e0b960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffc70d79580010, The blocked IRP Debugging Details: ------------------ Implicit thread is now ffffc70d`79015080 Page 17b4 not present in the dump file. Type ".hh dbgerr004" for details Page 17b4 not present in the dump file. Type ".hh dbgerr004" for details Page 500 not present in the dump file. Type ".hh dbgerr004" for details Page 500 not present in the dump file. Type ".hh dbgerr004" for details Page 500 not present in the dump file. Type ".hh dbgerr004" for details KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 2 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on CAMMARTINHARL01 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 4 Key : Analysis.Memory.CommitPeak.Mb Value: 72 Key : Analysis.System Value: CreateObject BUGCHECK_CODE: 9f BUGCHECK_P1: 3 BUGCHECK_P2: ffffc70d76838060 BUGCHECK_P3: fffff80372e0b960 BUGCHECK_P4: ffffc70d79580010 DRVPOWERSTATE_SUBCODE: 3 FAULTING_THREAD: ffffc70d79015080 ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout. IRP_ADDRESS: ffffc70d79580010 DEVICE_OBJECT: ffffc70d76838060 DRIVER_OBJECT: ffffc70d76806e60 IMAGE_NAME: pci.sys MODULE_NAME: pci FAULTING_MODULE: fffff804942c0000 pci PROCESS_NAME: System STACK_TEXT: ffffb681`79866540 fffff803`710ff46d : ffffc70d`00000000 00000000`00000001 00000000`00000004 00000000`00000004 : nt!KiSwapContext+0x76 ffffb681`79866680 fffff803`710fef0f : 00000000`00000000 fffff804`947fefd4 00000000`00000000 ffffc70d`7664b578 : nt!KiSwapThread+0x17d ffffb681`79866730 fffff803`71100ce7 : ffffc70d`00000000 00000000`00000000 ffffc70d`795801b8 00000000`00000000 : nt!KiCommitThreadWait+0x14f ffffb681`798667d0 fffff804`947ff1d5 : ffffb681`798668b0 ffffc70d`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x377 ffffb681`79866880 fffff804`947feb1b : ffffc70d`79580001 ffffffff`ee1e5d00 ffffc70d`79580010 00000000`00000003 : dxgkrnl!DpiFdoHandleDevicePower+0x1e5 ffffb681`79866910 fffff804`993fff05 : ffffc70d`76f5b030 ffffb681`79866ad9 00000000`00000000 ffffc70d`795801b8 : dxgkrnl!DpiDispatchPower+0x8b ffffb681`79866a30 fffff804`993ff3c4 : ffffc70d`76f5b030 ffffc70d`76adaa00 ffffc70d`79015080 ffffc70d`76f5b030 : nvlddmkm+0xe2ff05 ffffb681`79866b40 fffff803`711be4e2 : ffffc70d`79015080 ffffb681`79866bf0 fffff803`71391600 fffff803`71391680 : nvlddmkm+0xe2f3c4 ffffb681`79866b70 fffff803`7119c7fd : ffffffff`fa0a1f00 fffff803`711be304 ffffc70d`77a59180 00000000`0000014e : nt!PopIrpWorker+0x1de ffffb681`79866c10 fffff803`711f6e96 : fffff803`713d3180 ffffc70d`79015080 fffff803`7119c7bc 00000000`00000246 : nt!PspSystemThreadStartup+0x41 ffffb681`79866c60 00000000`00000000 : ffffb681`79867000 ffffb681`79861000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: .thread 0xffffc70d79015080 ; kb IMAGE_VERSION: 10.0.14393.4530 SYMBOL_NAME: pci!KsrGetFirmwareInformation <PERF> (pci+0x0)+0 BUCKET_ID_FUNC_OFFSET: 0 FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_DXG_POWER_IRP_TIMEOUT_pci!KsrGetFirmwareInformation__PERF__(pci+0x0) OS_VERSION: 10.0.14393.5356 BUILDLAB_STR: rs1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {53d336d3-c267-16ba-08dd-28b3916e530f} Followup: MachineOwner --------- 0: kd> .thread ffffc70d7682b040 Implicit thread is now ffffc70d`7682b040 0: kd> kv *** Stack trace for last set context - .thread/.cxr resets it # Child-SP RetAddr : Args to Child : Call Site 00 ffffb681`761bb540 fffff803`710ff46d : ffffb681`00000000 00000000`00000001 ffffb681`761bb940 00000000`00000000 : nt!KiSwapContext+0x76 01 ffffb681`761bb680 fffff803`710fef0f : ffffc70d`7682b040 ffffc70d`7682b140 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0x17d 02 ffffb681`761bb730 fffff803`710b98b6 : ffffc70d`00000000 ffffc70d`00000000 ffffb681`00000049 ffffb681`761bb8f0 : nt!KiCommitThreadWait+0x14f 03 ffffb681`761bb7d0 fffff804`942c37f7 : ffffffff`ffffffff fffff804`942c3e52 ffffc70d`00000000 fffff804`942c5d16 : nt!KeDelayExecutionThread+0x106 04 ffffb681`761bb850 fffff804`942d26b6 : 00000000`00000000 00000000`00000000 ffffffff`fffc1707 ffffc70d`79580000 : pci!PciStallForPowerChange+0x127 05 ffffb681`761bb8e0 fffff804`942d24a8 : ffffc70d`7683000b ffffc70d`768381b0 ffffc70d`79580010 fffff803`713d3180 : pci!PciSetHardwarePowerStateDispatch+0xfe 06 ffffb681`761bb940 fffff804`942d1d65 : ffffc70d`768381b0 ffffc70d`79580010 ffffc70d`76838738 ffffc70d`7682ea40 : pci!PciPowerDownDevice+0x150 07 ffffb681`761bb990 fffff804`942c633d : ffffc70d`765fac60 ffffc70d`795800e0 00000000`00000000 fffff804`93564b9f : pci!PciDevice_SetPower+0x175 08 ffffb681`761bb9f0 fffff804`9358a6e2 : ffffc70d`765fac60 00000000`00000000 ffffc70d`79580128 00790074`00690074 : pci!PciDispatchPnpPower+0xcd 09 ffffb681`761bba50 fffff804`93564416 : ffffc70d`7682ea40 00000000`00000000 ffffc70d`765fac60 00000000`00000000 : ACPI!ACPIFilterIrpSetPower+0xe2 0a ffffb681`761bbab0 fffff804`943a3458 : 00000000`00000007 ffffc70d`7683c880 00000000`00000080 00000000`00000004 : ACPI!ACPIDispatchIrp+0x2d6 0b ffffb681`761bbb30 fffff804`943a58d9 : ffffc70d`79580010 00000000`00000004 fffff804`00000004 006c0069`00000000 : xenfilt!FdoForwardIrpSynchronously+0x78 [E:\jenkins\workspace\win-xenbus_master\local\src\xenfilt\fdo.c @ 524] 0c ffffb681`761bbb90 fffff804`943a653a : ffffc70d`7664b560 00000000`00000080 fffff804`943a6520 ffffc70d`7664b560 : xenfilt!PdoDevicePower+0x109 [E:\jenkins\workspace\win-xenbus_master\local\src\xenfilt\pdo.c @ 1625] 0d ffffb681`761bbbe0 fffff803`7119c7fd : ffffc70d`7682b040 fffff804`943a6520 006e0069`00660065 00620020`00640065 : xenfilt!ThreadFunction+0x1a [E:\jenkins\workspace\win-xenbus_master\local\src\xenfilt\thread.c @ 109] 0e ffffb681`761bbc10 fffff803`711f6e96 : fffff803`713d3180 ffffc70d`7682b040 fffff803`7119c7bc 00740073`0075006d : nt!PspSystemThreadStartup+0x41 0f ffffb681`761bbc60 00000000`00000000 : ffffb681`761bc000 ffffb681`761b6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 0: kd> !irp ffffc70d79580010 Irp is active with 5 stacks 1 is current (= 0xffffc70d795800e0) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. cmd flg cl Device File Completion-Context >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e0 ffffc70d76838060 00000000 fffff8049358a710-fffff80493589a80 Success Error Cancel \Driver\pci ACPI!ACPIDeviceIrpDeviceFilterRequest Args: 00016600 00000001 00000004 00000005 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffc70d7682ea40 00000000 fffff804943a1cd0-ffffb681761bbb60 Success Error Cancel pending \Driver\ACPI xenfilt!DriverQueryCompletion Args: 00016600 00000001 00000004 00000005 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffc70d7683c9b0 00000000 fffff8049472f0c0-ffffb681798668b0 Success Error Cancel pending \Driver\xenfilt dxgkrnl!DpiFdoPowerCompletionRoutine Args: 00016600 00000001 00000004 00000005 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffc70d76f5b030 00000000 fffff803711bdd20-ffffc70d78cd62a0 Success Error Cancel pending \Driver\nvlddmkm nt!PopRequestCompletion Args: 00016600 00000001 00000004 00000005 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-ffffc70d78cd62a0 Args: 00000000 00000000 00000000 00000000
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |