Re: HCT 11.2 Driver Verifier test : Problem in PMTE test

MUX intermediate drivers shouldn't really support any power management
since a MUX IM doesn't directly control any hardware.

For details, see section "Handling Power Management" in the readme of
the DDK's MUX sample:

...\src\network\ndis\mux\driver\mux.htm

However, the MUX sample implements a n-to-1 IM. That is, several
virtual adapters on top of just one physical adapter. Thus, a n-to-1
IM can still forward power (and other) requests to the underlying
miniport.

As described in the readme's "Handling Power Management" section, NDIS
will *always* send power requests *directly* to the miniport that
controls the physical hardware. Thus, it is unnecessary to forward
such requests in a MUX IM.

I guess one can get a better understanding of how things work when
looking at 1-to-n or n-to-n MUX IMs (one or several virtual adapters
on top of several physical adapters). Those IMs cannot "forward" many
requests to underlying miniports because they may all return different
replies. So what should the MUX IM return as the result to NDIS then?

For instance, if some of the miniports underneath the MUX IM support
TCP Checksum Task Offload (CTO) while others don't, what should the IM
tell NDIS when asked if its virtual adapter(s) support CTO?

All that seems important is to return 'NdisDeviceStateUnspecified' for
all of the 'WakeUpCapabilities' requests from a MUX IM. Keep in mind
that any power requests will go *directly* to the hardware
miniport(s). Thus, a MUX IM does not need to bother with these.

Stephan
---
On Sat, 27 Sep 2003 03:31:11 -0700, "Amit Dhaduk"
<> wrote:

>Hi All,
>
> I got a problem during my NDIS Mux Intermediate
>driver testing with HCT 11.2 kit in Driver Verifier Test.
>In this test there is four subtests.
>
>1. NDIS Test
>2. NDIS(IPSec) Test
>3. ACPI S1 Stress Test
>4. Driver Enable/Disable Test
>
>
>NDIS test and NDIS(IPSec) tests are pass. But during ACPT
>Test -it will fail with PMTE test. I attach that log
>below. I use Windows XP OS.
>
>During Driver Verifier test, when execute pm test shell it
>will give error messege:
>
>***************************************
>PMTE failed to init
>Error : DEVICE_TEST_INFOC :: INIT()
>Error : Failed to init Device info
> ***************************************
>For hardware requirement, Is there require S1,S2,S3 or S4
>support in my Hardware Bios. Which way I come to know that
>my motherboard support S1,
>S2,S3 or S4 ? Is there any additional setting require
>related to IP Addres binding with server and test system.
>Now I had prepare my Test setup as per detail
>given in HCT Documentation. Please tell me if there power
>management related setting require.
>
>
> Can you help me if you have any solution for above
>test problem.
>
>Thanks in advance.
>
>Amit Dhaduk
>
>Log ::
>+================================================ ==========
>==========+
> Log header
>+================================================ ==========
>==========+
>
>
>
>===========================================
>VARIATION 1 START
>Start
>
>FAILURE: couldn't find device with PNPID=
>ROOT\MS_MUXMP\0001
>?õwØ5
>
>VARIATION 1:FAIL
>Elapsed Time: Days 0 Hours 0 Minutes 0 Seconds 3
>===========================================
>-----------------------------------------------------------
>---------
>NTLOG REPORT
>-----------------------------------------------------------
>---------
>Tests Total 0 | Variations Total
>1
>-----------------------------------------------------------
>---------
>Tests Passed 0 0 % | Variations Passed
>0 0%
>Tests Warned 0 0 % | Variations Warned
>0 0%
>Tests Failed sev3 0 0 % | Variations Failed sev3
>1 100%
>Tests Failed sev2 0 0 % | Variations Failed sev2
>0 0%
>Tests Failed sev1 0 0 % | Variations Failed sev1
>0 0%
>Tests Blocked 0 0 % | Variations Blocked
>0 0%
>Tests Aborted 0 0 % | Variations Aborted
>0 0%
>-----------------------------------------------------------
>---------