[KMDF WDF 1.5] DTM test : common scenario stress with IO (WDF Preview)

NTDEV
1

Hello all,

I have a problem for execute a WHQL test :
the concerned is : Common scenario stress with IO (WDF Preview)

During his execution, the target machine is frozen, and unfortunatelly I don’t have a BSOD for debug this problem.

Someone could explain me how to proceed for debug this behavior.

Possible to reproduce this test manually with my debug machine over 1394 cable ??
Or any other tips.

Thanks in advance,

Best regards,

Moulefrite

2

xxxxx@hotmail.com wrote:

I have a problem for execute a WHQL test :
the concerned is : Common scenario stress with IO (WDF Preview)

During his execution, the target machine is frozen, and unfortunatelly I don’t have a BSOD for debug this problem.

Someone could explain me how to proceed for debug this behavior.

Possible to reproduce this test manually with my debug machine over 1394 cable ??
Or any other tips.

The DTM detailed error log will show you the command line that was used
to run the test, if you can figure out where to look. You can run that
command line by hand with a debugger attached.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

Hi,

Have you already passed the “Common Scenario Stress with I/O” test, the one without the WDF verification? What type of a device is this for? Are you using UMDF or KMDF? With the WDF Preview test, there’s additional WDF related checks that’s enabled part of the preview test in WLK 1.5 which are specifically as below;
For KMDF Drivers:
Enable KMDF Enhanced Verifier
Enable WDF Verifier
Enable Handle Tracking
For UMDF Drivers:
Enable App Verifier for WdfHost.exe with the below settings
Exceptions Handles Locks Memory TLS
Enable UMDF Object Tracking

So if the original Common Scenario Stress Test passes but the WDF preview one hits this frozen state then it’s very likely that the above verifications arent satisfied. While executing this test can you please try attaching a kernel debugger to inspect if there’s any useful data we can get? Another step would be to enable the above settings, according to the framework type your device stack is using, one by one and observe if any of it specifically triggers this problem. BTW you can use the WdfVerifier tool from WDK for enabling WDF related verification , more info here http://msdn.microsoft.com/en-us/library/ff556129(VS.85).aspx

Please let me know if this helps.

Best Regards,
Neslihan

4

Thanks Tim and Neslihan Bulut for your reply,

The DTM detailed error log will show you the command line that was used to run the test, if you can
figure out where to look. You can run that command line by hand with a debugger attached.

I have tried to reproduce this test, but when I launch the .wsf script from WDK.
I have an error “WTT Logger unavailable! please reinstall WDTF”.
So I have installed debugView client to my target machine and debugView to my DTM Studio Machine.
I wait to see the target frozen for debug it.

For Neslihan :
My driver is KMDF Based, this test pass for windows XP 32bit, and the normal test (without WD FPreview) work fine for Windows 7 32bit.
My certification is for :
_ Windows XP x86 : All tests Pass successfully
_ Windows 7 x86 : All tests Pass successfully exept ( Common Scenario WDF Preview )

Thanks a lot for your great help,

Best regards,

Moulefrite