where are the TMF files?

I’m learning how to use the ETW version of tracing in 2K8 R2 and I’ve
ran into a problem that is preventing progress. MANY of the traceable
elements do not appear to have formatting information available. I
would like to trace the PCI bus driver and STORport. I can’t find the
TMF files for them and the detail is NOT in the symbol files available
from Microsoft (at least not according to tracepdb.exe).

Can anyone tell me WHERE the TMF files are for the drivers??

TIA,
Robert.


Robert Randall | xxxxx@gmail.com

Yup!

This issue has been raised a number of times to the Windows Driver Kits team over the years.

I am not aware of any current solution.

Peter
OSR

The solution is .

It is a truly maddening “feature”.

Mark Roddy

On Thu, Mar 17, 2011 at 4:53 PM, wrote:
>


>
> Yup!
>
> This issue has been raised a number of times to the Windows Driver Kits team over the years.
>
> I am not aware of any current solution.
>
> Peter
> OSR
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>

Robert,


MANY of the traceable elements do not appear to have formatting information
available. I
would like to trace the PCI bus driver and STORport.

[/quote]


Like any other vendor, Microsoft may choose to have traceable elements that
generates logs for internal consumption. It could be that the traceable
elements you see fall under that category.

- Danilo

Well this is the answer I expected but it is a bit frustrating.

So when STORport locks up (blocks forever) on an internal call after a
miniport driver makes a call to a STORport API what is a fella to do??

Oh yeah, get out his credit card and call Microsoft :wink:

Off to the web site to open a case and start the waiting process…

Thanks all!

Robert.

On Thu, Mar 17, 2011 at 9:38 PM, Danilo Almeida wrote:
> Robert,
>
>
> MANY of the traceable elements do not appear to have formatting information
> available. ?I
> would like to trace the PCI bus driver and STORport.
>
[/quote]

>
> Like any other vendor, Microsoft may choose to have traceable elements that
> generates logs for internal consumption. ?It could be that the traceable
> elements you see fall under that category.
>
> - Danilo
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>


Robert Randall | xxxxx@gmail.com

“Robert Randall” wrote in message
news:xxxxx@ntdev…
> Well this is the answer I expected but it is a bit frustrating.
>
> So when STORport locks up (blocks forever) on an internal call after a
> miniport driver makes a call to a STORport API what is a fella to do??

But this is a completely different situation.
If it locks - get the debugger, break in and post the stack.
Is this reproducible?

> Oh yeah, get out his credit card and call Microsoft :wink:

One can call OSR with the same credit card, no? :wink:

– pa

Ah good point on the OSR support :wink:

Yes, very very reproducible. However, I suspect a hardware problem so
I’m switching to Linux to determine if it is a hardware problem or
software problem.

If it is a software problem I’ll post the stack traces and some
additional details.

Thanks all.

Best,
Robert.

On Fri, Mar 18, 2011 at 9:39 AM, Pavel A. wrote:
> “Robert Randall” wrote in message
> news:xxxxx@ntdev…
>>
>> Well this is the answer I expected but it is a bit frustrating.
>>
>> So when STORport locks up (blocks forever) on an internal call after a
>> miniport driver makes a call to a STORport API what is a fella to do??
>
> But this is a completely different situation.
> If it locks - ?get the debugger, break in and post the stack.
> Is this reproducible?
>
>> Oh yeah, get out his credit card and call Microsoft :wink:
>
> One can call OSR with the same credit card, no? ?:wink:
>
> – pa
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>


Robert Randall | xxxxx@gmail.com

Basically the set of “traceable elements that generates logs for
internal consumption (only)” is identical to the set of traceable
elements.

I’m sure at this point Microsoft would prefer a closed box like iOS on
iP(hone/add) devices over an platform open to third party driver
development, but what they have is the latter, and not providing the
decoder rings for device stack tracing is silly and short-sighted and
unacceptable and is really annoying as so much time was spent touting
the glory of ETW as the Great New Tracing Facility.

Mark Roddy

On Thu, Mar 17, 2011 at 10:38 PM, Danilo Almeida wrote:
> Robert,
>
>
> MANY of the traceable elements do not appear to have formatting information
> available. ?I
> would like to trace the PCI bus driver and STORport.
>
[/quote]

>
> Like any other vendor, Microsoft may choose to have traceable elements that
> generates logs for internal consumption. ?It could be that the traceable
> elements you see fall under that category.
>
> - Danilo
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>

BRAVO!

On Fri, Mar 18, 2011 at 1:08 PM, Mark Roddy wrote:
> Basically the set of “traceable elements that generates logs for
> internal consumption (only)” is identical to the set of traceable
> elements.
>
> I’m sure at this point Microsoft would prefer a closed box like iOS on
> iP(hone/add) devices over an platform open to third party driver
> development, but what they have is the latter, and not providing the
> decoder rings for device stack tracing is silly and short-sighted and
> unacceptable and is really annoying as so much time was spent touting
> the glory of ETW as the Great New Tracing Facility.
>
> Mark Roddy
>
>
>
> On Thu, Mar 17, 2011 at 10:38 PM, Danilo Almeida wrote:
>> Robert,
>>
>>
>> MANY of the traceable elements do not appear to have formatting information
>> available. ?I
>> would like to trace the PCI bus driver and STORport.
>>
[/quote]

>>
>> Like any other vendor, Microsoft may choose to have traceable elements that
>> generates logs for internal consumption. ?It could be that the traceable
>> elements you see fall under that category.
>>
>> - Danilo
>>
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>


Robert Randall | xxxxx@gmail.com