Please help me, i am running WLK 1.2 Test for miniport driver it is falling the below mentioned two tests,
DP WLK - Hot-Replace - Device Test - Verify driver support for D3 power state
DP WLK - Hot-Add - Device Test - Verify driver support for Hot-Add CPU
i have installed Latest Update filter from winqual website.
In this Hot-Add and Hot-Replace some of child tests only getting fails. I can able to see Green tick mark in that tests but in status it is showing fail.
Below i have mentioned Child test informations:
Hot-Add Device Child Test result informations :
Failed Tests :
RunJob - Install WDTF
RunJob - Un-install WDTF
Run WDKDriverValidationLibraryJob Task
RunJob - DP_Lib_Job - Clean up Hot-Add CPU - Device Test
RunJob - DP_Lib_Job - Setup Hot-Add CPU - Device Test
Run WDK File Signature verification Library Job Task
Passed Tests:
Reboot 2
Reboot
RunJob - DP_Lib_Job - Run Hot-Add CPU - Device Test
Run SimpleIOStress
Hot-Replace Device Child Test result informations :
I think hot add and hot replace test cases are not really run
successful. First of all, please make sure that install WDTF and setup
hot add/replace child job can run success in your test environment.
Please follow WLK doc to setup test environment properly. Another
suggestion, there is a hotfix for hot replace http://support.microsoft.com/kb/961324.
Most of times install WDTF and Setup hot add/replace child jobs are getting fail. If suppose any one time both get pass then uninstall WDTF and cleanup hot add/replace are getting fail.
Test setup is perfect we got certification in last version of driver using some other setup now i am using another test machines for certification. Is there anyway to identify the test machine having hot-Add/Replace CPU support.
> Is there anyway to identify the test machine having hot-Add/Replace CPU support.
Sorry, I don’t know and I think it’s hard to get info about that.
Microsoft provide less doc about that two test case. You can have a try
to install a fresh new OS on current machine with all default inbox
driver and try to run those two test case to detect whether current
machine support hot add/replace. If not, you should use your previously
machine to run those two test case.
Haibo
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Wayne Gong
Sent: Monday, March 23, 2009 3:42 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Hot-Add and Hot-Replace - Device Test failure in
miniport driver
Is there anyway to identify the test machine having hot-Add/Replace CPU
support.
Sorry, I don’t know and I think it’s hard to get info about that.
Microsoft provide less doc about that two test case. You can have a try
to install a fresh new OS on current machine with all default inbox
driver and try to run those two test case to detect whether current
machine support hot add/replace. If not, you should use your previously
machine to run those two test case.
please tell at which condition install WDTF and Setup hot add/replace child jobs are get fail. Now i am using Windows 2008 (Datacenter) OS for certification test. For what purpose DTM Studio installing this two things in test machine at the time of test.