[nvmewin] WHQL test issues

Mon Jan 9 21:06:16 PST 2017

You need to manually install the instrumented stornvme.sys driver before that specific test runs. The driver should already be in the drivers directory. It just needs to be installed.

-------- Original message --------
From: 許銘洲 <joe_mchsu at phison.com>
Date: 1/9/17 8:31 PM (GMT-07:00)
To: "Robles, Raymond C" <raymond.c.robles at intel.com>
Cc: nvmewin at lists.openfabrics.org
Subject: RE: WHQL test issues

Hi Ray,
     I got it, thank you. Can you provide the manual errata steps to me please? Because we want to develop some tools with the signed OFA nvme driver on windows 81 and HLK only sign for windows 10 driver.
Thank you for your patience.
Joe
From: Robles, Raymond C [mailto:raymond.c.robles at intel.com]
Sent: Tuesday, January 10, 2017 6:14 AM
To: 許銘洲
Cc: nvmewin at lists.openfabrics.org
Subject: RE: WHQL test issues

Hello… I was able to talk to our local MSFT certification expert and get some additional info.

He basically said that there are specific NVMe test cases that are designed to run with an instrumented version of stornvme.sys and a shim driver (these are provided by MSFT).

There are defects in the test cases in the HCK impacting Win 8.1 and Server 2012 R2.  Basically, MSFT does a copy of the instrumented stornvme driver to the windows\system32\drivers directory but never performs any action to update the driver actually installed/running for the NVMe controller under test.  Third party driver(s) remain installed/running, and the test shim driver cannot communicate with anything but the instrumented driver and reports errors.

Intel and other companies have previously had manual errata for this, but since have had permission from MSFT to manually install stornvme prior to the impacted test cases so that the test cases run correctly.

In the HLK (Win10 and Server 2016), this test defect has been corrected and stornvme is installed during test setup activities.

Please attempt a retest with the latest HLK Win10 and Server 2016.

Thanks…
Ray

From: 許銘洲 [mailto:joe_mchsu at phison.com]
Sent: Sunday, January 08, 2017 8:58 PM
To: Robles, Raymond C <raymond.c.robles at intel.com>
Cc: nvmewin at lists.openfabrics.org
Subject: RE: WHQL test issues

Sorry, it looks like attachment be blocked. I attach the error message log below.

NVMe Queue Utilization Test Log:
Machine: Build=9200.00
        Platform=AMD64
        OS=Windows 8.1 Pro
        ServicePack=""
        Version=6.3
        BuildLab="winblue_r4"
        BuildDate=141028-1500
        Language=Chinese (Traditional) (REDMOND)
        Config=n/a

Start: Parse command line arguments, TUID=
End: Pass, Parse command line arguments, TUID=, Repro=nvmeshim.exe  /DriveNumber 1 /DriveLetter D: /operation QueueUtilization /scenario All /verbosity 4 /Duration 300

Start: Creating Operation, TUID=
Obtained scenario handle
HWID: SCSI\DiskNVMe____PCIe_SSD________02.1
End: Pass, Creating Operation, TUID=, Repro=nvmeshim.exe  /DriveNumber 1 /DriveLetter D: /operation QueueUtilization /scenario All /verbosity 4 /Duration 300

Start: IO Workload with Queue Statistics, TUID=
Description: Run multithreaded IO workload, check for Queue utilization
Expectation: Device should be able to utilize all the queue slots for IO
#Workload instances: 1
Disk Size in bytes =  37e4618200
Waiting for drive to be cleared up...
Instantiating 1 workload threads
Workload app string: diskio.exe /d D: /c sw;rw /b 512KB /t 300 /q 66 /s 200GB /v /uniquelogname /f
Launching workload threads...
Output file: Scenario1WorkloadInstance0.out
Set affinity of workload threads...
Error: 0x0, Error 0x00000000
        Failed to send IOCTL to SHIM, GLE = 0x2
        File=testsrc\driverstest\storage\wdk\nvme\queue.cpp Line=446
End: Fail, IO Workload with Queue Statistics, TUID=, Repro=nvmeshim.exe  /DriveNumber 1 /DriveLetter D: /operation QueueUtilization /scenario All /verbosity 4 /Duration 300

Start: IO Workload with Queue Statistics, TUID=
Description: Run multithreaded IO workload, check for Queue utilization
Expectation: Device should be able to utilize all the queue slots for IO
#Workload instances: 4
Disk Size in bytes =  37e4618200
Waiting for drive to be cleared up...
Instantiating 4 workload threads
Workload app string: diskio.exe /d D: /c sw;rw /b 512KB /t 300 /q 66 /s 49GB /v /uniquelogname /f
Workload app string: diskio.exe /d D: /c sw;rw /b 512KB /t 300 /q 66 /s 49GB /v /uniquelogname /f
Workload app string: diskio.exe /d D: /c sw;rw /b 512KB /t 300 /q 66 /s 49GB /v /uniquelogname /f
Workload app string: diskio.exe /d D: /c sw;rw /b 512KB /t 300 /q 66 /s 49GB /v /uniquelogname /f
Launching workload threads...
Output file: Scenario2WorkloadInstance0.out
Output file: Scenario2WorkloadInstance1.out
Output file: Scenario2WorkloadInstance2.out
Output file: Scenario2WorkloadInstance3.out
Set affinity of workload threads...
Error: 0x0, Error 0x00000000
        Failed to send IOCTL to SHIM, GLE = 0x2
        File=testsrc\driverstest\storage\wdk\nvme\queue.cpp Line=446
End: Fail, IO Workload with Queue Statistics, TUID=, Repro=nvmeshim.exe  /DriveNumber 1 /DriveLetter D: /operation QueueUtilization /scenario All /verbosity 4 /Duration 300

Summary: Total=4, Passed=2, Failed=2, Blocked=0, Warned=0, Skipped=0
===============================================================================================================================================

NVMe Device Capabilities Test log:
Machine: Build=9200.00
        Platform=AMD64
        OS=Windows 8.1 Pro
        ServicePack=""
        Version=6.3
        BuildLab="winblue_r4"
        BuildDate=141028-1500
        Language=Chinese (Traditional) (REDMOND)
        Config=n/a

Start: Parse command line arguments, TUID=
End: Pass, Parse command line arguments, TUID=, Repro=nvmeshim.exe  /DriveNumber 1 /DriveLetter D: /operation CapabilitiesVerification /scenario All /verbosity 4 /Duration 300

Start: Creating Operation, TUID=
Obtained scenario handle
HWID: SCSI\DiskNVMe____PCIe_SSD________02.1
End: Pass, Creating Operation, TUID=, Repro=nvmeshim.exe  /DriveNumber 1 /DriveLetter D: /operation CapabilitiesVerification /scenario All /verbosity 4 /Duration 300

Start: Assertion: Controller Capabilities, TUID=
Description: This assertion validates values in Controller Capabilities register
Expectation: Controller has spec compliant values along with Windows Host requirements. For further details, please check Chapters 3, 5 of NVMe spec along with Windows HCK Requirements and test documentation
Error: 0x0, Error 0x00000000
        Failed to send IOCTL to SHIM, GLE = 0x2
        File=testsrc\driverstest\storage\wdk\nvme\capabilities.cpp Line=58
End: Fail, Assertion: Controller Capabilities, TUID=, Repro=nvmeshim.exe  /DriveNumber 1 /DriveLetter D: /operation CapabilitiesVerification /scenario All /verbosity 4 /Duration 300

Start: Assertion: Controller Version, TUID=
Description: This assertion validates values in Controller Version register
Expectation: Controller has spec compliant values along with Windows Host requirements. For further details, please check Chapters 3, 5 of NVMe spec along with Windows HCK Requirements and test documentation
Error: 0x0, Error 0x00000000
        Failed to send IOCTL to SHIM, GLE = 0x2
        File=testsrc\driverstest\storage\wdk\nvme\capabilities.cpp Line=107
End: Fail, Assertion: Controller Version, TUID=, Repro=nvmeshim.exe  /DriveNumber 1 /DriveLetter D: /operation CapabilitiesVerification /scenario All /verbosity 4 /Duration 300

Start: Assertion: Controller Configuration, TUID=
Description: This assertion validates values in Controller Configuration register
Expectation: Controller has spec compliant values along with Windows Host requirements. For further details, please check Chapters 3, 5 of NVMe spec along with Windows HCK Requirements and test documentation
Error: 0x0, Error 0x00000000
        Failed to send IOCTL to SHIM, GLE = 0x2
        File=testsrc\driverstest\storage\wdk\nvme\capabilities.cpp Line=138
End: Fail, Assertion: Controller Configuration, TUID=, Repro=nvmeshim.exe  /DriveNumber 1 /DriveLetter D: /operation CapabilitiesVerification /scenario All /verbosity 4 /Duration 300

Start: Assertion: Controller Identify Data, TUID=
Description: This assertion validates values in Identify Data register
Expectation: Controller has spec compliant values along with Windows Host requirements. For further details, please check Chapters 3, 5 of NVMe spec along with Windows HCK Requirements and test documentation
Error: 0x0, Error 0x00000000
        Failed to send IOCTL to SHIM, GLE = 0x2
        File=testsrc\driverstest\storage\wdk\nvme\capabilities.cpp Line=168
End: Fail, Assertion: Controller Identify Data, TUID=, Repro=nvmeshim.exe  /DriveNumber 1 /DriveLetter D: /operation CapabilitiesVerification /scenario All /verbosity 4 /Duration 300

Start: Assertion: Controller Identify Namespace Data, TUID=
Description: This assertion validates values in Identify Namespace Data
Expectation: Controller has spec compliant values along with Windows Host requirements. For further details, please check Chapters 3, 5 of NVMe spec along with Windows HCK Requirements and test documentation
End: Pass, Assertion: Controller Identify Namespace Data, TUID=, Repro=nvmeshim.exe  /DriveNumber 1 /DriveLetter D: /operation CapabilitiesVerification /scenario All /verbosity 4 /Duration 300

Summary: Total=7, Passed=3, Failed=4, Blocked=0, Warned=0, Skipped=0

============================================================================================================================

Thanks,
           Joe

From: 許銘洲
Sent: Monday, January 09, 2017 11:48 AM
To: 'Robles, Raymond C'
Cc: nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: RE: WHQL test issues

Attachment zip include HCK package and testing 1.5 nvme driver.
I use the IOCTL_Sample_App on website, It send Identify command and it’s work.
[cid:image001.png at 01D26B32.4EE9AEC0]

Thanks,
           Joe
From: Robles, Raymond C [mailto:raymond.c.robles at intel.com]
Sent: Monday, January 09, 2017 10:17 AM
To: 許銘洲
Cc: nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: RE: WHQL test issues

Sure. Could you send a full characterization of the failure please?

We'll need full details of the failure in order to help out. Have you tried sending normal IOCTLS to the driver?

Thanks...
Ray

-------- Original message --------
From: 許銘洲 <joe_mchsu at phison.com<mailto:joe_mchsu at phison.com>>
Date: 1/8/17 6:40 PM (GMT-07:00)
To: "Robles, Raymond C" <raymond.c.robles at intel.com<mailto:raymond.c.robles at intel.com>>
Cc: nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: RE: WHQL test issues

Hi Ray,
     Thank you for your reply. The test device is our company nvme PS-5007 device, it is already publicly available. I tried recent 1.5 version nvme driver, but the error situation is same.  However, I use Microsoft original NVME standard driver in windows 8.1,“Nvme Device Capabilities Test” and “Nvme Queue Utilization Test” are pass. Do you have any idea to help me solve this problem?
Thanks,
            Joe

From: Robles, Raymond C [mailto:raymond.c.robles at intel.com]
Sent: Friday, January 06, 2017 2:28 AM
To: 許銘洲
Cc: nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: RE: WHQL test issues

Hi Joe,

I’m unaware of any issues with WHCK for our OFA reference driver. All driver revisions released have passed WHCK testing. A couple of questions for you:

*         Which NVMe device are you using to test? All testing completed has been done on production drives from Intel, Samsung, or PMC-Sierra. If you are using a pre-production NVMe product, it will be difficult to root cause without full access to H/W and F/W on the NVMe device.

*         Have you tried running on a publicly available NVMe device?

*         Have you tried the recent 1.5 release driver?

In addition to the questions above, I see that you are not currently subscribed to the nvmewin email list. Please go and subscribe to this list so that I do not have to approve all your messages individually to be sent to the community email distribution. Here is the link…

https://www.openfabrics.org/index.php/working-groups-overview.html#nvmewin

Thanks…
Ray

From: nvmewin [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of ???
Sent: Thursday, January 05, 2017 1:57 AM
To: nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: [nvmewin] WHQL test issues

Hi,
  I use Windows HCK 2.1 to test nvme driver which download from openfabrics svn revision_1.4/64 bit/windows81 . I get error messages when I test “Nvme Device Capabilities Test” and “Nvme Queue Utilization Test” items.
Error message show “failed to send IOCTL to SHIM, GLE =0x2”. The test pc platform is windows 8.1 64bit.
Is this issue related with nvme driver ?
Thank you for your help~
                   Joe

This message and any attachments are confidential and may be legally privileged. Any unauthorized review, use or distribution by anyone other than the intended recipient is strictly prohibited. If you are not the intended recipient, please immediately notify the sender, completely delete the message and any attachments, and destroy all copies. Your cooperation will be highly appreciated.

This message and any attachments are confidential and may be legally privileged. Any unauthorized review, use or distribution by anyone other than the intended recipient is strictly prohibited. If you are not the intended recipient, please immediately notify the sender, completely delete the message and any attachments, and destroy all copies. Your cooperation will be highly appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20170110/2f35d77d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 102607 bytes
Desc: image001.png
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20170110/2f35d77d/attachment.png>