none
Problem using WLK 1.6 with PCIHCT RRS feed

  • Question

  • Hello,

    I'm running WLK/DTM 1.6 for Windows 2008. I have installed
    QFE's 2, 5, and 6 that are currently available with the installation
    package along with the latest filters.

    I am seeing a problem with the test named "PCI Hardware Compliance
    Test For a Single Device (PCIHCT)".

    It seems that when I run the set of tests, I get errors.
    Applying the filters does not cause them to go away.
    Then when I run that test again by itself, it passes. I don't
    know if it is running it the second time that makes it succeed
    or running it without certain other tests running first.

    Nothing substantive has changed with our driver since we
    certified our driver using the WDK/HCK 2.0 or the WLK/DTM
    when that was previously used for testing all Windows versions,
    and I do not recall these problems ever appearing before.

    Looking at the logs, it seems that various errors of these
    sorts occurred (not including all):

    PCI Function @ 0.1E.0
    SSID/SSVID Capability
    PCI Function @ 0.1C.0
    PCI Express Capability
    ...

    I realize that we can probably get by by just rerunning the
    test, since that seems to work, but it would be nice to understand
    the reason for the failure.

    Thanks,
    Nathan

    Friday, November 1, 2013 6:17 PM

All replies

  • Can you print more specific errors? Also does this when running after tests where the device is enabled/disabled/re-enumerated?  This may be a known issue from that kit if i remember correctly...

    This posting is provided "AS IS" with no warranties, and confers no rights

    Friday, November 1, 2013 7:18 PM
  • Thanks for your reply, gerogek.

    > Can you print more specific errors?

    If I could send you the .CPK file, it would be much easier than trying to put the errors in a forum message. Or is there a way to attach files to forum messages?

    Anyway, here are the first several:


    PCI Function @ 0.1E.0
    [No specific error noted within this one. It just said Failed, perhaps referring to the next one]

    SSID/SSVID Capability
    Error 10/31/2013 10:25:11.883 PM Assertion B576282C-5C66-4253-A275-257F5D49EFEF: FAILED. SSVID register of the Subsystem ID and Subsystem Vendor ID Capability table cannot have a value of 0h .
    File:   <Unspecified file> Line: 0
    Error Type:   NT_STATUS
    Error Code:   0xc0000420
    Error Text:   Error 0xc0000420


    PCI Function @ 0.1C.0
    [No specific error noted within this one. It just said Failed, perhaps referring to the next one]

    PCI Express Capability
    Warning 10/31/2013 10:25:11.883 PM Assertion A69B656D-73A9-4924-824B-C4A32D49BFE1: Failed with a WARNING. Bit 8 (Extended Tag Field Enable) in the Device Control register (offset 8h) in the PCI Express Capability table must be read-writable if Extended Tag Field Support is indicated.
    File:   <Unspecified file> Line: 0
    Error 10/31/2013 10:25:11.883 PM Assertion 1E2C30DD-F627-44B1-8E49-B88F4F84BDA2: FAILED. Bit 20 (Data Link Layer Link Active Reporting Capable) in the Link Capabilities register (offset Ch) in the PCI Express Capability table has an initial value of 0h. It must be 1h for hot-plug capable downstream ports and root ports..
    File:   <Unspecified file> Line: 0
    Error Type:   NT_STATUS
    Error Code:   0xc0000420
    Error Text:   Error 0xc0000420


    PCI Function @ 0.7.0
    [No specific error noted within this one. It just said Failed, perhaps referring to the next one]

    SSID/SSVID Capability
    Error 10/31/2013 10:25:11.883 PM Assertion 7A5587BC-5646-4DC4-9A5D-22F85AB2204E: FAILED. PCI Express ports and bridges must implement Subsystem ID and Subsystem Vendor ID Capability.
    File:   <Unspecified file> Line: 0
    Error Type:   NT_STATUS
    Error Code:   0xc0000420
    Error Text:   Error 0xc0000420

    PCI Express Capability
    Error 10/31/2013 10:25:11.883 PM Assertion 0E36472A-0EDB-4685-A67D-7AF1FFBFA81B: FAILED. Data Link Layer Link Active Reporting Capable bit is set but Data Link Layer Link Active is not.
    File:   <Unspecified file> Line: 0
    Error Type:   NT_STATUS
    Error Code:   0xc0000420
    Error Text:   Error 0xc0000420
    Error 10/31/2013 10:25:11.883 PM Assertion E82AA9DF-B698-4035-B9F2-8497CC16AEFA: FAILED. Bit 12 (Data Link Layer State Changed Enable) in the Slot Control register (offset 18h) in the PCI Express Capability table must be read-writable .
    File:   <Unspecified file> Line: 0
    Error Type:   NT_STATUS
    Error Code:   0xc0000420
    Error Text:   Error 0xc0000420

    Message Signaled Interrupts Capability
    Error 10/31/2013 10:25:11.883 PM Assertion DDC8A893-6F85-4D69-BC79-874BA52E0A02: FAILED. Bit range 31:2 (Message Address)in the Message Address register (offset 4h) in the MSI Capability table must be read-writable .
    File:   <Unspecified file> Line: 0
    Error Type:   NT_STATUS
    Error Code:   0xc0000420
    Error Text:   Error 0xc0000420


    And there are many, many more.

    > Also does this when running after tests where the device
    > is enabled/disabled/re-enumerated?  This may be a known
    > issue from that kit if i remember correctly...

    I don't know. Which specific tests would that be? I can try it.

    If it is a known issue, is there anything that can be done other than to be sure to run the tests in a specific order?

    Thanks,
    Nathan

    Friday, November 1, 2013 8:14 PM