EvtDeviceArmWakeFromSx not called
in [Device Drivers]
|
Prev: How to send IOCTLs to a filter driver KB uses wrong mutex?
Next: Is WDK's sample Ramdisk a Filter driver?
From: rsdn on 8 Dec 2006 15:17 Thanks, from wdflogdump 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner TRACE_FORMAT_SEARCH_PATH= wdftrace: searchpath is: wdftrace: gTracePrefix: "" wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- TMF file used for formatting IFR log is: C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf\wdf01001.tmf Log at 86073000 Gather log: Please wait, this may take a moment (reading 4032 bytes). % read so far ... 10, 20, 100 There are 22 log entries --- start of log --- 1: FxDeviceInitAPI_cpp5 -- PowerPolicyEventCallbacks size -2042877768 is invalid, expected 28 2: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State WdfDevStatePnpInit from WdfDevStatePnpObjectCreated 3: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State WdfDevStatePnpInitStarting from WdfDevStatePnpInit 4: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting 5: FxIoTarget_cpp995 -- ignoring WDFIOTARGET 79DF5CF8 state, sending WDFREQUEST F7A2A7A0, state 1 6: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy state WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated 7: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state FxIdleStarted from FxIdleStopped 8: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated 9: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State WdfDevStatePowerD0Starting from WdfDevStatePowerStartingCheckDeviceType 10: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting 11: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State WdfDevStatePowerD0StartingDmaEnable from WdfDevStatePowerD0StartingConnectInterrupt 12: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State WdfDevStatePowerD0StartingStartSelfManagedIo from WdfDevStatePowerD0StartingDmaEnable 13: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state FxIdleStartedPowerUp from FxIdleStarted 14: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state FxIdleDisabled from FxIdleStartedPowerUp 15: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State WdfDevStatePowerDecideD0State from WdfDevStatePowerD0StartingStartSelfManagedIo 16: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State 17: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy state WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarting 18: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy state WdfDevStatePwrPolStartingDecideS0Wake from WdfDevStatePwrPolStartingSucceeded 19: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy state WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake 20: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state FxIdleDisabled from FxIdleDisabled 21: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable 22: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces ---- end of log ---- Regards Sumithra "Doron Holan [MS]" wrote: > for KMDF 1.1 you need to use !wdftmffile , see > http://blogs.msdn.com/doronh/archive/2006/07/31/684531.aspx > > d > > -- > Please do not send e-mail directly to this alias. this alias is for > newsgroup purposes only. > This posting is provided "AS IS" with no warranties, and confers no rights. > > > "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > news:E79DD4A0-2C17-4DCF-820A-E2575B301AA2(a)microsoft.com... > > Thanks. I got the following from wdflogdump > > > > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner > > TRACE_FORMAT_SEARCH_PATH= > > wdftrace: searchpath is: C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf > > > > wdftrace: gTracePrefix: "" > > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " > > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- > > Log at 85dc2000 > > Gather log: Please wait, this may take a moment (reading 4032 bytes). > > % read so far ... 10, 20, 100 > > There are 22 log entries > > --- start of log --- > > Unknown( 16): GUID=cbb7aabc-8282-c8df-ba62-9bfc713cd1e0 (No Format > > Information found). > > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format > > Information found). > > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format > > Information found). > > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format > > Information found). > > Unknown( 20): GUID=80086f8b-6b01-45ac-dd58-6ef38233e4de (No Format > > Information found). > > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format > > Information found). > > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format > > Information found). > > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > > Information found). > > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > > Information found). > > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > > Information found). > > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > > Information found). > > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > > Information found). > > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format > > Information found). > > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format > > Information found). > > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > > Information found). > > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > > Information found). > > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format > > Information found). > > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format > > Information found). > > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format > > Information found). > > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format > > Information found). > > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format > > Information found). > > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format > > Information found). > > > > Regards > > Sumithra > > > > "Doron Holan [MS]" wrote: > > > >> you need to fix your symbols path so that KMDF is in it. for KMDF v1.1, > >> it > >> is in the tree where you installed KMDF , > >> %ddkroot%\WDF\KMDF10\symbols\x86fre\wdf > >> > >> d > >> > >> -- > >> Please do not send e-mail directly to this alias. this alias is for > >> newsgroup purposes only. > >> This posting is provided "AS IS" with no warranties, and confers no > >> rights. > >> > >> > >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > >> news:F4ED721E-C1A5-464D-92E9-F81F1CFBB284(a)microsoft.com... > >> > wdfkd.wdflogdump returns > >> > > >> > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner > >> > TRACE_FORMAT_SEARCH_PATH= > >> > wdftrace: searchpath is: C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf > >> > > >> > wdftrace: gTracePrefix: "" > >> > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " > >> > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- > >> > error: Could not retrieve WDF IFR log header for driver eepromburner. > >> > hint: Build your driver with newer WDF libraries. > >> > > >> > I am using build tools from Windows DDK 3790.1830. What am I missing? > >> > > >> > Regards > >> > Sumithra > >> > > >> > > >> > "Doron Holan [MS]" wrote: > >> > > >> >> !wdfkd.wdflogdump > >> >> > >> >> -- > >> >> Please do not send e-mail directly to this alias. this alias is for > >> >> newsgroup purposes only. > >> >> This posting is provided "AS IS" with no warranties, and confers no > >> >> rights. > >> >> > >> >> > >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > >> >> news:D17A7CB6-A95E-40B2-8478-DE7519139E36(a)microsoft.com... > >> >> > OS is Windows XP SP2. I have a USB mouse as well on the bus. I could > >> >> > not > >> >> > get > >> >> > a dumo on wdflogdump. The error returned is > >> >> > > >> >> > 0: kd> !wdflogdump > >> >> > No export wdflogdump found. > >> >> > > >> >> > What version of WinDbg should I be running? > >> >> > > >> >> > Thanks for your help. > >> >> > > >> >> > Regards > >> >> > Sumithra > >> >> > > >> >> > "Doron Holan [MS]" wrote: > >> >> > > >> >> >> what OS? for usb SS to work, all devices on the controller must > >> >> >> say > >> >> >> they > >> >> >> are SS ready. is your device the only one on the bus? what does > >> >> >> !wdflogdump say? > >> >> >> > >> >> >> d > >> >> >> > >> >> >> -- > >> >> >> Please do not send e-mail directly to this alias. this alias is for > >> >> >> newsgroup purposes only. > >> >> >> This posting is provided "AS IS" with no warranties, and confers no > >> >> >> rights. > >> >> >> > >> >> >> > >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > >> >> >> news:5C23E9EA-3B0F-4014-AE0F-E9F451EAA404(a)microsoft.com... > >> >> >> > There are 4 UHCI controllers and 1 EHCI controller. All of them > >> >> >> > report > >> >> >> > > >> >> >> > PDCAP_D0_SUPPORTED > >> >> >> > PDCAP_D3_SUPPORTED > >> >> >> > PDCAP_WAKE_FROM_D3_SUPPORTED > >> >> >> > > >> >> >> > I can still wake the system from a USB mouse and PS/2 keyboard. I > >> >> >> > think > >> >> >> > the > >> >> >> > USB mouse will not be able to wake up the system if the HC is not > >> >> >> > able > >> >> >> > to > >> >> >> > wake up from all Sx states. > >> >> >> > > >> >> >> > Regards > >> >> >> > Sumithra > >> >> >> > > >> >> >> > Regards > >> >> >> > Sumithra > >> >> >> > > >> >> >> > "Doron Holan [MS]" wrote: > >> >> >> > > >> >> >> >> in xp sp2 and later, open up the properties of the HC and your > >> >> >> >> device > >> >> >> >> and > >> >> >> >> look at the details tab. select the power caps from the list. > >> >> >> >> > >> >> >> >> d > >> >> >> >> > >> >> >> >> -- > >> >> >> >> Please do not send e-mail directly to this alias. this alias is > >> >> >> >> for > >> >> >> >> newsgroup purposes only. > >> >> >> >> This posting is provided "AS IS" with no warranties, and confers > >> >> >> >> no > >> >> >> >> rights. > >> >> >> >> > >> >> >> >> > >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > >> >> >> >> news:7D161F1C-1AEF-44B5-BE85-BF7FAF33FBE0(a)microsoft.com... > >> >> >> >> > Yes I did call WdfDeviceAssignSxWakeSettings to enable wake > >> >> >> >> > from > >> >> >> >> > Sx > >> >> >> >> > and > >> >> >> >> > also > >> >> >> >> > use WdfDeviceAssignS0IdleSettings with 10s timeout. How do I > >> >> >> >> > determine > >> >> >> >> > that > >> >> >> >> > the host controller is capable of waking from all Sx states. I > >> >> >> >> > can > >> >> >> >> > wake > >> >> >> >> > the > >> >> >> >> > system with other PS2 keyboard, mouse as well as a USB mouse. > >> >> >> >> > > >> >> >> >> > Regards > >> >> >> >> > Sumithra > >> >> >> >> > > >> >> >> >> > "Doron Holan [MS]" wrote: > >> >> >> >> > > >> >> >> >> >> did you call WdfDeviceAssignSxWakeSettings to enable wake > >> >> >> >> >> from > >> >> >> >> >> Sx? > >> >> >> >> >> Did > >> >> >> >> >> you > >> >> >> >> >> call WdfDeviceAssignS0IdleSettings to idle out while in S0? > >> >> >> >> >> If > >> >> >> >> >> so, > >> >> >> >> >> is > >> >> >> >> >> your > >> >> >> >> >> host controller capable of waking from all Sx states? > >> >> >> >> >> > >> >> >> >> >> d > >> >> >> >> >> > >> >> >> >> >> -- > >> >> >> >> >> Please do not send e-mail directly to this alias. this alias > >> >> >> >> >> is > >> >> >> >> >> for > >> >> >> >> >> newsgroup purposes only. > >> >> >> >> >> This posting is provided "AS IS" with no warranties, and > >> >> >> >> >> confers > >> >> >> >> >> no > >> >> >> >> >> rights. > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > >> >> >> >> >> news:86451B29-1267-4032-A370-77A4CABECEBF(a)microsoft.com... > >> >> >> >> >> > Hi > >> >> >> >> >> > > >> >> >> >> >> > I am writing a KMDF driver for a USB device that is remote > >> >> >> >> >> > wakeup > >> >> >> >> >> > capable. > >> >> >> >> >> > But EvtDeviceArmWakeFromSx is never called when I go to > >> >> >> >> >> > standby. > >> >> >> >> >> > I > >> >> >> >> >> > have > >> >> >> >> >> > registered > >> >> >> >> >> > > >> >> >> >> >> > EvtDeviceArmWakeFromS0, EvtDeviceDisarmWakeFromS0 , > >> >> >> >> >> > EvtDeviceWakeFromS0Triggered, EvtDeviceArmWakeFromSx > >> >> >> >> >> > ,EvtDeviceDisarmWakeFromSx , EvtDeviceWakeFromSxTriggered > >> >> >> >> >> > > >> >> >> >> >> > Also another thing I noticed is I see the power management > >> >> >> >> >> > tab > >> >> >> >> >> > in > >> >> >> >> >> > the > >> >> >> >> >> > Device > >> >> >> >> >> > Manager, but there are no registry entries created to > >> >> >> >> >> > reflect > >> >> >> >> >> > this. > >> >> >> >> >> > > >> >> >> >> >> > What should I do to get EvtDeviceArmWakeFromSx called? > >> >> >> >> >> > > >> >> >> >> >> > Regards > >> >> >> >> >> > Sumithra > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> > >> >> > >> >> > >> > >> > >> > > >
From: Doron Holan [MS] on 8 Dec 2006 23:14 ok, send the log right after you do a Sx->S0 transition and EvtDeviceArmWakeFromSx is not called d -- Please do not send e-mail directly to this alias. this alias is for newsgroup purposes only. This posting is provided "AS IS" with no warranties, and confers no rights. "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message news:572818BE-D4F7-46C1-83F6-751C5269D27C(a)microsoft.com... > Thanks, from wdflogdump > > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner > TRACE_FORMAT_SEARCH_PATH= > wdftrace: searchpath is: > > wdftrace: gTracePrefix: "" > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- > TMF file used for formatting IFR log is: > C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf\wdf01001.tmf > Log at 86073000 > Gather log: Please wait, this may take a moment (reading 4032 bytes). > % read so far ... 10, 20, 100 > There are 22 log entries > --- start of log --- > 1: FxDeviceInitAPI_cpp5 -- PowerPolicyEventCallbacks size -2042877768 is > invalid, expected 28 > 2: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State > WdfDevStatePnpInit from WdfDevStatePnpObjectCreated > 3: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State > WdfDevStatePnpInitStarting from WdfDevStatePnpInit > 4: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State > WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting > 5: FxIoTarget_cpp995 -- ignoring WDFIOTARGET 79DF5CF8 state, sending > WDFREQUEST F7A2A7A0, state 1 > 6: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy state > WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated > 7: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state > FxIdleStarted from FxIdleStopped > 8: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated > 9: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > WdfDevStatePowerD0Starting from WdfDevStatePowerStartingCheckDeviceType > 10: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting > 11: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > WdfDevStatePowerD0StartingDmaEnable from > WdfDevStatePowerD0StartingConnectInterrupt > 12: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > WdfDevStatePowerD0StartingStartSelfManagedIo from > WdfDevStatePowerD0StartingDmaEnable > 13: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state > FxIdleStartedPowerUp from FxIdleStarted > 14: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state > FxIdleDisabled from FxIdleStartedPowerUp > 15: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > WdfDevStatePowerDecideD0State from > WdfDevStatePowerD0StartingStartSelfManagedIo > 16: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State > 17: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy state > WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarting > 18: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy state > WdfDevStatePwrPolStartingDecideS0Wake from > WdfDevStatePwrPolStartingSucceeded > 19: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy state > WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake > 20: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state > FxIdleDisabled from FxIdleDisabled > 21: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State > WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable > 22: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State > WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces > ---- end of log ---- > > Regards > Sumithra > > > "Doron Holan [MS]" wrote: > >> for KMDF 1.1 you need to use !wdftmffile , see >> http://blogs.msdn.com/doronh/archive/2006/07/31/684531.aspx >> >> d >> >> -- >> Please do not send e-mail directly to this alias. this alias is for >> newsgroup purposes only. >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message >> news:E79DD4A0-2C17-4DCF-820A-E2575B301AA2(a)microsoft.com... >> > Thanks. I got the following from wdflogdump >> > >> > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner >> > TRACE_FORMAT_SEARCH_PATH= >> > wdftrace: searchpath is: C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf >> > >> > wdftrace: gTracePrefix: "" >> > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " >> > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- >> > Log at 85dc2000 >> > Gather log: Please wait, this may take a moment (reading 4032 bytes). >> > % read so far ... 10, 20, 100 >> > There are 22 log entries >> > --- start of log --- >> > Unknown( 16): GUID=cbb7aabc-8282-c8df-ba62-9bfc713cd1e0 (No Format >> > Information found). >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format >> > Information found). >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format >> > Information found). >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format >> > Information found). >> > Unknown( 20): GUID=80086f8b-6b01-45ac-dd58-6ef38233e4de (No Format >> > Information found). >> > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format >> > Information found). >> > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format >> > Information found). >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> > Information found). >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> > Information found). >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> > Information found). >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> > Information found). >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> > Information found). >> > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format >> > Information found). >> > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format >> > Information found). >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> > Information found). >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> > Information found). >> > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format >> > Information found). >> > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format >> > Information found). >> > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format >> > Information found). >> > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format >> > Information found). >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format >> > Information found). >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format >> > Information found). >> > >> > Regards >> > Sumithra >> > >> > "Doron Holan [MS]" wrote: >> > >> >> you need to fix your symbols path so that KMDF is in it. for KMDF >> >> v1.1, >> >> it >> >> is in the tree where you installed KMDF , >> >> %ddkroot%\WDF\KMDF10\symbols\x86fre\wdf >> >> >> >> d >> >> >> >> -- >> >> Please do not send e-mail directly to this alias. this alias is for >> >> newsgroup purposes only. >> >> This posting is provided "AS IS" with no warranties, and confers no >> >> rights. >> >> >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message >> >> news:F4ED721E-C1A5-464D-92E9-F81F1CFBB284(a)microsoft.com... >> >> > wdfkd.wdflogdump returns >> >> > >> >> > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner >> >> > TRACE_FORMAT_SEARCH_PATH= >> >> > wdftrace: searchpath is: C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf >> >> > >> >> > wdftrace: gTracePrefix: "" >> >> > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " >> >> > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- >> >> > error: Could not retrieve WDF IFR log header for driver >> >> > eepromburner. >> >> > hint: Build your driver with newer WDF libraries. >> >> > >> >> > I am using build tools from Windows DDK 3790.1830. What am I >> >> > missing? >> >> > >> >> > Regards >> >> > Sumithra >> >> > >> >> > >> >> > "Doron Holan [MS]" wrote: >> >> > >> >> >> !wdfkd.wdflogdump >> >> >> >> >> >> -- >> >> >> Please do not send e-mail directly to this alias. this alias is for >> >> >> newsgroup purposes only. >> >> >> This posting is provided "AS IS" with no warranties, and confers no >> >> >> rights. >> >> >> >> >> >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message >> >> >> news:D17A7CB6-A95E-40B2-8478-DE7519139E36(a)microsoft.com... >> >> >> > OS is Windows XP SP2. I have a USB mouse as well on the bus. I >> >> >> > could >> >> >> > not >> >> >> > get >> >> >> > a dumo on wdflogdump. The error returned is >> >> >> > >> >> >> > 0: kd> !wdflogdump >> >> >> > No export wdflogdump found. >> >> >> > >> >> >> > What version of WinDbg should I be running? >> >> >> > >> >> >> > Thanks for your help. >> >> >> > >> >> >> > Regards >> >> >> > Sumithra >> >> >> > >> >> >> > "Doron Holan [MS]" wrote: >> >> >> > >> >> >> >> what OS? for usb SS to work, all devices on the controller must >> >> >> >> say >> >> >> >> they >> >> >> >> are SS ready. is your device the only one on the bus? what >> >> >> >> does >> >> >> >> !wdflogdump say? >> >> >> >> >> >> >> >> d >> >> >> >> >> >> >> >> -- >> >> >> >> Please do not send e-mail directly to this alias. this alias is >> >> >> >> for >> >> >> >> newsgroup purposes only. >> >> >> >> This posting is provided "AS IS" with no warranties, and confers >> >> >> >> no >> >> >> >> rights. >> >> >> >> >> >> >> >> >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message >> >> >> >> news:5C23E9EA-3B0F-4014-AE0F-E9F451EAA404(a)microsoft.com... >> >> >> >> > There are 4 UHCI controllers and 1 EHCI controller. All of >> >> >> >> > them >> >> >> >> > report >> >> >> >> > >> >> >> >> > PDCAP_D0_SUPPORTED >> >> >> >> > PDCAP_D3_SUPPORTED >> >> >> >> > PDCAP_WAKE_FROM_D3_SUPPORTED >> >> >> >> > >> >> >> >> > I can still wake the system from a USB mouse and PS/2 >> >> >> >> > keyboard. I >> >> >> >> > think >> >> >> >> > the >> >> >> >> > USB mouse will not be able to wake up the system if the HC is >> >> >> >> > not >> >> >> >> > able >> >> >> >> > to >> >> >> >> > wake up from all Sx states. >> >> >> >> > >> >> >> >> > Regards >> >> >> >> > Sumithra >> >> >> >> > >> >> >> >> > Regards >> >> >> >> > Sumithra >> >> >> >> > >> >> >> >> > "Doron Holan [MS]" wrote: >> >> >> >> > >> >> >> >> >> in xp sp2 and later, open up the properties of the HC and >> >> >> >> >> your >> >> >> >> >> device >> >> >> >> >> and >> >> >> >> >> look at the details tab. select the power caps from the list. >> >> >> >> >> >> >> >> >> >> d >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> Please do not send e-mail directly to this alias. this alias >> >> >> >> >> is >> >> >> >> >> for >> >> >> >> >> newsgroup purposes only. >> >> >> >> >> This posting is provided "AS IS" with no warranties, and >> >> >> >> >> confers >> >> >> >> >> no >> >> >> >> >> rights. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message >> >> >> >> >> news:7D161F1C-1AEF-44B5-BE85-BF7FAF33FBE0(a)microsoft.com... >> >> >> >> >> > Yes I did call WdfDeviceAssignSxWakeSettings to enable wake >> >> >> >> >> > from >> >> >> >> >> > Sx >> >> >> >> >> > and >> >> >> >> >> > also >> >> >> >> >> > use WdfDeviceAssignS0IdleSettings with 10s timeout. How do >> >> >> >> >> > I >> >> >> >> >> > determine >> >> >> >> >> > that >> >> >> >> >> > the host controller is capable of waking from all Sx >> >> >> >> >> > states. I >> >> >> >> >> > can >> >> >> >> >> > wake >> >> >> >> >> > the >> >> >> >> >> > system with other PS2 keyboard, mouse as well as a USB >> >> >> >> >> > mouse. >> >> >> >> >> > >> >> >> >> >> > Regards >> >> >> >> >> > Sumithra >> >> >> >> >> > >> >> >> >> >> > "Doron Holan [MS]" wrote: >> >> >> >> >> > >> >> >> >> >> >> did you call WdfDeviceAssignSxWakeSettings to enable wake >> >> >> >> >> >> from >> >> >> >> >> >> Sx? >> >> >> >> >> >> Did >> >> >> >> >> >> you >> >> >> >> >> >> call WdfDeviceAssignS0IdleSettings to idle out while in >> >> >> >> >> >> S0? >> >> >> >> >> >> If >> >> >> >> >> >> so, >> >> >> >> >> >> is >> >> >> >> >> >> your >> >> >> >> >> >> host controller capable of waking from all Sx states? >> >> >> >> >> >> >> >> >> >> >> >> d >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> >> Please do not send e-mail directly to this alias. this >> >> >> >> >> >> alias >> >> >> >> >> >> is >> >> >> >> >> >> for >> >> >> >> >> >> newsgroup purposes only. >> >> >> >> >> >> This posting is provided "AS IS" with no warranties, and >> >> >> >> >> >> confers >> >> >> >> >> >> no >> >> >> >> >> >> rights. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message >> >> >> >> >> >> news:86451B29-1267-4032-A370-77A4CABECEBF(a)microsoft.com... >> >> >> >> >> >> > Hi >> >> >> >> >> >> > >> >> >> >> >> >> > I am writing a KMDF driver for a USB device that is >> >> >> >> >> >> > remote >> >> >> >> >> >> > wakeup >> >> >> >> >> >> > capable. >> >> >> >> >> >> > But EvtDeviceArmWakeFromSx is never called when I go to >> >> >> >> >> >> > standby. >> >> >> >> >> >> > I >> >> >> >> >> >> > have >> >> >> >> >> >> > registered >> >> >> >> >> >> > >> >> >> >> >> >> > EvtDeviceArmWakeFromS0, EvtDeviceDisarmWakeFromS0 , >> >> >> >> >> >> > EvtDeviceWakeFromS0Triggered, EvtDeviceArmWakeFromSx >> >> >> >> >> >> > ,EvtDeviceDisarmWakeFromSx , >> >> >> >> >> >> > EvtDeviceWakeFromSxTriggered >> >> >> >> >> >> > >> >> >> >> >> >> > Also another thing I noticed is I see the power >> >> >> >> >> >> > management >> >> >> >> >> >> > tab >> >> >> >> >> >> > in >> >> >> >> >> >> > the >> >> >> >> >> >> > Device >> >> >> >> >> >> > Manager, but there are no registry entries created to >> >> >> >> >> >> > reflect >> >> >> >> >> >> > this. >> >> >> >> >> >> > >> >> >> >> >> >> > What should I do to get EvtDeviceArmWakeFromSx called? >> >> >> >> >> >> > >> >> >> >> >> >> > Regards >> >> >> >> >> >> > Sumithra >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>
From: rsdn on 12 Dec 2006 17:15 Thanks. I am attaching the entire log. Regards Sumithra 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner TRACE_FORMAT_SEARCH_PATH= wdftrace: searchpath is: *** ERROR: Module load completed but symbols could not be loaded for NAVENG.sys *** ERROR: Module load completed but symbols could not be loaded for NAVEX15.sys *** ERROR: Module load completed but symbols could not be loaded for NAVAP.sys *** ERROR: Symbol file could not be found. Defaulted to export symbols for SYMEVENT.SYS - *** ERROR: Module load completed but symbols could not be loaded for lfsfilt.sys *** WARNING: Unable to verify timestamp for ialmrnt5.dll *** ERROR: Module load completed but symbols could not be loaded for ialmrnt5.dll *** WARNING: Unable to verify timestamp for ialmdnt5.dll *** ERROR: Module load completed but symbols could not be loaded for ialmdnt5.dll *** WARNING: Unable to verify timestamp for ialmdev5.DLL *** ERROR: Module load completed but symbols could not be loaded for ialmdev5.DLL *** WARNING: Unable to verify timestamp for ialmdd5.DLL *** ERROR: Module load completed but symbols could not be loaded for ialmdd5.DLL *** ERROR: Module load completed but symbols could not be loaded for e100b325.sys *** ERROR: Module load completed but symbols could not be loaded for ialmnt5.sys *** ERROR: Module load completed but symbols could not be loaded for cvintdrv.SYS *** ERROR: Module load completed but symbols could not be loaded for lpx.sys *** ERROR: Module load completed but symbols could not be loaded for ndasbus.sys *** ERROR: Module load completed but symbols could not be loaded for iteraid.sys *** ERROR: Module load completed but symbols could not be loaded for mdmxsdk.sys *** ERROR: Module load completed but symbols could not be loaded for NAVAPEL.SYS *** ERROR: Module load completed but symbols could not be loaded for TIHWDRV.SYS wdftrace: gTracePrefix: "" wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- TMF file used for formatting IFR log is: C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf\wdf01001.tmf Log at 8605a000 Gather log: Please wait, this may take a moment (reading 4032 bytes). % read so far ... 10, 20, 100 There are 22 log entries --- start of log --- 1: FxDeviceInitAPI_cpp5 -- PowerPolicyEventCallbacks size -2042879032 is invalid, expected 28 2: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State WdfDevStatePnpInit from WdfDevStatePnpObjectCreated 3: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State WdfDevStatePnpInitStarting from WdfDevStatePnpInit 4: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting 5: FxIoTarget_cpp995 -- ignoring WDFIOTARGET 7A045FE8 state, sending WDFREQUEST F7A327A0, state 1 6: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated 7: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdleStarted from FxIdleStopped 8: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated 9: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerD0Starting from WdfDevStatePowerStartingCheckDeviceType 10: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting 11: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerD0StartingDmaEnable from WdfDevStatePowerD0StartingConnectInterrupt 12: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerD0StartingStartSelfManagedIo from WdfDevStatePowerD0StartingDmaEnable 13: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdleStartedPowerUp from FxIdleStarted 14: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdleDisabled from FxIdleStartedPowerUp 15: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerDecideD0State from WdfDevStatePowerD0StartingStartSelfManagedIo 16: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State 17: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarting 18: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolStartingDecideS0Wake from WdfDevStatePwrPolStartingSucceeded 19: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake 20: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdleDisabled from FxIdleDisabled 21: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable 22: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces ---- end of log ---- 0: kd> g fyi: \Driver\Mouclass \Device\PointerClass2 irp (86218008) QueryPower-Sleeping3 status c00002d3 watchdog!WdUpdateRecoveryState: Recovery enabled. Break instruction exception - code 80000003 (first chance) ******************************************************************************* * * * You are seeing this message because you pressed either * * CTRL+C (if you run kd.exe) or, * * CTRL+BREAK (if you run WinDBG), * * on your debugger machine's keyboard. * * * * THIS IS NOT A BUG OR A SYSTEM CRASH * * * * If you did not intend to break into the debugger, press the "g" key, then * * press the "Enter" key now. This message might immediately reappear. If it * * does, press "g" and "Enter" again. * * * ******************************************************************************* nt!RtlpBreakWithStatusInstruction: 804dba52 cc int 3 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner TRACE_FORMAT_SEARCH_PATH= wdftrace: searchpath is: wdftrace: gTracePrefix: "" wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- TMF file used for formatting IFR log is: C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf\wdf01001.tmf Log at 8605a000 Gather log: Please wait, this may take a moment (reading 4032 bytes). % read so far ... 10, 20, 30, 40, 100 There are 50 log entries --- start of log --- 1: FxDeviceInitAPI_cpp5 -- PowerPolicyEventCallbacks size -2042879032 is invalid, expected 28 2: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State WdfDevStatePnpInit from WdfDevStatePnpObjectCreated 3: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State WdfDevStatePnpInitStarting from WdfDevStatePnpInit 4: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting 5: FxIoTarget_cpp995 -- ignoring WDFIOTARGET 7A045FE8 state, sending WDFREQUEST F7A327A0, state 1 6: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated 7: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdleStarted from FxIdleStopped 8: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated 9: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerD0Starting from WdfDevStatePowerStartingCheckDeviceType 10: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting 11: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerD0StartingDmaEnable from WdfDevStatePowerD0StartingConnectInterrupt 12: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerD0StartingStartSelfManagedIo from WdfDevStatePowerD0StartingDmaEnable 13: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdleStartedPowerUp from FxIdleStarted 14: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdleDisabled from FxIdleStartedPowerUp 15: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerDecideD0State from WdfDevStatePowerD0StartingStartSelfManagedIo 16: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State 17: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarting 18: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolStartingDecideS0Wake from WdfDevStatePwrPolStartingSucceeded 19: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake 20: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdleDisabled from FxIdleDisabled 21: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable 22: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces 23: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolSleeping from WdfDevStatePwrPolStarted 24: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolSleepingWakePowerDown from WdfDevStatePwrPolSleeping 25: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerGotoDx from WdfDevStatePowerD0 26: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolSleepingSendWake from WdfDevStatePwrPolSleepingWakePowerDown 27: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolCheckPowerPageable from WdfDevStatePwrPolSleepingSendWake 28: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolSleepingWakeWakeArrived from WdfDevStatePwrPolCheckPowerPageable 29: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerGotoDxIoStopped from WdfDevStatePowerGotoDx 30: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdleGoingToDx from FxIdleDisabled 31: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdleInDx from FxIdleGoingToDx 32: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerDx from WdfDevStatePowerGotoDxIoStopped 33: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolSystemAsleepWakeArmed from WdfDevStatePwrPolSleepingWakeWakeArrived 34: PowerPolicyStateMach -- Completion of WaitWake irp 862DF008, STATUS_SUCCESS 35: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolSystemWakeDeviceWakeTriggered from WdfDevStatePwrPolSystemAsleepWakeArmed 36: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolSystemWakeDeviceWakeTriggeredS0 from WdfDevStatePwrPolSystemWakeDeviceWakeTriggered 37: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerCheckDeviceType from WdfDevStatePowerDx 38: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerWaking from WdfDevStatePowerCheckDeviceType 39: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerWakingConnectInterrupt from WdfDevStatePowerWaking 40: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerWakingDmaEnable from WdfDevStatePowerWakingConnectInterrupt 41: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolSystemWakeDeviceWokeDisarm from WdfDevStatePwrPolSystemWakeDeviceWakeTriggeredS0 42: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolSystemWakeDeviceWakeCompletePowerUp from WdfDevStatePwrPolSystemWakeDeviceWokeDisarm 43: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerStartSelfManagedIo from WdfDevStatePowerWakingDmaEnable 44: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdlePowerUp from FxIdleInDx 45: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdlePowerUpComplete from FxIdlePowerUp 46: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdleDisabled from FxIdlePowerUpComplete 47: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State WdfDevStatePowerD0 from WdfDevStatePowerStartSelfManagedIo 48: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolStartingDecideS0Wake from WdfDevStatePwrPolSystemWakeDeviceWakeCompletePowerUp 49: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake 50: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state FxIdleDisabled from FxIdleDisabled ---- end of log ---- "Doron Holan [MS]" wrote: > ok, send the log right after you do a Sx->S0 transition and > EvtDeviceArmWakeFromSx is not called > > d > > -- > Please do not send e-mail directly to this alias. this alias is for > newsgroup purposes only. > This posting is provided "AS IS" with no warranties, and confers no rights. > > > "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > news:572818BE-D4F7-46C1-83F6-751C5269D27C(a)microsoft.com... > > Thanks, from wdflogdump > > > > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner > > TRACE_FORMAT_SEARCH_PATH= > > wdftrace: searchpath is: > > > > wdftrace: gTracePrefix: "" > > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " > > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- > > TMF file used for formatting IFR log is: > > C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf\wdf01001.tmf > > Log at 86073000 > > Gather log: Please wait, this may take a moment (reading 4032 bytes). > > % read so far ... 10, 20, 100 > > There are 22 log entries > > --- start of log --- > > 1: FxDeviceInitAPI_cpp5 -- PowerPolicyEventCallbacks size -2042877768 is > > invalid, expected 28 > > 2: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State > > WdfDevStatePnpInit from WdfDevStatePnpObjectCreated > > 3: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State > > WdfDevStatePnpInitStarting from WdfDevStatePnpInit > > 4: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State > > WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting > > 5: FxIoTarget_cpp995 -- ignoring WDFIOTARGET 79DF5CF8 state, sending > > WDFREQUEST F7A2A7A0, state 1 > > 6: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy state > > WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated > > 7: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state > > FxIdleStarted from FxIdleStopped > > 8: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > > WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated > > 9: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > > WdfDevStatePowerD0Starting from WdfDevStatePowerStartingCheckDeviceType > > 10: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > > WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting > > 11: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > > WdfDevStatePowerD0StartingDmaEnable from > > WdfDevStatePowerD0StartingConnectInterrupt > > 12: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > > WdfDevStatePowerD0StartingStartSelfManagedIo from > > WdfDevStatePowerD0StartingDmaEnable > > 13: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state > > FxIdleStartedPowerUp from FxIdleStarted > > 14: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state > > FxIdleDisabled from FxIdleStartedPowerUp > > 15: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > > WdfDevStatePowerDecideD0State from > > WdfDevStatePowerD0StartingStartSelfManagedIo > > 16: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State > > WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State > > 17: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy state > > WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarting > > 18: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy state > > WdfDevStatePwrPolStartingDecideS0Wake from > > WdfDevStatePwrPolStartingSucceeded > > 19: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy state > > WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake > > 20: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state > > FxIdleDisabled from FxIdleDisabled > > 21: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State > > WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable > > 22: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State > > WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces > > ---- end of log ---- > > > > Regards > > Sumithra > > > > > > "Doron Holan [MS]" wrote: > > > >> for KMDF 1.1 you need to use !wdftmffile , see > >> http://blogs.msdn.com/doronh/archive/2006/07/31/684531.aspx > >> > >> d > >> > >> -- > >> Please do not send e-mail directly to this alias. this alias is for > >> newsgroup purposes only. > >> This posting is provided "AS IS" with no warranties, and confers no > >> rights. > >> > >> > >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > >> news:E79DD4A0-2C17-4DCF-820A-E2575B301AA2(a)microsoft.com... > >> > Thanks. I got the following from wdflogdump > >> > > >> > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner > >> > TRACE_FORMAT_SEARCH_PATH= > >> > wdftrace: searchpath is: C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf > >> > > >> > wdftrace: gTracePrefix: "" > >> > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " > >> > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- > >> > Log at 85dc2000 > >> > Gather log: Please wait, this may take a moment (reading 4032 bytes). > >> > % read so far ... 10, 20, 100 > >> > There are 22 log entries > >> > --- start of log --- > >> > Unknown( 16): GUID=cbb7aabc-8282-c8df-ba62-9bfc713cd1e0 (No Format > >> > Information found). > >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format > >> > Information found). > >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format > >> > Information found). > >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format > >> > Information found). > >> > Unknown( 20): GUID=80086f8b-6b01-45ac-dd58-6ef38233e4de (No Format > >> > Information found). > >> > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format > >> > Information found). > >> > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format > >> > Information found). > >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > >> > Information found). > >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > >> > Information found). > >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > >> > Information found). > >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > >> > Information found). > >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > >> > Information found). > >> > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format > >> > Information found). > >> > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format > >> > Information found). > >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > >> > Information found). > >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format > >> > Information found). > >> > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format > >> > Information found). > >> > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format > >> > Information found). > >> > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format > >> > Information found). > >> > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format > >> > Information found). > >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format > >> > Information found). > >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format > >> > Information found). > >> > > >> > Regards > >> > Sumithra > >> > > >> > "Doron Holan [MS]" wrote: > >> > > >> >> you need to fix your symbols path so that KMDF is in it. for KMDF > >> >> v1.1, > >> >> it > >> >> is in the tree where you installed KMDF , > >> >> %ddkroot%\WDF\KMDF10\symbols\x86fre\wdf > >> >> > >> >> d > >> >> > >> >> -- > >> >> Please do not send e-mail directly to this alias. this alias is for > >> >> newsgroup purposes only. > >> >> This posting is provided "AS IS" with no warranties, and confers no > >> >> rights. > >> >> > >> >> > >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > >> >> news:F4ED721E-C1A5-464D-92E9-F81F1CFBB284(a)microsoft.com... > >> >> > wdfkd.wdflogdump returns > >> >> > > >> >> > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner > >> >> > TRACE_FORMAT_SEARCH_PATH= > >> >> > wdftrace: searchpath is: C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf > >> >> > > >> >> > wdftrace: gTracePrefix: "" > >> >> > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " > >> >> > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- > >> >> > error: Could not retrieve WDF IFR log header for driver > >> >> > eepromburner. > >> >> > hint: Build your driver with newer WDF libraries. > >> >> > > >> >> > I am using build tools from Windows DDK 3790.1830. What am I > >> >> > missing? > >> >> > > >> >> > Regards > >> >> > Sumithra > >> >> > > >> >> > > >> >> > "Doron Holan [MS]" wrote: > >> >> > > >> >> >> !wdfkd.wdflogdump > >> >> >> > >> >> >> -- > >> >> >> Please do not send e-mail directly to this alias. this alias is for > >> >> >> newsgroup purposes only. > >> >> >> This posting is provided "AS IS" with no warranties, and confers no > >> >> >> rights. > >> >> >> > >> >> >> > >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > >> >> >> news:D17A7CB6-A95E-40B2-8478-DE7519139E36(a)microsoft.com... > >> >> >> > OS is Windows XP SP2. I have a USB mouse as well on the bus. I > >> >> >> > could > >> >> >> > not > >> >> >> > get > >> >> >> > a dumo on wdflogdump. The error returned is > >> >> >> > > >> >> >> > 0: kd> !wdflogdump > >> >> >> > No export wdflogdump found. > >> >> >> > > >> >> >> > What version of WinDbg should I be running? > >> >> >> > > >> >> >> > Thanks for your help. > >> >> >> > > >> >> >> > Regards > >> >> >> > Sumithra > >> >> >> > > >> >> >> > "Doron Holan [MS]" wrote: > >> >> >> > > >> >> >> >> what OS? for usb SS to work, all devices on the controller must > >> >> >> >> say > >> >> >> >> they > >> >> >> >> are SS ready. is your device the only one on the bus? what > >> >> >> >> does > >> >> >> >> !wdflogdump say? > >> >> >> >> > >> >> >> >> d > >> >> >> >> > >> >> >> >> -- > >> >> >> >> Please do not send e-mail directly to this alias. this alias is > >> >> >> >> for > >> >> >> >> newsgroup purposes only. > >> >> >> >> This posting is provided "AS IS" with no warranties, and confers > >> >> >> >> no > >> >> >> >> rights. > >> >> >> >> > >> >> >> >> > >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > >> >> >> >> news:5C23E9EA-3B0F-4014-AE0F-E9F451EAA404(a)microsoft.com... > >> >> >> >> > There are 4 UHCI controllers and 1 EHCI controller. All of > >> >> >> >> > them > >> >> >> >> > report > >> >> >> >> > > >> >> >> >> > PDCAP_D0_SUPPORTED > >> >> >> >> > PDCAP_D3_SUPPORTED > >> >> >> >> > PDCAP_WAKE_FROM_D3_SUPPORTED > >> >> >> >> > > >> >> >> >> > I can still wake the system from a USB mouse and PS/2 > >> >> >> >> > keyboard. I > >> >> >> >> > think > >> >> >> >> > the > >> >> >> >> > USB mouse will not be able to wake up the system if the HC is > >> >> >> >> > not > >> >> >> >> > able > >> >> >> >> > to > >> >> >> >> > wake up from all Sx states. > >> >> >> >> > > >> >> >> >> > Regards > >> >> >> >> > Sumithra > >> >> >> >> > > >> >> >> >> > Regards > >> >> >> >> > Sumithra > >> >> >> >> > > >> >> >> >> > "Doron Holan [MS]" wrote: > >> >> >> >> > > >> >> >> >> >> in xp sp2 and later, open up the properties of the HC and > >> >> >> >> >> your > >> >> >> >> >> device > >> >> >> >> >> and > >> >> >> >> >> look at the details tab. select the power caps from the list. > >> >> >> >> >> > >> >> >> >> >> d > >> >> >> >> >> > >> >> >> >> >> -- > >> >> >> >> >> Please do not send e-mail directly to this alias. this alias > >> >> >> >> >> is > >> >> >> >> >> for > >> >> >> >> >> newsgroup purposes only. > >> >> >> >> >> This posting is provided "AS IS" with no warranties, and > >> >> >> >> >> confers > >> >> >> >> >> no > >> >> >> >> >> rights. > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > >> >> >> >> >> news:7D161F1C-1AEF-44B5-BE85-BF7FAF33FBE0(a)microsoft.com... > >> >> >> >> >> > Yes I did call WdfDeviceAssignSxWakeSettings to enable wake > >> >> >> >> >> > from
From: Doron Holan [MS] on 13 Dec 2006 00:35 The first line of the log should be a clear clue 1: FxDeviceInitAPI_cpp5 -- PowerPolicyEventCallbacks size -2042879032 is invalid, expected 28 Did you call WDF_POWER_POLICY_EVENT_CALLBACKS_INIT on the WDF_POWER_POLICY_EVENT_CALLBACKS structure you used when calling WdfDeviceInitSetPowerPolicyEventCallbacks()? d -- Please do not send e-mail directly to this alias. this alias is for newsgroup purposes only. This posting is provided "AS IS" with no warranties, and confers no rights. "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message news:D9D0AA98-A028-4D56-9A33-7FAF700A1FD5(a)microsoft.com... > Thanks. I am attaching the entire log. > > Regards > Sumithra > > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner > TRACE_FORMAT_SEARCH_PATH= > wdftrace: searchpath is: > *** ERROR: Module load completed but symbols could not be loaded for > NAVENG.sys > *** ERROR: Module load completed but symbols could not be loaded for > NAVEX15.sys > *** ERROR: Module load completed but symbols could not be loaded for > NAVAP.sys > *** ERROR: Symbol file could not be found. Defaulted to export symbols > for > SYMEVENT.SYS - > *** ERROR: Module load completed but symbols could not be loaded for > lfsfilt.sys > *** WARNING: Unable to verify timestamp for ialmrnt5.dll > *** ERROR: Module load completed but symbols could not be loaded for > ialmrnt5.dll > *** WARNING: Unable to verify timestamp for ialmdnt5.dll > *** ERROR: Module load completed but symbols could not be loaded for > ialmdnt5.dll > *** WARNING: Unable to verify timestamp for ialmdev5.DLL > *** ERROR: Module load completed but symbols could not be loaded for > ialmdev5.DLL > *** WARNING: Unable to verify timestamp for ialmdd5.DLL > *** ERROR: Module load completed but symbols could not be loaded for > ialmdd5.DLL > *** ERROR: Module load completed but symbols could not be loaded for > e100b325.sys > *** ERROR: Module load completed but symbols could not be loaded for > ialmnt5.sys > *** ERROR: Module load completed but symbols could not be loaded for > cvintdrv.SYS > *** ERROR: Module load completed but symbols could not be loaded for > lpx.sys > *** ERROR: Module load completed but symbols could not be loaded for > ndasbus.sys > *** ERROR: Module load completed but symbols could not be loaded for > iteraid.sys > *** ERROR: Module load completed but symbols could not be loaded for > mdmxsdk.sys > *** ERROR: Module load completed but symbols could not be loaded for > NAVAPEL.SYS > *** ERROR: Module load completed but symbols could not be loaded for > TIHWDRV.SYS > > wdftrace: gTracePrefix: "" > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- > TMF file used for formatting IFR log is: > C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf\wdf01001.tmf > Log at 8605a000 > Gather log: Please wait, this may take a moment (reading 4032 bytes). > % read so far ... 10, 20, 100 > There are 22 log entries > --- start of log --- > 1: FxDeviceInitAPI_cpp5 -- PowerPolicyEventCallbacks size -2042879032 is > invalid, expected 28 > 2: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > WdfDevStatePnpInit from WdfDevStatePnpObjectCreated > 3: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > WdfDevStatePnpInitStarting from WdfDevStatePnpInit > 4: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting > 5: FxIoTarget_cpp995 -- ignoring WDFIOTARGET 7A045FE8 state, sending > WDFREQUEST F7A327A0, state 1 > 6: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated > 7: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdleStarted from FxIdleStopped > 8: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated > 9: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerD0Starting from WdfDevStatePowerStartingCheckDeviceType > 10: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting > 11: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerD0StartingDmaEnable from > WdfDevStatePowerD0StartingConnectInterrupt > 12: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerD0StartingStartSelfManagedIo from > WdfDevStatePowerD0StartingDmaEnable > 13: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdleStartedPowerUp from FxIdleStarted > 14: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdleDisabled from FxIdleStartedPowerUp > 15: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerDecideD0State from > WdfDevStatePowerD0StartingStartSelfManagedIo > 16: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State > 17: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarting > 18: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolStartingDecideS0Wake from > WdfDevStatePwrPolStartingSucceeded > 19: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake > 20: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdleDisabled from FxIdleDisabled > 21: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable > 22: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces > ---- end of log ---- > 0: kd> g > fyi: \Driver\Mouclass \Device\PointerClass2 irp (86218008) > QueryPower-Sleeping3 status c00002d3 > watchdog!WdUpdateRecoveryState: Recovery enabled. > Break instruction exception - code 80000003 (first chance) > ******************************************************************************* > * > * > * You are seeing this message because you pressed either > * > * CTRL+C (if you run kd.exe) or, > * > * CTRL+BREAK (if you run WinDBG), > * > * on your debugger machine's keyboard. > * > * > * > * THIS IS NOT A BUG OR A SYSTEM CRASH > * > * > * > * If you did not intend to break into the debugger, press the "g" key, > then > * > * press the "Enter" key now. This message might immediately reappear. If > it * > * does, press "g" and "Enter" again. > * > * > * > ******************************************************************************* > nt!RtlpBreakWithStatusInstruction: > 804dba52 cc int 3 > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner > TRACE_FORMAT_SEARCH_PATH= > wdftrace: searchpath is: > > wdftrace: gTracePrefix: "" > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- > TMF file used for formatting IFR log is: > C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf\wdf01001.tmf > Log at 8605a000 > Gather log: Please wait, this may take a moment (reading 4032 bytes). > % read so far ... 10, 20, 30, 40, 100 > There are 50 log entries > --- start of log --- > 1: FxDeviceInitAPI_cpp5 -- PowerPolicyEventCallbacks size -2042879032 is > invalid, expected 28 > 2: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > WdfDevStatePnpInit from WdfDevStatePnpObjectCreated > 3: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > WdfDevStatePnpInitStarting from WdfDevStatePnpInit > 4: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting > 5: FxIoTarget_cpp995 -- ignoring WDFIOTARGET 7A045FE8 state, sending > WDFREQUEST F7A327A0, state 1 > 6: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated > 7: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdleStarted from FxIdleStopped > 8: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated > 9: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerD0Starting from WdfDevStatePowerStartingCheckDeviceType > 10: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting > 11: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerD0StartingDmaEnable from > WdfDevStatePowerD0StartingConnectInterrupt > 12: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerD0StartingStartSelfManagedIo from > WdfDevStatePowerD0StartingDmaEnable > 13: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdleStartedPowerUp from FxIdleStarted > 14: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdleDisabled from FxIdleStartedPowerUp > 15: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerDecideD0State from > WdfDevStatePowerD0StartingStartSelfManagedIo > 16: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State > 17: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarting > 18: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolStartingDecideS0Wake from > WdfDevStatePwrPolStartingSucceeded > 19: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake > 20: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdleDisabled from FxIdleDisabled > 21: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable > 22: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces > 23: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolSleeping from WdfDevStatePwrPolStarted > 24: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolSleepingWakePowerDown from WdfDevStatePwrPolSleeping > 25: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerGotoDx from WdfDevStatePowerD0 > 26: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolSleepingSendWake from > WdfDevStatePwrPolSleepingWakePowerDown > 27: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolCheckPowerPageable from WdfDevStatePwrPolSleepingSendWake > 28: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolSleepingWakeWakeArrived from > WdfDevStatePwrPolCheckPowerPageable > 29: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerGotoDxIoStopped from WdfDevStatePowerGotoDx > 30: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdleGoingToDx from FxIdleDisabled > 31: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdleInDx from FxIdleGoingToDx > 32: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerDx from WdfDevStatePowerGotoDxIoStopped > 33: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolSystemAsleepWakeArmed from > WdfDevStatePwrPolSleepingWakeWakeArrived > 34: PowerPolicyStateMach -- Completion of WaitWake irp 862DF008, > STATUS_SUCCESS > 35: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolSystemWakeDeviceWakeTriggered from > WdfDevStatePwrPolSystemAsleepWakeArmed > 36: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolSystemWakeDeviceWakeTriggeredS0 from > WdfDevStatePwrPolSystemWakeDeviceWakeTriggered > 37: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerCheckDeviceType from WdfDevStatePowerDx > 38: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerWaking from WdfDevStatePowerCheckDeviceType > 39: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerWakingConnectInterrupt from WdfDevStatePowerWaking > 40: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerWakingDmaEnable from > WdfDevStatePowerWakingConnectInterrupt > 41: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolSystemWakeDeviceWokeDisarm from > WdfDevStatePwrPolSystemWakeDeviceWakeTriggeredS0 > 42: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolSystemWakeDeviceWakeCompletePowerUp from > WdfDevStatePwrPolSystemWakeDeviceWokeDisarm > 43: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerStartSelfManagedIo from WdfDevStatePowerWakingDmaEnable > 44: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdlePowerUp from FxIdleInDx > 45: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdlePowerUpComplete from FxIdlePowerUp > 46: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdleDisabled from FxIdlePowerUpComplete > 47: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > WdfDevStatePowerD0 from WdfDevStatePowerStartSelfManagedIo > 48: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolStartingDecideS0Wake from > WdfDevStatePwrPolSystemWakeDeviceWakeCompletePowerUp > 49: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake > 50: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > FxIdleDisabled from FxIdleDisabled > ---- end of log ---- > > > "Doron Holan [MS]" wrote: > >> ok, send the log right after you do a Sx->S0 transition and >> EvtDeviceArmWakeFromSx is not called >> >> d >> >> -- >> Please do not send e-mail directly to this alias. this alias is for >> newsgroup purposes only. >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message >> news:572818BE-D4F7-46C1-83F6-751C5269D27C(a)microsoft.com... >> > Thanks, from wdflogdump >> > >> > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner >> > TRACE_FORMAT_SEARCH_PATH= >> > wdftrace: searchpath is: >> > >> > wdftrace: gTracePrefix: "" >> > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " >> > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- >> > TMF file used for formatting IFR log is: >> > C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf\wdf01001.tmf >> > Log at 86073000 >> > Gather log: Please wait, this may take a moment (reading 4032 bytes). >> > % read so far ... 10, 20, 100 >> > There are 22 log entries >> > --- start of log --- >> > 1: FxDeviceInitAPI_cpp5 -- PowerPolicyEventCallbacks size -2042877768 >> > is >> > invalid, expected 28 >> > 2: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State >> > WdfDevStatePnpInit from WdfDevStatePnpObjectCreated >> > 3: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State >> > WdfDevStatePnpInitStarting from WdfDevStatePnpInit >> > 4: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State >> > WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting >> > 5: FxIoTarget_cpp995 -- ignoring WDFIOTARGET 79DF5CF8 state, sending >> > WDFREQUEST F7A2A7A0, state 1 >> > 6: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy >> > state >> > WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated >> > 7: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle state >> > FxIdleStarted from FxIdleStopped >> > 8: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State >> > WdfDevStatePowerStartingCheckDeviceType from >> > WdfDevStatePowerObjectCreated >> > 9: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State >> > WdfDevStatePowerD0Starting from WdfDevStatePowerStartingCheckDeviceType >> > 10: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State >> > WdfDevStatePowerD0StartingConnectInterrupt from >> > WdfDevStatePowerD0Starting >> > 11: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State >> > WdfDevStatePowerD0StartingDmaEnable from >> > WdfDevStatePowerD0StartingConnectInterrupt >> > 12: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State >> > WdfDevStatePowerD0StartingStartSelfManagedIo from >> > WdfDevStatePowerD0StartingDmaEnable >> > 13: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle >> > state >> > FxIdleStartedPowerUp from FxIdleStarted >> > 14: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle >> > state >> > FxIdleDisabled from FxIdleStartedPowerUp >> > 15: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State >> > WdfDevStatePowerDecideD0State from >> > WdfDevStatePowerD0StartingStartSelfManagedIo >> > 16: PowerStateMachine_cp -- !devobj 0x85FF4F00 entering Power State >> > WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State >> > 17: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy >> > state >> > WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarting >> > 18: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy >> > state >> > WdfDevStatePwrPolStartingDecideS0Wake from >> > WdfDevStatePwrPolStartingSucceeded >> > 19: PowerPolicyStateMach -- !devobj 0x85FF4F00 entering power policy >> > state >> > WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake >> > 20: PowerIdleStateMachin -- !devobj 0x85FF4F00 entering power idle >> > state >> > FxIdleDisabled from FxIdleDisabled >> > 21: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State >> > WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable >> > 22: PnpStateMachine_cpp1 -- !devobj 0x85FF4F00 entering PnP State >> > WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces >> > ---- end of log ---- >> > >> > Regards >> > Sumithra >> > >> > >> > "Doron Holan [MS]" wrote: >> > >> >> for KMDF 1.1 you need to use !wdftmffile , see >> >> http://blogs.msdn.com/doronh/archive/2006/07/31/684531.aspx >> >> >> >> d >> >> >> >> -- >> >> Please do not send e-mail directly to this alias. this alias is for >> >> newsgroup purposes only. >> >> This posting is provided "AS IS" with no warranties, and confers no >> >> rights. >> >> >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message >> >> news:E79DD4A0-2C17-4DCF-820A-E2575B301AA2(a)microsoft.com... >> >> > Thanks. I got the following from wdflogdump >> >> > >> >> > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner >> >> > TRACE_FORMAT_SEARCH_PATH= >> >> > wdftrace: searchpath is: C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf >> >> > >> >> > wdftrace: gTracePrefix: "" >> >> > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " >> >> > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- >> >> > Log at 85dc2000 >> >> > Gather log: Please wait, this may take a moment (reading 4032 >> >> > bytes). >> >> > % read so far ... 10, 20, 100 >> >> > There are 22 log entries >> >> > --- start of log --- >> >> > Unknown( 16): GUID=cbb7aabc-8282-c8df-ba62-9bfc713cd1e0 (No Format >> >> > Information found). >> >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format >> >> > Information found). >> >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format >> >> > Information found). >> >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format >> >> > Information found). >> >> > Unknown( 20): GUID=80086f8b-6b01-45ac-dd58-6ef38233e4de (No Format >> >> > Information found). >> >> > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format >> >> > Information found). >> >> > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format >> >> > Information found). >> >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> >> > Information found). >> >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> >> > Information found). >> >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> >> > Information found). >> >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> >> > Information found). >> >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> >> > Information found). >> >> > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format >> >> > Information found). >> >> > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format >> >> > Information found). >> >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> >> > Information found). >> >> > Unknown( 13): GUID=e00d0259-1841-541c-81dd-62de3d983a88 (No Format >> >> > Information found). >> >> > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format >> >> > Information found). >> >> > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format >> >> > Information found). >> >> > Unknown( 15): GUID=f6d56a33-687a-cd66-9bdf-a3302ad96359 (No Format >> >> > Information found). >> >> > Unknown( 16): GUID=ad651db4-3e6f-8cfc-3875-f6bffc262fda (No Format >> >> > Information found). >> >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format >> >> > Information found). >> >> > Unknown( 14): GUID=4f52dfe2-134d-04ae-29d9-54077143a384 (No Format >> >> > Information found). >> >> > >> >> > Regards >> >> > Sumithra >> >> > >> >> > "Doron Holan [MS]" wrote: >> >> > >> >> >> you need to fix your symbols path so that KMDF is in it. for KMDF >> >> >> v1.1, >> >> >> it >> >> >> is in the tree where you installed KMDF , >> >> >> %ddkroot%\WDF\KMDF10\symbols\x86fre\wdf >> >> >> >> >> >> d >> >> >> >> >> >> -- >> >> >> Please do not send e-mail directly to this alias. this alias is for >> >> >> newsgroup purposes only. >> >> >> This posting is provided "AS IS" with no warranties, and confers no >> >> >> rights. >> >> >> >> >> >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message >> >> >> news:F4ED721E-C1A5-464D-92E9-F81F1CFBB284(a)microsoft.com... >> >> >> > wdfkd.wdflogdump returns >> >> >> > >> >> >> > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump >> >> >> > eepromburner >> >> >> > TRACE_FORMAT_SEARCH_PATH= >> >> >> > wdftrace: searchpath is: >> >> >> > C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf >> >> >> > >> >> >> > wdftrace: gTracePrefix: "" >> >> >> > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " >> >> >> > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- >> >> >> > error: Could not retrieve WDF IFR log header for driver >> >> >> > eepromburner. >> >> >> > hint: Build your driver with newer WDF libraries. >> >> >> > >> >> >> > I am using build tools from Windows DDK 3790.1830. What am I >> >> >> > missing? >> >> >> > >> >> >> > Regards >> >> >> > Sumithra >> >> >> > >> >> >> > >> >> >> > "Doron Holan [MS]" wrote: >> >> >> > >> >> >> >> !wdfkd.wdflogdump >> >> >> >> >> >> >> >> -- >> >> >> >> Please do not send e-mail directly to this alias. this alias is >> >> >> >> for >> >> >> >> newsgroup purposes only. >> >> >> >> This posting is provided "AS IS" with no warranties, and confers >> >> >> >> no >> >> >> >> rights. >> >> >> >> >> >> >> >> >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message >> >> >> >> news:D17A7CB6-A95E-40B2-8478-DE7519139E36(a)microsoft.com... >> >> >> >> > OS is Windows XP SP2. I have a USB mouse as well on the bus. I >> >> >> >> > could >> >> >> >> > not >> >> >> >> > get >> >> >> >> > a dumo on wdflogdump. The error returned is >> >> >> >> > >> >> >> >> > 0: kd> !wdflogdump >> >> >> >> > No export wdflogdump found. >> >> >> >> > >> >> >> >> > What version of WinDbg should I be running? >> >> >> >> > >> >> >> >> > Thanks for your help. >> >> >> >> > >> >> >> >> > Regards >> >> >> >> > Sumithra >> >> >> >> > >> >> >> >> > "Doron Holan [MS]" wrote: >> >> >> >> > >> >> >> >> >> what OS? for usb SS to work, all devices on the controller >> >> >> >> >> must >> >> >> >> >> say >> >> >> >> >> they >> >> >> >> >> are SS ready. is your device the only one on the bus? what >> >> >> >> >> does >> >> >> >> >> !wdflogdump say? >> >> >> >> >> >> >> >> >> >> d >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> Please do not send e-mail directly to this alias. this alias >> >> >> >> >> is >> >> >> >> >> for >> >> >> >> >> newsgroup purposes only. >> >> >> >> >> This posting is provided "AS IS" with no warranties, and >> >> >> >> >> confers >> >> >> >> >> no >> >> >> >> >> rights. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message >> >> >> >> >> news:5C23E9EA-3B0F-4014-AE0F-E9F451EAA404(a)microsoft.com... >> >> >> >> >> > There are 4 UHCI controllers and 1 EHCI controller. All of >> >> >> >> >> > them >> >> >> >> >> > report >> >> >> >> >> > >> >> >> >> >> > PDCAP_D0_SUPPORTED >> >> >> >> >> > PDCAP_D3_SUPPORTED >> >> >> >> >> > PDCAP_WAKE_FROM_D3_SUPPORTED >> >> >> >> >> > >> >> >> >> >> > I can still wake the system from a USB mouse and PS/2 >> >> >> >> >> > keyboard. I >> >> >> >> >> > think >> >> >> >> >> > the >> >> >> >> >> > USB mouse will not be able to wake up the system if the HC >> >> >> >> >> > is >> >> >> >> >> > not >> >> >> >> >> > able >> >> >> >> >> > to >> >> >> >> >> > wake up from all Sx states. >> >> >> >> >> > >> >> >> >> >> > Regards >> >> >> >> >> > Sumithra >> >> >> >> >> > >> >> >> >> >> > Regards >> >> >> >> >> > Sumithra >> >> >> >> >> > >> >> >> >> >> > "Doron Holan [MS]" wrote: >> >> >> >> >> > >> >> >> >> >> >> in xp sp2 and later, open up the properties of the HC and >> >> >> >> >> >> your >> >> >> >> >> >> device >> >> >> >> >> >> and >> >> >> >> >> >> look at the details tab. select the power caps from the >> >> >> >> >> >> list. >> >> >> >> >> >> >> >> >> >> >> >> d >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> >> Please do not send e-mail directly to this alias. this >> >> >> >> >> >> alias >> >> >> >> >> >> is >> >> >> >> >> >> for >> >> >> >> >> >> newsgroup purposes only. >> >> >> >> >> >> This posting is provided "AS IS" with no warranties, and >> >> >> >> >> >> confers >> >> >> >> >> >> no >> >> >> >> >> >> rights. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message >> >> >> >> >> >> news:7D161F1C-1AEF-44B5-BE85-BF7FAF33FBE0(a)microsoft.com... >> >> >> >> >> >> > Yes I did call WdfDeviceAssignSxWakeSettings to enable >> >> >> >> >> >> > wake >> >> >> >> >> >> > from
From: rsdn on 13 Dec 2006 15:07 Thanks. That did it. It should have a struck me to check the code again. I am testing further. Regards Sumithra "Doron Holan [MS]" wrote: > The first line of the log should be a clear clue > > 1: FxDeviceInitAPI_cpp5 -- PowerPolicyEventCallbacks size -2042879032 is > invalid, expected 28 > > Did you call WDF_POWER_POLICY_EVENT_CALLBACKS_INIT on the > WDF_POWER_POLICY_EVENT_CALLBACKS structure you used when calling > WdfDeviceInitSetPowerPolicyEventCallbacks()? > > d > > -- > Please do not send e-mail directly to this alias. this alias is for > newsgroup purposes only. > This posting is provided "AS IS" with no warranties, and confers no rights. > > > "rsdn" <rsdn(a)discussions.microsoft.com> wrote in message > news:D9D0AA98-A028-4D56-9A33-7FAF700A1FD5(a)microsoft.com... > > Thanks. I am attaching the entire log. > > > > Regards > > Sumithra > > > > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner > > TRACE_FORMAT_SEARCH_PATH= > > wdftrace: searchpath is: > > *** ERROR: Module load completed but symbols could not be loaded for > > NAVENG.sys > > *** ERROR: Module load completed but symbols could not be loaded for > > NAVEX15.sys > > *** ERROR: Module load completed but symbols could not be loaded for > > NAVAP.sys > > *** ERROR: Symbol file could not be found. Defaulted to export symbols > > for > > SYMEVENT.SYS - > > *** ERROR: Module load completed but symbols could not be loaded for > > lfsfilt.sys > > *** WARNING: Unable to verify timestamp for ialmrnt5.dll > > *** ERROR: Module load completed but symbols could not be loaded for > > ialmrnt5.dll > > *** WARNING: Unable to verify timestamp for ialmdnt5.dll > > *** ERROR: Module load completed but symbols could not be loaded for > > ialmdnt5.dll > > *** WARNING: Unable to verify timestamp for ialmdev5.DLL > > *** ERROR: Module load completed but symbols could not be loaded for > > ialmdev5.DLL > > *** WARNING: Unable to verify timestamp for ialmdd5.DLL > > *** ERROR: Module load completed but symbols could not be loaded for > > ialmdd5.DLL > > *** ERROR: Module load completed but symbols could not be loaded for > > e100b325.sys > > *** ERROR: Module load completed but symbols could not be loaded for > > ialmnt5.sys > > *** ERROR: Module load completed but symbols could not be loaded for > > cvintdrv.SYS > > *** ERROR: Module load completed but symbols could not be loaded for > > lpx.sys > > *** ERROR: Module load completed but symbols could not be loaded for > > ndasbus.sys > > *** ERROR: Module load completed but symbols could not be loaded for > > iteraid.sys > > *** ERROR: Module load completed but symbols could not be loaded for > > mdmxsdk.sys > > *** ERROR: Module load completed but symbols could not be loaded for > > NAVAPEL.SYS > > *** ERROR: Module load completed but symbols could not be loaded for > > TIHWDRV.SYS > > > > wdftrace: gTracePrefix: "" > > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " > > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- > > TMF file used for formatting IFR log is: > > C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf\wdf01001.tmf > > Log at 8605a000 > > Gather log: Please wait, this may take a moment (reading 4032 bytes). > > % read so far ... 10, 20, 100 > > There are 22 log entries > > --- start of log --- > > 1: FxDeviceInitAPI_cpp5 -- PowerPolicyEventCallbacks size -2042879032 is > > invalid, expected 28 > > 2: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > > WdfDevStatePnpInit from WdfDevStatePnpObjectCreated > > 3: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > > WdfDevStatePnpInitStarting from WdfDevStatePnpInit > > 4: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > > WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting > > 5: FxIoTarget_cpp995 -- ignoring WDFIOTARGET 7A045FE8 state, sending > > WDFREQUEST F7A327A0, state 1 > > 6: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated > > 7: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdleStarted from FxIdleStopped > > 8: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated > > 9: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerD0Starting from WdfDevStatePowerStartingCheckDeviceType > > 10: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting > > 11: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerD0StartingDmaEnable from > > WdfDevStatePowerD0StartingConnectInterrupt > > 12: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerD0StartingStartSelfManagedIo from > > WdfDevStatePowerD0StartingDmaEnable > > 13: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdleStartedPowerUp from FxIdleStarted > > 14: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdleDisabled from FxIdleStartedPowerUp > > 15: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerDecideD0State from > > WdfDevStatePowerD0StartingStartSelfManagedIo > > 16: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State > > 17: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarting > > 18: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolStartingDecideS0Wake from > > WdfDevStatePwrPolStartingSucceeded > > 19: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake > > 20: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdleDisabled from FxIdleDisabled > > 21: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > > WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable > > 22: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > > WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces > > ---- end of log ---- > > 0: kd> g > > fyi: \Driver\Mouclass \Device\PointerClass2 irp (86218008) > > QueryPower-Sleeping3 status c00002d3 > > watchdog!WdUpdateRecoveryState: Recovery enabled. > > Break instruction exception - code 80000003 (first chance) > > ******************************************************************************* > > * > > * > > * You are seeing this message because you pressed either > > * > > * CTRL+C (if you run kd.exe) or, > > * > > * CTRL+BREAK (if you run WinDBG), > > * > > * on your debugger machine's keyboard. > > * > > * > > * > > * THIS IS NOT A BUG OR A SYSTEM CRASH > > * > > * > > * > > * If you did not intend to break into the debugger, press the "g" key, > > then > > * > > * press the "Enter" key now. This message might immediately reappear. If > > it * > > * does, press "g" and "Enter" again. > > * > > * > > * > > ******************************************************************************* > > nt!RtlpBreakWithStatusInstruction: > > 804dba52 cc int 3 > > 0: kd> !C:\WinDDK\WDF\KMDF10\bin\x86\wdfkd.wdflogdump eepromburner > > TRACE_FORMAT_SEARCH_PATH= > > wdftrace: searchpath is: > > > > wdftrace: gTracePrefix: "" > > wdftrace: gTracePrefixDefault: "%7!u!: %2!-20.20s! -- " > > wdftrace: trace format prefix: %7!u!: %2!-20.20s! -- > > TMF file used for formatting IFR log is: > > C:\WinDDK\WDF\KMDF10\symbols\x86fre\wdf\tmf\wdf01001.tmf > > Log at 8605a000 > > Gather log: Please wait, this may take a moment (reading 4032 bytes). > > % read so far ... 10, 20, 30, 40, 100 > > There are 50 log entries > > --- start of log --- > > 1: FxDeviceInitAPI_cpp5 -- PowerPolicyEventCallbacks size -2042879032 is > > invalid, expected 28 > > 2: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > > WdfDevStatePnpInit from WdfDevStatePnpObjectCreated > > 3: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > > WdfDevStatePnpInitStarting from WdfDevStatePnpInit > > 4: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > > WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting > > 5: FxIoTarget_cpp995 -- ignoring WDFIOTARGET 7A045FE8 state, sending > > WDFREQUEST F7A327A0, state 1 > > 6: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated > > 7: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdleStarted from FxIdleStopped > > 8: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated > > 9: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerD0Starting from WdfDevStatePowerStartingCheckDeviceType > > 10: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting > > 11: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerD0StartingDmaEnable from > > WdfDevStatePowerD0StartingConnectInterrupt > > 12: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerD0StartingStartSelfManagedIo from > > WdfDevStatePowerD0StartingDmaEnable > > 13: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdleStartedPowerUp from FxIdleStarted > > 14: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdleDisabled from FxIdleStartedPowerUp > > 15: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerDecideD0State from > > WdfDevStatePowerD0StartingStartSelfManagedIo > > 16: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State > > 17: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarting > > 18: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolStartingDecideS0Wake from > > WdfDevStatePwrPolStartingSucceeded > > 19: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake > > 20: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdleDisabled from FxIdleDisabled > > 21: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > > WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable > > 22: PnpStateMachine_cpp1 -- !devobj 0x8615B180 entering PnP State > > WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces > > 23: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolSleeping from WdfDevStatePwrPolStarted > > 24: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolSleepingWakePowerDown from WdfDevStatePwrPolSleeping > > 25: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerGotoDx from WdfDevStatePowerD0 > > 26: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolSleepingSendWake from > > WdfDevStatePwrPolSleepingWakePowerDown > > 27: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolCheckPowerPageable from WdfDevStatePwrPolSleepingSendWake > > 28: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolSleepingWakeWakeArrived from > > WdfDevStatePwrPolCheckPowerPageable > > 29: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerGotoDxIoStopped from WdfDevStatePowerGotoDx > > 30: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdleGoingToDx from FxIdleDisabled > > 31: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdleInDx from FxIdleGoingToDx > > 32: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerDx from WdfDevStatePowerGotoDxIoStopped > > 33: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolSystemAsleepWakeArmed from > > WdfDevStatePwrPolSleepingWakeWakeArrived > > 34: PowerPolicyStateMach -- Completion of WaitWake irp 862DF008, > > STATUS_SUCCESS > > 35: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolSystemWakeDeviceWakeTriggered from > > WdfDevStatePwrPolSystemAsleepWakeArmed > > 36: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolSystemWakeDeviceWakeTriggeredS0 from > > WdfDevStatePwrPolSystemWakeDeviceWakeTriggered > > 37: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerCheckDeviceType from WdfDevStatePowerDx > > 38: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerWaking from WdfDevStatePowerCheckDeviceType > > 39: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerWakingConnectInterrupt from WdfDevStatePowerWaking > > 40: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerWakingDmaEnable from > > WdfDevStatePowerWakingConnectInterrupt > > 41: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolSystemWakeDeviceWokeDisarm from > > WdfDevStatePwrPolSystemWakeDeviceWakeTriggeredS0 > > 42: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolSystemWakeDeviceWakeCompletePowerUp from > > WdfDevStatePwrPolSystemWakeDeviceWokeDisarm > > 43: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerStartSelfManagedIo from WdfDevStatePowerWakingDmaEnable > > 44: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdlePowerUp from FxIdleInDx > > 45: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdlePowerUpComplete from FxIdlePowerUp > > 46: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdleDisabled from FxIdlePowerUpComplete > > 47: PowerStateMachine_cp -- !devobj 0x8615B180 entering Power State > > WdfDevStatePowerD0 from WdfDevStatePowerStartSelfManagedIo > > 48: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolStartingDecideS0Wake from > > WdfDevStatePwrPolSystemWakeDeviceWakeCompletePowerUp > > 49: PowerPolicyStateMach -- !devobj 0x8615B180 entering power policy state > > WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake > > 50: PowerIdleStateMachin -- !devobj 0x8615B180 entering power idle state > > FxIdleDisabled from FxIdleDisabled > > ---- end of log ---- > > > > > > "Doron Holan [MS]" wrote: > > > >> ok, send the log right after you do a Sx->S0 transition and > >> EvtDeviceArmWakeFromSx is not called > >> > >> d > >> > >> --
First
|
Prev
|
Pages: 1 2 3 4 Prev: How to send IOCTLs to a filter driver KB uses wrong mutex? Next: Is WDK's sample Ramdisk a Filter driver? |