none
wdflogdump won't. RRS feed

  • Question

  • 1: kd> !wdflogdump xxxxxxx
    Trace searchpath is: C:\ProgramFiles(x86)\WindowsKits\8.0\Tools\x86\Tracing

    Trace format prefix is: %7!u!: %!FUNC! - 
    Trying to extract TMF information from - c:\users\xxxxxx\symbols\Wdf01000.pdb\728BD5691936407D901237B3A05AE8182\Wdf01000.pdb
    Log at 00000001
    Gather log: Please wait, this may take a moment (reading 0 bytes).
    % read so far ... 
    warn: The log could not be accessed
    hint: Are the symbols the WDF library available?
    hint: The log is inaccessable after driver unload.

    Seems sort of broken, but I have no idea why.


    Mark Roddy Windows Driver and OS consultant www.hollistech.com

    Friday, March 22, 2013 4:06 PM
    Moderator

Answers

  • Is this just another manifestation of this?:

    http://www.osronline.com/showThread.cfm?link=237007

    We wasted a few hours chasing this one down today, so just wanted to put this out there and save everyone else the hassle...

    On or around 11/30, a bad version of wdf01000.pdb made its way onto the public symbol server (timestamp 11/30/2012 6:23AM). The effect of this is that the extensions exported from wdfkd.dll will not function properly. For example, here's some output from !wdfdevice using the bad PDB:

    ***************************************
    1: kd> !wdfdevice 0x5d73c908

    Dumping WDFDEVICE 0x5d73c908
    =================================

    WDM PDEVICE_OBJECTs:  self acac4320, attached a2840298, pdo a2840298

    Filter WDFDEVICE

    Pnp state:  0 ( WdfDevStatePnpInvalid )
    Power state:  0x8a000000 (No matching name)
    Power Pol state:  0 ( WdfDevStatePwrPolInvalid )

    Device is NOT the power policy owner for the stack
    No pended pnp, power, wait-wake irps
    ***************************************

    We wasted a few hours chasing this one down today, so just wanted to put this out there and save everyone else the hassle...

    On or around 11/30, a bad version of wdf01000.pdb made its way onto the public symbol server (timestamp 11/30/2012 6:23AM). The effect of this is that the extensions exported from wdfkd.dll will not function properly. For example, here's some output from !wdfdevice using the bad PDB:

    ***************************************
    1: kd> !wdfdevice 0x5d73c908

    Dumping WDFDEVICE 0x5d73c908
    =================================

    WDM PDEVICE_OBJECTs:  self acac4320, attached a2840298, pdo a2840298

    Filter WDFDEVICE

    Pnp state:  0 ( WdfDevStatePnpInvalid )
    Power state:  0x8a000000 (No matching name)
    Power Pol state:  0 ( WdfDevStatePwrPolInvalid )

    Device is NOT the power policy owner for the stack
    No pended pnp, power, wait-wake irps
    ***************************************

    We reported the issue to the KMDF team and they quickly diagnosed the issue, provided a workaround, and are working on getting it resolved. If you happen to stumble upon this issue in the meantime, the workaround is to download the RTM symbol packs and use the KMDF PDBs provided therein:

    http://msdn.microsoft.com/en-us/windows/hardware/gg463028.aspx

    We have confirmed that this resolves the issue for us on both x86 and x64 versions of the O/S.

    -scott
    OSR 


    Mark Roddy Windows Driver and OS consultant www.hollistech.com

    Friday, March 22, 2013 5:28 PM
    Moderator