We’ve been working on WHLK’ing Wintun on 1903. We have pretty easy success doing so on 1809 and prior builds, but on 1903, we’ve run into snags. After considerable amount of time trying to debug this, we decided to run the same failing tests on the fairly battle-tested “Intel(R) PRO/1000 MT Desktop Adapter” driver, and to our surprise, this also failed. The tests in question are:
- DF - Fuzz zero length buffer IOCTL test (Reliability)
- DF - Concurrent Hardware And Operating System (CHAOS) Test (Development and Integration)
They seem to get hung up around surprise removal, eventually resulting in something like:
WDTF_TARGETS : INFO : - Query("IsPhantom=False AND ((DeviceID='PCI\VEN_8086&DEV_100E&SUBSYS_001E8086&REV_02\3&267A616A&0&18' OR HardwareIDs='PCI\VEN_8086&DEV_100E&SUBSYS_001E8086&REV_02'))")
WDTF_TARGETS : INFO : Target: Intel(R) PRO/1000 MT Desktop Adapter PCI\VEN_8086&DEV_100E&SUBSYS_001E8086&REV_02\3&267A616A&0&18
WDTF_TEST : ERROR : Found a device that has a non-zero problem code or is phantom. Logging device info.
WDTF_TEST : INFO : DeviceID: PCI\VEN_8086&DEV_100E&SUBSYS_001E8086&REV_02\3&267A616A&0&18
WDTF_TEST : INFO : DisplayName: Intel(R) PRO/1000 MT Desktop Adapter
WDTF_TEST : INFO : Status: 25175296
WDTF_TEST : INFO : IsPhantom: FALSE
WDTF_TEST : INFO : ProblemCode: 43
WDTF_TEST : INFO : Rebooting the system.
I’m interested to learn if anybody else is seeing this with various NDIS Miniport drivers on 1903. In some cursory searches on the Internet, I haven’t come across much, but 1903 is also relatively new.