[nvmewin] OFA reference driver release assistance

Robles, Raymond C raymond.c.robles at intel.com
Thu Sep 22 16:12:15 PDT 2016


Thanks Tom.

Question... do you think you can push a fix for this failure?

Thanks...
Ray

From: Tom Freeman [mailto:thomas.freeman at hgst.com]
Sent: Wednesday, September 21, 2016 1:48 PM
To: Robles, Raymond C <raymond.c.robles at intel.com>; nvmewin <nvmewin at lists.openfabrics.org>
Subject: RE: OFA reference driver release assistance

In my previous test, I incorrectly used the HLK version of scsicompliance.exe.
I reran the test with the HCK version of scsicompliance.exe (version 2.0.20100428)

I'm attaching the files with the complete results - password "nvmeOFA15"

For 2012 and 2012R2, the command was:
scsicompliance  /device \\.\physicaldrive1<file:///\\.\physicaldrive1> /verbosity 4 /scenario nvme /operation test /version 2

For 2008R2 the command was:
scsicompliance  /device \\.\PhysicalDrive2<file:///\\.\PhysicalDrive2> /verbosity 4 /scenario common /operation test /version 2


2008R2 passed
2012 and 2012r2 had a similar failure as reported with the HLK version of the test.
Here are the details of that failure:

Policy: REQUIRED
Start: ASSERTION: INQUIRY Attempting Unit Serial Number Page 0x80., TUID=
Description: Checking if Unit Serial Number Page 0x80 is supported
Reference: SCSI Primary Commands - 4 (SPC-4) Revision 30 (or published) specification Section 7.8.15 http://www.t10.org/ftp/t10/drafts/spc4/spc4r30.pdf
Expectation: Device returns meaningful data as defined in SCSI-NVME translation document
Sending SCSI command to device.

INQUIRY Command:
12 01 80 00 ff 00
DeviceIoControl SUCCEEDED.

SCSI status: 0x00
    (GOOD)
Sense bytes: 0x00
Data bytes:  0x2c
      00       04        08       0C
      ---------------------------------------------------------------
000  00800028 30303030  5F303030 305F3030    ...(0000_0000_00
010  30305F30 3030305F  30303043 5F434130    00_0000_000C_CA0
020  305F3630 31465F42  4230302E 00000000    0_601F_BB00.....
== DONE ==============================================================
INQUIRY: Unit serial number page is supported.
"Peripheral Qualifier" = 0x0
"Peripheral Device Type" = 0x0
"Page Code" = 0x80
"Page Length" = 0x28
"Unit serial number page length shall be set to 20"
Error: 0x0, Error 0x00000000
       Logging an error
       File=testsrc\driverstest\storage\wdk\scsicompliance\lib\core\policyscenario.cpp Line=213
End: Fail, ASSERTION: INQUIRY Attempting Unit Serial Number Page 0x80., TUID=, Repro=scsicompliance  /device \\.\physicaldrive1<file:///\\.\physicaldrive1> /verbosity 4 /scenario nvme /operation test /version 2


Tom Freeman
Software Engineer, Device Manager and Driver Development
Western Digital Corporation
e.  Thomas.freeman at hgst.com<mailto:Thomas.freeman at hgst.com>
o.  +1-507-322-2311

[cid:image001.jpg at 01D214EC.13F5D100]

From: Robles, Raymond C [mailto:raymond.c.robles at intel.com]
Sent: Tuesday, September 20, 2016 4:29 PM
To: Tom Freeman <thomas.freeman at hgst.com<mailto:thomas.freeman at hgst.com>>; nvmewin <nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>>
Cc: Huffman, Amber <amber.huffman at intel.com<mailto:amber.huffman at intel.com>>
Subject: RE: OFA reference driver release assistance

Hi Tom,

This is awesome. Thank you very much for completing this testing. I'm adding it to a test spreadsheet I'm maintaining.

On the failure below, I'll log the 40 length expectation by the test. BTW, can you provide the MS SCSI compliance command line you used to run the test? As well as the version?

Thanks again!
Ray

From: Tom Freeman [mailto:thomas.freeman at hgst.com]
Sent: Tuesday, September 20, 2016 11:59 AM
To: Robles, Raymond C <raymond.c.robles at intel.com<mailto:raymond.c.robles at intel.com>>; nvmewin <nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>>
Cc: Huffman, Amber <amber.huffman at intel.com<mailto:amber.huffman at intel.com>>
Subject: RE: OFA reference driver release assistance

I've completed my testing for the 1.5 release
All the testing was successful.
There was a single failure in the Scsi Compliance (details at the end of the note). Filter 10700 overrides this on Server 2016 HLK testing.
I was not able to verify that filter on HCK on 2008R2, 2012 and 2012R2.

Testing details:
64-bit on 2008R2, 2012 and 2012R2

1 hour of data integrity testing using sdstress
1 hour of heavy stress testing using IOMETER covering, at least, 512B, 4KB and 128KB ranging from 1 OIO to 64 OIO both sequential and random
Quick and slow format of both MBR and GPT partitioning
Microsoft SCSI Compliance.


Scsi Compliance Failure:
Policy: REQUIRED
Start: ASSERTION: INQUIRY Attempting Unit Serial Number Page 0x80., TUID=
Description: Checking if Unit Serial Number Page 0x80 is supported
Reference: SCSI Primary Commands - 4 (SPC-4) Revision 30 (or published) specification Section 7.8.15 http://www.t10.org/ftp/t10/drafts/spc4/spc4r30.pdf
Expectation: Device returns meaningful data as defined in SCSI-NVME translation document
Sending SCSI command to device.
INQUIRY Command:
12 01 80 00 ff 00
DeviceIoControl SUCCEEDED.
SCSI status: 0x00
    (GOOD)
Sense bytes: 0x00
Data bytes:  0x2c

      00       04        08       0C
      ---------------------------------------------------------------
000  00800028 30303030  5F303030 305F3030    ...(0000_0000_00
010  30305F30 3030305F  30303043 5F434130    00_0000_000C_CA0
020  305F3630 31465F42  4230302E 00000000    0_601F_BB00.....
== DONE ==============================================================
INQUIRY: Unit serial number page is supported.
"Peripheral Qualifier" = 0x0
"Peripheral Device Type" = 0x0
"Page Code" = 0x80
Error: 0x0, Error 0x00000000
       Unit serial number page length shall be set to either 20 for EUI64 or 36 for NGUID. Actual=40
       File=drivers\storage\tests\scsicompliance\lib\nvme\inquiry_nvme.cpp Line=120
Error: 0x0, Error 0x00000000
       Logging an error
       File=drivers\storage\tests\scsicompliance\lib\core\policyscenario.cpp Line=213
End: Fail, ASSERTION: INQUIRY Attempting Unit Serial Number Page 0x80., TUID=, Repro=scsicompliance  /device \\.\PhysicalDrive1<file:///\\.\PhysicalDrive1> /verbosity 4 /scenario NVMe /Operation test /Version 2




Tom Freeman
Software Engineer, Device Manager and Driver Development
Western Digital Corporation
e.  Thomas.freeman at hgst.com<mailto:Thomas.freeman at hgst.com>
o.  +1-507-322-2311

[cid:image006.jpg at 01D2141E.ACAFEA30]

From: Tom Freeman
Sent: Monday, September 12, 2016 11:49 AM
To: 'Robles, Raymond C' <raymond.c.robles at intel.com<mailto:raymond.c.robles at intel.com>>; nvmewin <nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>>
Cc: Huffman, Amber <amber.huffman at intel.com<mailto:amber.huffman at intel.com>>
Subject: RE: OFA reference driver release assistance

I can run the Unit testing test for 64-bit on 2008R2, 2012 and 2012R2

These are the unit tests I'll run:
-          1 hour of data integrity testing using sdstress (Microsoft Tool)
-          1 hour of heavy stress testing using IOMETER covering, at least, 512B, 4KB and 128KB ranging from 1 OIO to 64 OIO both sequential and random
-          Quick and slow format of both MBR and GPT partitioning
-          Microsoft SCSI Compliance, no failures except (warnings OK)


Tom Freeman
Software Engineer, Device Manager and Driver Development
Western Digital Corporation
e.  Thomas.freeman at hgst.com<mailto:Thomas.freeman at hgst.com>
o.  +1-507-322-2311

[cid:image007.jpg at 01D2141E.ACAFEA30]

From: nvmewin [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Robles, Raymond C
Sent: Friday, September 9, 2016 12:47 PM
To: nvmewin <nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>>
Cc: Huffman, Amber <amber.huffman at intel.com<mailto:amber.huffman at intel.com>>
Subject: [nvmewin] OFA reference driver release assistance

Hello,

In order to officially release the OFA reference driver, there are some tests that need to be run. I'm asking for volunteers for run the following tests:


*         WHQL/WHCK Certification Tests (no submission to MS required... just need test results)

*         Normal Unit Testing Test Suite

The only requirements for devices on which to run the above tests is that the NVMe SSD be 1.2 compliant. As additional info, here is a list of features that we've added since our last release. Please review and sanity check my list.

Recent patches include

*         Performance improvement & robustness

*         NVMe Spec rev 1.2 feature compliant

*         Supports MS Windows 10, 8.1, 7, Server 2012 R2, 2012 and 2008 R2

*         Supports both 32 & 64-bit

*         What is new since last release:

o   Namespace Management (Create, Delete, Attach, Detach)

o   EOL Read Only Support

o   Win 8.1 Timers

o   Surprise Removal Support in IOCTL Path

o   Disk Initialization Performance Optimization

o   Storage Request Block Support

o   StorPort Performance Options

o   StorPort DPC Redirection

o   Misc. Bug Fixes

o   Security Send/Receive with Zero Data Length

o   SNTI updates for SCSI to NVMe Translation

Thanks...
Ray

Raymond C. Robles
NSG ISE Host Storage Software
Intel Corporation
Office: 480-554-2600
Mobile: 480-399-0645
raymond.c.robles at intel.com<mailto:raymond.c.robles at intel.com>

[cid:image001.gif at 01CB9B29.EA8D14F0]

Western Digital Corporation (and its subsidiaries) E-mail Confidentiality Notice & Disclaimer:
This e-mail and any files transmitted with it may contain confidential or legally privileged information of WDC and/or its affiliates, and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.
Western Digital Corporation (and its subsidiaries) E-mail Confidentiality Notice & Disclaimer:
This e-mail and any files transmitted with it may contain confidential or legally privileged information of WDC and/or its affiliates, and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160922/989b8d3e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2938 bytes
Desc: image001.jpg
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160922/989b8d3e/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 2934 bytes
Desc: image002.jpg
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160922/989b8d3e/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 2937 bytes
Desc: image003.jpg
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160922/989b8d3e/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 1568 bytes
Desc: image004.jpg
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20160922/989b8d3e/attachment-0003.jpg>


More information about the nvmewin mailing list