HCT 12.0 Help !

NTDEV
1

Hi All,

I’m running into a situation like this (new to this HCT so might not
make lot of sense … )—

  1. The driver ( again ) is pseudo-bus type
  2. Under certain machine(s), when I try to start the test under the disk
    categories, it comes back with “It could not identify one of the
    device…” under serial number detection. IN ESSENCE WHAT I UNDERSTAND
    THAT WE CAN REALLY GO ANY FURTHER ON THE TEST PATH, UNLESS IT IS
    RESOLVED, SO disk stress or driver verifier etc are meaningless at that
    point … Under some other machine(s), it does not complain ( same
    identical driver, and inf ) so that yellow bang is not there under any
    of the listed tests that can be hand under the disk category. BUT WHEN I
    RUN THE DRIVER TEST test suite ( ie, it has multiple tests, and
    requiring multiple reboot ), all most always I see there is a delay in
    booting up, and I’m almost sure PnP is trying its best to enumerate the
    devices, so I THINK IT TIMES OUT AND throw-away the driver, and
    eventually boots up, kicks off the remaining test, NOW THE TEST FINDS
    THAT A DEVICE WAS PRESENT AND CONFIGURED FOR THIS SET OF TESTS AND NOW
    GONE …

I know I just put a broad coverage, so if I get any guestimate, insight
that would be great to narrow my search-space !!

-pro

2

Further information(s) on it —

Under previous version of HCT ( presumably 11.x ) it did not have this
problem, with the same binary and inf, so something around the PnP might
have more stringent checking in the HCT_12.0.

I tried to emulate the reboot ( w/o running the HCT on the machine ) and
could not find any reason to suspect the driver being getting in the way.
Everytime it reboots ( again it takes quite a bit of time, this I will have
to narrow in my next test, as observed, it is going power-down path, not
coming back-up from the reset ), the driver is still in the stack, and
things are bit better …

So the net would be something like “device pid/vid configuration” and/or PnP
where the driver might not be robust enough as per hct12 …

Any thoughts ?

-pro

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Sinha, Prokash
Sent: Monday, November 08, 2004 11:03 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] HCT 12.0 Help !

Hi All,

I’m running into a situation like this (new to this HCT so might not
make lot of sense … )—

  1. The driver ( again ) is pseudo-bus type
  2. Under certain machine(s), when I try to start the test under the disk
    categories, it comes back with “It could not identify one of the
    device…” under serial number detection. IN ESSENCE WHAT I UNDERSTAND
    THAT WE CAN REALLY GO ANY FURTHER ON THE TEST PATH, UNLESS IT IS
    RESOLVED, SO disk stress or driver verifier etc are meaningless at that
    point … Under some other machine(s), it does not complain ( same
    identical driver, and inf ) so that yellow bang is not there under any
    of the listed tests that can be hand under the disk category. BUT WHEN I
    RUN THE DRIVER TEST test suite ( ie, it has multiple tests, and
    requiring multiple reboot ), all most always I see there is a delay in
    booting up, and I’m almost sure PnP is trying its best to enumerate the
    devices, so I THINK IT TIMES OUT AND throw-away the driver, and
    eventually boots up, kicks off the remaining test, NOW THE TEST FINDS
    THAT A DEVICE WAS PRESENT AND CONFIGURED FOR THIS SET OF TESTS AND NOW
    GONE …

I know I just put a broad coverage, so if I get any guestimate, insight
that would be great to narrow my search-space !!

-pro

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

Prokash, I contacted the WHQL Device Testing team on your behalf. Here is
their response:

We’re not sure what you mean by “Psuedo bus.” Is this a virtual device
driver with a root enumerated PnP ID?

Under HCT 11.2, the ACPI Stress version fails and pop ups an error dialog
like ‘can’t find PNP ID’. . This causes a failure in driver verifier and
device path exerciser. See this errata:

http://www.microsoft.com/whdc/hwtest/search/details.aspx?Type=err&ID=1146

Under HCT 12.0 and HCT 12.1, this was fixed, so we are not sure what is
occurring.

Please send the following information to xxxxx@microsoft.com

  1. The exact error you are seeing from the HCT. Please copy and paste or
    re-type the message that you see in the dialog box.

  2. Please provide the plug and play ID of your device and the type of device
    that you are qualifying.

  3. Please provide any failing logs and the names of the tests that are
    failing.

Thanks,
The WHQL Device Testing Team

“Prokash Sinha” wrote in message news:xxxxx@ntdev…
> Further information(s) on it —
>
> Under previous version of HCT ( presumably 11.x ) it did not have this
> problem, with the same binary and inf, so something around the PnP might
> have more stringent checking in the HCT_12.0.
>
> I tried to emulate the reboot ( w/o running the HCT on the machine ) and
> could not find any reason to suspect the driver being getting in the way.
> Everytime it reboots ( again it takes quite a bit of time, this I will
> have
> to narrow in my next test, as observed, it is going power-down path, not
> coming back-up from the reset ), the driver is still in the stack, and
> things are bit better …
>
> So the net would be something like “device pid/vid configuration” and/or
> PnP
> where the driver might not be robust enough as per hct12 …
>
> Any thoughts ?
>
> -pro
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Sinha, Prokash
> Sent: Monday, November 08, 2004 11:03 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] HCT 12.0 Help !
>
>
> Hi All,
>
> I’m running into a situation like this (new to this HCT so might not
> make lot of sense … )—
>
> 1) The driver ( again ) is pseudo-bus type
> 2) Under certain machine(s), when I try to start the test under the disk
> categories, it comes back with “It could not identify one of the
> device…” under serial number detection. IN ESSENCE WHAT I UNDERSTAND
> THAT WE CAN REALLY GO ANY FURTHER ON THE TEST PATH, UNLESS IT IS
> RESOLVED, SO disk stress or driver verifier etc are meaningless at that
> point … Under some other machine(s), it does not complain ( same
> identical driver, and inf ) so that yellow bang is not there under any
> of the listed tests that can be hand under the disk category. BUT WHEN I
> RUN THE DRIVER TEST test suite ( ie, it has multiple tests, and
> requiring multiple reboot ), all most always I see there is a delay in
> booting up, and I’m almost sure PnP is trying its best to enumerate the
> devices, so I THINK IT TIMES OUT AND throw-away the driver, and
> eventually boots up, kicks off the remaining test, NOW THE TEST FINDS
> THAT A DEVICE WAS PRESENT AND CONFIGURED FOR THIS SET OF TESTS AND NOW
> GONE …
>
>
> I know I just put a broad coverage, so if I get any guestimate, insight
> that would be great to narrow my search-space !!
>
> -pro
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>

4

Thanks June, It’s been a great help.

As you know that you are cc’ed on all the offline emails.

Ending this thread !

-pro

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of June Blender
(MSFT)
Sent: Tuesday, November 09, 2004 10:46 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] HCT 12.0 Help !

Prokash, I contacted the WHQL Device Testing team on your behalf. Here is
their response:

We’re not sure what you mean by “Psuedo bus.” Is this a virtual device
driver with a root enumerated PnP ID?

Under HCT 11.2, the ACPI Stress version fails and pop ups an error dialog
like ‘can’t find PNP ID’. . This causes a failure in driver verifier and
device path exerciser. See this errata:

http://www.microsoft.com/whdc/hwtest/search/details.aspx?Type=err&ID=1146

Under HCT 12.0 and HCT 12.1, this was fixed, so we are not sure what is
occurring.

Please send the following information to xxxxx@microsoft.com

  1. The exact error you are seeing from the HCT. Please copy and paste or
    re-type the message that you see in the dialog box.

  2. Please provide the plug and play ID of your device and the type of device
    that you are qualifying.

  3. Please provide any failing logs and the names of the tests that are
    failing.

Thanks,
The WHQL Device Testing Team

“Prokash Sinha” wrote in message news:xxxxx@ntdev…
> Further information(s) on it —
>
> Under previous version of HCT ( presumably 11.x ) it did not have this
> problem, with the same binary and inf, so something around the PnP might
> have more stringent checking in the HCT_12.0.
>
> I tried to emulate the reboot ( w/o running the HCT on the machine ) and
> could not find any reason to suspect the driver being getting in the way.
> Everytime it reboots ( again it takes quite a bit of time, this I will
> have
> to narrow in my next test, as observed, it is going power-down path, not
> coming back-up from the reset ), the driver is still in the stack, and
> things are bit better …
>
> So the net would be something like “device pid/vid configuration” and/or
> PnP
> where the driver might not be robust enough as per hct12 …
>
> Any thoughts ?
>
> -pro
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Sinha, Prokash
> Sent: Monday, November 08, 2004 11:03 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] HCT 12.0 Help !
>
>
> Hi All,
>
> I’m running into a situation like this (new to this HCT so might not
> make lot of sense … )—
>
> 1) The driver ( again ) is pseudo-bus type
> 2) Under certain machine(s), when I try to start the test under the disk
> categories, it comes back with “It could not identify one of the
> device…” under serial number detection. IN ESSENCE WHAT I UNDERSTAND
> THAT WE CAN REALLY GO ANY FURTHER ON THE TEST PATH, UNLESS IT IS
> RESOLVED, SO disk stress or driver verifier etc are meaningless at that
> point … Under some other machine(s), it does not complain ( same
> identical driver, and inf ) so that yellow bang is not there under any
> of the listed tests that can be hand under the disk category. BUT WHEN I
> RUN THE DRIVER TEST test suite ( ie, it has multiple tests, and
> requiring multiple reboot ), all most always I see there is a delay in
> booting up, and I’m almost sure PnP is trying its best to enumerate the
> devices, so I THINK IT TIMES OUT AND throw-away the driver, and
> eventually boots up, kicks off the remaining test, NOW THE TEST FINDS
> THAT A DEVICE WAS PRESENT AND CONFIGURED FOR THIS SET OF TESTS AND NOW
> GONE …
>
>
> I know I just put a broad coverage, so if I get any guestimate, insight
> that would be great to narrow my search-space !!
>
> -pro
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@garlic.com
To unsubscribe send a blank email to xxxxx@lists.osr.com