From jhwang at marvell.com Mon Apr 6 21:30:30 2015 From: jhwang at marvell.com (Jinghai Wang) Date: Mon, 6 Apr 2015 21:30:30 -0700 Subject: [nvmewin] NVMe Windows driver Message-ID: <91A41E78C4F4444BBD1EB4198A7B9C4FB527CDE014@SC-VEXCH2.marvell.com> Hi All, I'm looking for a NVMe windows driver open source. I didn't find it at http://git.openfabrics.org/, who can tell me where I can find it? Thanks in advance. Regards, Jinghai -------------- next part -------------- An HTML attachment was scrubbed... URL: From raymond.c.robles at intel.com Tue Apr 7 13:15:51 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Tue, 7 Apr 2015 20:15:51 +0000 Subject: [nvmewin] NVMe Windows driver In-Reply-To: <91A41E78C4F4444BBD1EB4198A7B9C4FB527CDE014@SC-VEXCH2.marvell.com> References: <91A41E78C4F4444BBD1EB4198A7B9C4FB527CDE014@SC-VEXCH2.marvell.com> Message-ID: <49158E750348AA499168FD41D88983606B632662@fmsmsx117.amr.corp.intel.com> Hi Jinghai, The link to the OFA driver is at the following link below. You can browse the source through your internet browser, or use a SVN client to access the code. Directions are on the page. https://www.openfabrics.org/index.php/resources/developer-tools/nvme-windows-development.html NOTE: Currently, the website is down. I've contacted the OFA administrator to inform them. Thanks, Ray From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Jinghai Wang Sent: Monday, April 06, 2015 9:31 PM To: nvmewin at lists.openfabrics.org Subject: [nvmewin] NVMe Windows driver Hi All, I'm looking for a NVMe windows driver open source. I didn't find it at http://git.openfabrics.org/, who can tell me where I can find it? Thanks in advance. Regards, Jinghai -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhwang at marvell.com Tue Apr 7 18:26:26 2015 From: jhwang at marvell.com (Jinghai Wang) Date: Tue, 7 Apr 2015 18:26:26 -0700 Subject: [nvmewin] =?gb2312?b?tPC4tDogTlZNZSBXaW5kb3dzIGRyaXZlcg==?= In-Reply-To: <49158E750348AA499168FD41D88983606B632662@fmsmsx117.amr.corp.intel.com> References: <91A41E78C4F4444BBD1EB4198A7B9C4FB527CDE014@SC-VEXCH2.marvell.com> <49158E750348AA499168FD41D88983606B632662@fmsmsx117.amr.corp.intel.com> Message-ID: <91A41E78C4F4444BBD1EB4198A7B9C4FB527CDE310@SC-VEXCH2.marvell.com> Hi Ray, Thanks for your info. I didn’t find the release in the site which you provided. And finally, I goggled the correct site is https://svn.openfabrics.org/svnrepo/nvmewin/releases/, and the latest build version is R1.4 now. Regards, Jinghai 发件人: Robles, Raymond C [mailto:raymond.c.robles at intel.com] 发送时间: Wednesday, April 08, 2015 4:16 AM 收件人: Jinghai Wang; nvmewin at lists.openfabrics.org 主题: RE: NVMe Windows driver Hi Jinghai, The link to the OFA driver is at the following link below. You can browse the source through your internet browser, or use a SVN client to access the code. Directions are on the page. https://www.openfabrics.org/index.php/resources/developer-tools/nvme-windows-development.html NOTE: Currently, the website is down. I’ve contacted the OFA administrator to inform them. Thanks, Ray From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Jinghai Wang Sent: Monday, April 06, 2015 9:31 PM To: nvmewin at lists.openfabrics.org Subject: [nvmewin] NVMe Windows driver Hi All, I’m looking for a NVMe windows driver open source. I didn’t find it at http://git.openfabrics.org/, who can tell me where I can find it? Thanks in advance. Regards, Jinghai -------------- next part -------------- An HTML attachment was scrubbed... URL: From raymond.c.robles at intel.com Tue Apr 7 18:47:09 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Wed, 8 Apr 2015 01:47:09 +0000 Subject: [nvmewin] NVMe Windows driver In-Reply-To: <91A41E78C4F4444BBD1EB4198A7B9C4FB527CDE310@SC-VEXCH2.marvell.com> References: <91A41E78C4F4444BBD1EB4198A7B9C4FB527CDE014@SC-VEXCH2.marvell.com> <49158E750348AA499168FD41D88983606B632662@fmsmsx117.amr.corp.intel.com> <91A41E78C4F4444BBD1EB4198A7B9C4FB527CDE310@SC-VEXCH2.marvell.com> Message-ID: <49158E750348AA499168FD41D88983606B632E58@fmsmsx117.amr.corp.intel.com> Hi Jinghai, Yes, this link takes you directly to the source that can be browsed via your web browser. As I mentioned in my response below, the OFA site is down right now, and only certain pages work. The OFA website admins are working on porting to a new web address. You found one of the working links. The port of the OFA website is about 90% complete, and I’m in the process of reviewing all the NVMe Windows driver information for correctness. Please expect the website to be back up in the next week or so. Again, the link I provided below will have more complete information. If the address of our OFA NVMe Windows driver changes, then I’ll update this distribution list with the new address. Thanks, Ray From: Jinghai Wang [mailto:jhwang at marvell.com] Sent: Tuesday, April 07, 2015 6:26 PM To: Robles, Raymond C; nvmewin at lists.openfabrics.org Subject: 答复: NVMe Windows driver Hi Ray, Thanks for your info. I didn’t find the release in the site which you provided. And finally, I goggled the correct site is https://svn.openfabrics.org/svnrepo/nvmewin/releases/, and the latest build version is R1.4 now. Regards, Jinghai 发件人: Robles, Raymond C [mailto:raymond.c.robles at intel.com] 发送时间: Wednesday, April 08, 2015 4:16 AM 收件人: Jinghai Wang; nvmewin at lists.openfabrics.org 主题: RE: NVMe Windows driver Hi Jinghai, The link to the OFA driver is at the following link below. You can browse the source through your internet browser, or use a SVN client to access the code. Directions are on the page. https://www.openfabrics.org/index.php/resources/developer-tools/nvme-windows-development.html NOTE: Currently, the website is down. I’ve contacted the OFA administrator to inform them. Thanks, Ray From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Jinghai Wang Sent: Monday, April 06, 2015 9:31 PM To: nvmewin at lists.openfabrics.org Subject: [nvmewin] NVMe Windows driver Hi All, I’m looking for a NVMe windows driver open source. I didn’t find it at http://git.openfabrics.org/, who can tell me where I can find it? Thanks in advance. Regards, Jinghai -------------- next part -------------- An HTML attachment was scrubbed... URL: From raymond.c.robles at intel.com Thu Apr 9 17:29:00 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Fri, 10 Apr 2015 00:29:00 +0000 Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers Message-ID: <49158E750348AA499168FD41D88983606B63477F@fmsmsx117.amr.corp.intel.com> All, As we enter Q2, I'm happy to announce that we a have a very good feature plan in place for both Q2 and Q4 releases in 2015 of the OFA driver. The list of requested features is included below for final review. I would like to formally ask for volunteers for patch submissions. As of today, there are no volunteers for any of the below patches. Intel would like to start with the volunteering... we will volunteer to provide the namespace management patch. 2015 Release #1 (Q2/Q3 - 2015) Feature Description Submitter Date Concurrent Channels Start I/O Concurrent Channels allows StartIo to be called in parallel resulting in improved IOPS. Perf Opts Instead of learning cores, use perf opts. Shave off 2 seconds in init code... using Storport initialize perf opts. No need for source core interrupt steering code in driver. Win 8.1 Timers Storport Notification usage. Hot plug and IOCTLs, this does not work, for Win8.1... StorportRequestTimer() function needed. CFS Bit Monitoring CFS bit monitoring and handling. Look into adding additional handling code just to monitor CSTS.CFS. EOL - Read Only Read only support for devices at EOL. Detection at init, hot plug, or run-time. Namespace Mgmt Namespace management - creation and deletion of namespaces. Intel (Carolyn) End of May WHQL WHQL test suite run (any bug fixes). 2015 Release #2 (Q4 - 2015) Feature Description Submitter Date Multi-Path Multipath feature set from 1.1 spec (Multi-path I/O, Namespace Sharing, Reservations) RTD3 Active/idle RTD3 Temp Thresholds Temperature thresholds (Get/Set Feature and AER trigger) Live FW Update Live firmware update Atomicity Atomicity Enhancements Win 10 Win 10 support (push to Q4 release) SNTL SNTL 1.5 doc updates WHQL WHQL test suite run (any bug fixes) - for each release of OFA Thanks, Ray [cid:image001.png at 01CB3870.4BB88E70] Raymond C. Robles NSG ISE Host Storage Software Intel Corporation Office: 480-554-2600 Mobile: 480-399-0645 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1756 bytes Desc: image001.png URL: From suman.p at samsung.com Fri Apr 10 05:39:24 2015 From: suman.p at samsung.com (suman prakash) Date: Fri, 10 Apr 2015 18:09:24 +0530 Subject: [nvmewin] nvmewin Digest, Vol 40, Issue 3 In-Reply-To: References: Message-ID: <012101d0738b$76f59a00$64e0ce00$@samsung.com> All, Samsung would like to take up the following 3 patches - 1. Feature - Optimizing driver initialization performance. Description - Instead of learning cores, use StorPortInitializePerfOpts() to get the array of MSI numbers corresponding to each logical processor and make the Llogical processor-Queue-MSIx mapping. Submitter - Samsung (Suman) Date - End of June 2. Feature - Handling device surprise removal in IOCTL path using Win 8.1 Timers. Description - The existing implementation of detecting surprise removal during IO using the StorPortNotification(RequestTimerCall,..) does not work when IOCTL commands are outstanding. Starting from Windows 8 kernel, StorPortRequestTimer() is supported which handles the surprise removal in IOCTL path too. For Windows 7 kernel, this will be a limitation. Submitter - Samsung (Suman) Date - End of July 3. Feature - Device EOF support (Read Only) Description - Read only support for devices at EOL. Detection at init, hot plug, or run-time. Submitter - Samsung (Suman) Date - End of August Thanks, Suman -----Original Message----- From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of nvmewin-request at lists.openfabrics.org Sent: Friday, April 10, 2015 6:00 AM To: nvmewin at lists.openfabrics.org Subject: nvmewin Digest, Vol 40, Issue 3 Send nvmewin mailing list submissions to nvmewin at lists.openfabrics.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.openfabrics.org/mailman/listinfo/nvmewin or, via email, send a message with subject or body 'help' to nvmewin-request at lists.openfabrics.org You can reach the person managing the list at nvmewin-owner at lists.openfabrics.org When replying, please edit your Subject line so it is more specific than "Re: Contents of nvmewin digest..." Today's Topics: 1. OFA Release Plan: Release #1 2015 -- Call for patch volunteers (Robles, Raymond C) ---------------------------------------------------------------------- Message: 1 Date: Fri, 10 Apr 2015 00:29:00 +0000 From: "Robles, Raymond C" To: "nvmewin at lists.openfabrics.org" Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers Message-ID: <49158E750348AA499168FD41D88983606B63477F at fmsmsx117.amr.corp.intel.com> Content-Type: text/plain; charset="us-ascii" All, As we enter Q2, I'm happy to announce that we a have a very good feature plan in place for both Q2 and Q4 releases in 2015 of the OFA driver. The list of requested features is included below for final review. I would like to formally ask for volunteers for patch submissions. As of today, there are no volunteers for any of the below patches. Intel would like to start with the volunteering... we will volunteer to provide the namespace management patch. 2015 Release #1 (Q2/Q3 - 2015) Feature Description Submitter Date Concurrent Channels Start I/O Concurrent Channels allows StartIo to be called in parallel resulting in improved IOPS. Perf Opts Instead of learning cores, use perf opts. Shave off 2 seconds in init code... using Storport initialize perf opts. No need for source core interrupt steering code in driver. Win 8.1 Timers Storport Notification usage. Hot plug and IOCTLs, this does not work, for Win8.1... StorportRequestTimer() function needed. CFS Bit Monitoring CFS bit monitoring and handling. Look into adding additional handling code just to monitor CSTS.CFS. EOL - Read Only Read only support for devices at EOL. Detection at init, hot plug, or run-time. Namespace Mgmt Namespace management - creation and deletion of namespaces. Intel (Carolyn) End of May WHQL WHQL test suite run (any bug fixes). 2015 Release #2 (Q4 - 2015) Feature Description Submitter Date Multi-Path Multipath feature set from 1.1 spec (Multi-path I/O, Namespace Sharing, Reservations) RTD3 Active/idle RTD3 Temp Thresholds Temperature thresholds (Get/Set Feature and AER trigger) Live FW Update Live firmware update Atomicity Atomicity Enhancements Win 10 Win 10 support (push to Q4 release) SNTL SNTL 1.5 doc updates WHQL WHQL test suite run (any bug fixes) - for each release of OFA Thanks, Ray [cid:image001.png at 01CB3870.4BB88E70] Raymond C. Robles NSG ISE Host Storage Software Intel Corporation Office: 480-554-2600 Mobile: 480-399-0645 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1756 bytes Desc: image001.png URL: ------------------------------ _______________________________________________ nvmewin mailing list nvmewin at lists.openfabrics.org http://lists.openfabrics.org/mailman/listinfo/nvmewin End of nvmewin Digest, Vol 40, Issue 3 ************************************** From bsuman.prakash at gmail.com Fri Apr 10 07:56:44 2015 From: bsuman.prakash at gmail.com (Suman Prakash) Date: Fri, 10 Apr 2015 20:26:44 +0530 Subject: [nvmewin] nvmewin Digest, Vol 40, Issue 3 In-Reply-To: References: Message-ID: All, Samsung would like to take up the following patches - 1.Feature - Optimizing driver initialization performance. Description - Instead of learning cores, use StorPortInitializePerfOpts() to get the array of MSI numbers corresponding to each logical processor and make the Llogical processor-Queue-MSIx mapping. Submitter - Samsung (Suman) Date - End of June 2. Feature - Handling device surprise removal in IOCTL path using Win 8.1 Timers. Description - The existing implementation of detecting surprise removal during IO using the StorPortNotification(RequestTimerCall,..) does not work when IOCTL commands are outstanding. Starting from Windows 8 kernel, StorPortRequestTimer() is supported which handles the surprise removal in IOCTL path too. For Windows 7 kernel, this will be a limitation. Submitter - Samsung (Suman) Date - End of July 3. Feature - Device EOF support(Read Only) Description - Read only support for devices at EOL. Detection at init, hot plug, or run-time. Submitter - Samsung (Suman) Date - End of August Thanks, Suman On Fri, Apr 10, 2015 at 6:00 AM, wrote: > Send nvmewin mailing list submissions to > nvmewin at lists.openfabrics.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.openfabrics.org/mailman/listinfo/nvmewin > or, via email, send a message with subject or body 'help' to > nvmewin-request at lists.openfabrics.org > > You can reach the person managing the list at > nvmewin-owner at lists.openfabrics.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of nvmewin digest..." > > > Today's Topics: > > 1. OFA Release Plan: Release #1 2015 -- Call for patch > volunteers (Robles, Raymond C) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 10 Apr 2015 00:29:00 +0000 > From: "Robles, Raymond C" > To: "nvmewin at lists.openfabrics.org" > Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch > volunteers > Message-ID: > < > 49158E750348AA499168FD41D88983606B63477F at fmsmsx117.amr.corp.intel.com> > > Content-Type: text/plain; charset="us-ascii" > > All, > > As we enter Q2, I'm happy to announce that we a have a very good feature > plan in place for both Q2 and Q4 releases in 2015 of the OFA driver. The > list of requested features is included below for final review. > > I would like to formally ask for volunteers for patch submissions. As of > today, there are no volunteers for any of the below patches. > > Intel would like to start with the volunteering... we will volunteer to > provide the namespace management patch. > > 2015 Release #1 (Q2/Q3 - 2015) > > Feature > > Description > > Submitter > > Date > > Concurrent Channels > > Start I/O Concurrent Channels allows StartIo to be called in parallel > resulting in improved IOPS. > > > > > > Perf Opts > > Instead of learning cores, use perf opts. Shave off 2 seconds in init > code... using Storport initialize perf opts. No need for source core > interrupt steering code in driver. > > > > > > Win 8.1 Timers > > Storport Notification usage. Hot plug and IOCTLs, this does not work, for > Win8.1... StorportRequestTimer() function needed. > > > > > > CFS Bit Monitoring > > CFS bit monitoring and handling. Look into adding additional handling code > just to monitor CSTS.CFS. > > > > > > EOL - Read Only > > Read only support for devices at EOL. Detection at init, hot plug, or > run-time. > > > > > > Namespace Mgmt > > Namespace management - creation and deletion of namespaces. > > Intel (Carolyn) > > End of May > > WHQL > > WHQL test suite run (any bug fixes). > > > > > > > > 2015 Release #2 (Q4 - 2015) > > Feature > > Description > > Submitter > > Date > > Multi-Path > > Multipath feature set from 1.1 spec (Multi-path I/O, Namespace Sharing, > Reservations) > > > > > > RTD3 > > Active/idle RTD3 > > > > > > Temp Thresholds > > Temperature thresholds (Get/Set Feature and AER trigger) > > > > > > Live FW Update > > Live firmware update > > > > > > Atomicity > > Atomicity Enhancements > > > > > > Win 10 > > Win 10 support (push to Q4 release) > > > > > > SNTL > > SNTL 1.5 doc updates > > > > > > WHQL > > WHQL test suite run (any bug fixes) - for each release of OFA > > > > > > > > Thanks, > Ray > > [cid:image001.png at 01CB3870.4BB88E70] > Raymond C. Robles > NSG ISE Host Storage Software > Intel Corporation > Office: 480-554-2600 > Mobile: 480-399-0645 > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150410/3fb7f519/attachment.html > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: image001.png > Type: image/png > Size: 1756 bytes > Desc: image001.png > URL: < > http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150410/3fb7f519/attachment.png > > > > ------------------------------ > > _______________________________________________ > nvmewin mailing list > nvmewin at lists.openfabrics.org > http://lists.openfabrics.org/mailman/listinfo/nvmewin > > > End of nvmewin Digest, Vol 40, Issue 3 > ************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From raymond.c.robles at intel.com Fri Apr 10 11:17:52 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Fri, 10 Apr 2015 18:17:52 +0000 Subject: [nvmewin] nvmewin Digest, Vol 40, Issue 3 In-Reply-To: References: Message-ID: <49158E750348AA499168FD41D88983606B634CD7@fmsmsx117.amr.corp.intel.com> Hi Suman, Thank you very much for volunteering Samsung for the below patches. I will update the feature table for release 1 of 2015. Thanks, Ray From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Suman Prakash Sent: Friday, April 10, 2015 7:57 AM To: nvmewin at lists.openfabrics.org; m.thapliyal at samsung.com; rohini.m at samsung.com Subject: Re: [nvmewin] nvmewin Digest, Vol 40, Issue 3 All, Samsung would like to take up the following patches - 1.Feature - Optimizing driver initialization performance. Description - Instead of learning cores, use StorPortInitializePerfOpts() to get the array of MSI numbers corresponding to each logical processor and make the Llogical processor-Queue-MSIx mapping. Submitter - Samsung (Suman) Date - End of June 2. Feature - Handling device surprise removal in IOCTL path using Win 8.1 Timers. Description - The existing implementation of detecting surprise removal during IO using the StorPortNotification(RequestTimerCall,..) does not work when IOCTL commands are outstanding. Starting from Windows 8 kernel, StorPortRequestTimer() is supported which handles the surprise removal in IOCTL path too. For Windows 7 kernel, this will be a limitation. Submitter - Samsung (Suman) Date - End of July 3. Feature - Device EOF support(Read Only) Description - Read only support for devices at EOL. Detection at init, hot plug, or run-time. Submitter - Samsung (Suman) Date - End of August Thanks, Suman On Fri, Apr 10, 2015 at 6:00 AM, > wrote: Send nvmewin mailing list submissions to nvmewin at lists.openfabrics.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.openfabrics.org/mailman/listinfo/nvmewin or, via email, send a message with subject or body 'help' to nvmewin-request at lists.openfabrics.org You can reach the person managing the list at nvmewin-owner at lists.openfabrics.org When replying, please edit your Subject line so it is more specific than "Re: Contents of nvmewin digest..." Today's Topics: 1. OFA Release Plan: Release #1 2015 -- Call for patch volunteers (Robles, Raymond C) ---------------------------------------------------------------------- Message: 1 Date: Fri, 10 Apr 2015 00:29:00 +0000 From: "Robles, Raymond C" > To: "nvmewin at lists.openfabrics.org" > Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers Message-ID: <49158E750348AA499168FD41D88983606B63477F at fmsmsx117.amr.corp.intel.com> Content-Type: text/plain; charset="us-ascii" All, As we enter Q2, I'm happy to announce that we a have a very good feature plan in place for both Q2 and Q4 releases in 2015 of the OFA driver. The list of requested features is included below for final review. I would like to formally ask for volunteers for patch submissions. As of today, there are no volunteers for any of the below patches. Intel would like to start with the volunteering... we will volunteer to provide the namespace management patch. 2015 Release #1 (Q2/Q3 - 2015) Feature Description Submitter Date Concurrent Channels Start I/O Concurrent Channels allows StartIo to be called in parallel resulting in improved IOPS. Perf Opts Instead of learning cores, use perf opts. Shave off 2 seconds in init code... using Storport initialize perf opts. No need for source core interrupt steering code in driver. Win 8.1 Timers Storport Notification usage. Hot plug and IOCTLs, this does not work, for Win8.1... StorportRequestTimer() function needed. CFS Bit Monitoring CFS bit monitoring and handling. Look into adding additional handling code just to monitor CSTS.CFS. EOL - Read Only Read only support for devices at EOL. Detection at init, hot plug, or run-time. Namespace Mgmt Namespace management - creation and deletion of namespaces. Intel (Carolyn) End of May WHQL WHQL test suite run (any bug fixes). 2015 Release #2 (Q4 - 2015) Feature Description Submitter Date Multi-Path Multipath feature set from 1.1 spec (Multi-path I/O, Namespace Sharing, Reservations) RTD3 Active/idle RTD3 Temp Thresholds Temperature thresholds (Get/Set Feature and AER trigger) Live FW Update Live firmware update Atomicity Atomicity Enhancements Win 10 Win 10 support (push to Q4 release) SNTL SNTL 1.5 doc updates WHQL WHQL test suite run (any bug fixes) - for each release of OFA Thanks, Ray [cid:image001.png at 01CB3870.4BB88E70] Raymond C. Robles NSG ISE Host Storage Software Intel Corporation Office: 480-554-2600 Mobile: 480-399-0645 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1756 bytes Desc: image001.png URL: ------------------------------ _______________________________________________ nvmewin mailing list nvmewin at lists.openfabrics.org http://lists.openfabrics.org/mailman/listinfo/nvmewin End of nvmewin Digest, Vol 40, Issue 3 ************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From brandon.schulz at hgst.com Mon Apr 13 14:01:16 2015 From: brandon.schulz at hgst.com (Brandon Schulz) Date: Mon, 13 Apr 2015 21:01:16 +0000 Subject: [nvmewin] nvmewin Digest, Vol 40, Issue 3 In-Reply-To: <012101d0738b$76f59a00$64e0ce00$@samsung.com> References: <012101d0738b$76f59a00$64e0ce00$@samsung.com> Message-ID: Suman - Do you know what you are going to use as a trigger for entering read-only mode at drive EOL? Brandon -----Original Message----- From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of suman prakash Sent: Friday, April 10, 2015 7:39 AM To: nvmewin at lists.openfabrics.org Subject: Re: [nvmewin] nvmewin Digest, Vol 40, Issue 3 All, Samsung would like to take up the following 3 patches - 1. Feature - Optimizing driver initialization performance. Description - Instead of learning cores, use StorPortInitializePerfOpts() to get the array of MSI numbers corresponding to each logical processor and make the Llogical processor-Queue-MSIx mapping. Submitter - Samsung (Suman) Date - End of June 2. Feature - Handling device surprise removal in IOCTL path using Win 8.1 Timers. Description - The existing implementation of detecting surprise removal during IO using the StorPortNotification(RequestTimerCall,..) does not work when IOCTL commands are outstanding. Starting from Windows 8 kernel, StorPortRequestTimer() is supported which handles the surprise removal in IOCTL path too. For Windows 7 kernel, this will be a limitation. Submitter - Samsung (Suman) Date - End of July 3. Feature - Device EOF support (Read Only) Description - Read only support for devices at EOL. Detection at init, hot plug, or run-time. Submitter - Samsung (Suman) Date - End of August Thanks, Suman -----Original Message----- From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of nvmewin-request at lists.openfabrics.org Sent: Friday, April 10, 2015 6:00 AM To: nvmewin at lists.openfabrics.org Subject: nvmewin Digest, Vol 40, Issue 3 Send nvmewin mailing list submissions to nvmewin at lists.openfabrics.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.openfabrics.org/mailman/listinfo/nvmewin or, via email, send a message with subject or body 'help' to nvmewin-request at lists.openfabrics.org You can reach the person managing the list at nvmewin-owner at lists.openfabrics.org When replying, please edit your Subject line so it is more specific than "Re: Contents of nvmewin digest..." Today's Topics: 1. OFA Release Plan: Release #1 2015 -- Call for patch volunteers (Robles, Raymond C) ---------------------------------------------------------------------- Message: 1 Date: Fri, 10 Apr 2015 00:29:00 +0000 From: "Robles, Raymond C" To: "nvmewin at lists.openfabrics.org" Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch volunteers Message-ID: <49158E750348AA499168FD41D88983606B63477F at fmsmsx117.amr.corp.intel.com> Content-Type: text/plain; charset="us-ascii" All, As we enter Q2, I'm happy to announce that we a have a very good feature plan in place for both Q2 and Q4 releases in 2015 of the OFA driver. The list of requested features is included below for final review. I would like to formally ask for volunteers for patch submissions. As of today, there are no volunteers for any of the below patches. Intel would like to start with the volunteering... we will volunteer to provide the namespace management patch. 2015 Release #1 (Q2/Q3 - 2015) Feature Description Submitter Date Concurrent Channels Start I/O Concurrent Channels allows StartIo to be called in parallel resulting in improved IOPS. Perf Opts Instead of learning cores, use perf opts. Shave off 2 seconds in init code... using Storport initialize perf opts. No need for source core interrupt steering code in driver. Win 8.1 Timers Storport Notification usage. Hot plug and IOCTLs, this does not work, for Win8.1... StorportRequestTimer() function needed. CFS Bit Monitoring CFS bit monitoring and handling. Look into adding additional handling code just to monitor CSTS.CFS. EOL - Read Only Read only support for devices at EOL. Detection at init, hot plug, or run-time. Namespace Mgmt Namespace management - creation and deletion of namespaces. Intel (Carolyn) End of May WHQL WHQL test suite run (any bug fixes). 2015 Release #2 (Q4 - 2015) Feature Description Submitter Date Multi-Path Multipath feature set from 1.1 spec (Multi-path I/O, Namespace Sharing, Reservations) RTD3 Active/idle RTD3 Temp Thresholds Temperature thresholds (Get/Set Feature and AER trigger) Live FW Update Live firmware update Atomicity Atomicity Enhancements Win 10 Win 10 support (push to Q4 release) SNTL SNTL 1.5 doc updates WHQL WHQL test suite run (any bug fixes) - for each release of OFA Thanks, Ray [cid:image001.png at 01CB3870.4BB88E70] Raymond C. Robles NSG ISE Host Storage Software Intel Corporation Office: 480-554-2600 Mobile: 480-399-0645 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1756 bytes Desc: image001.png URL: ------------------------------ _______________________________________________ nvmewin mailing list nvmewin at lists.openfabrics.org http://lists.openfabrics.org/mailman/listinfo/nvmewin End of nvmewin Digest, Vol 40, Issue 3 ************************************** _______________________________________________ nvmewin mailing list nvmewin at lists.openfabrics.org http://lists.openfabrics.org/mailman/listinfo/nvmewin From tom.fones at ssi.samsung.com Mon Apr 13 14:36:35 2015 From: tom.fones at ssi.samsung.com (Tom Fones-SSI) Date: Mon, 13 Apr 2015 21:36:35 +0000 Subject: [nvmewin] nvmewin Message-ID: May I ask the community if anyone has tried to install and use a custom storage class driver (replacement for Disk.sys in Windows) on an NVMe disk, and if so have they had any success ? Thanks in advance, Tom Fones @ Samsung From raymond.c.robles at intel.com Mon Apr 13 16:01:03 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Mon, 13 Apr 2015 23:01:03 +0000 Subject: [nvmewin] nvmewin In-Reply-To: References: Message-ID: <49158E750348AA499168FD41D88983606B636AC9@fmsmsx117.amr.corp.intel.com> I have not heard of any such experiments. Thanks, Ray -----Original Message----- From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Tom Fones-SSI Sent: Monday, April 13, 2015 2:37 PM To: suman prakash; nvmewin at lists.openfabrics.org Subject: Re: [nvmewin] nvmewin May I ask the community if anyone has tried to install and use a custom storage class driver (replacement for Disk.sys in Windows) on an NVMe disk, and if so have they had any success ? Thanks in advance, Tom Fones @ Samsung _______________________________________________ nvmewin mailing list nvmewin at lists.openfabrics.org http://lists.openfabrics.org/mailman/listinfo/nvmewin From bsuman.prakash at gmail.com Tue Apr 14 12:50:03 2015 From: bsuman.prakash at gmail.com (Suman Prakash) Date: Wed, 15 Apr 2015 01:20:03 +0530 Subject: [nvmewin] nvmewin Digest, Vol 40, Issue 5 In-Reply-To: References: Message-ID: Hi Brandon, Please find my answer below - a. EoL: Detection during device hot plug - During driver initialization, the SMART/Health Information, Critical Warning field, bit 3 which mentions "If set to '1', then the media has been placed in read only mode" is the trigger to enter Read Only mode. In driver, we have introduced a new state in NVMeRunning(), which sends a Get Log Page for SMART Health information, and save the critical warning field. During disk initialization, when kernel sends the SCSI mode sense command with Page code 0x3f(Return all pages), in the mode parameter header, in Device specific parameter, the WP(write protect) bit is set to 1. Once the mode sense response is returned, the disk in the disk manager is shown as 'Read Only' and no more write commands are sent to the device. b. EoL: Detection during run time - During run time, for write command, the completion entry with SCT = 1h (Command Specific Status) and SC = 82h (Attempted Write to Read Only Range) is the trigger to enter Read Only mode. Please note that this is currently not part of the NVM Express: SCSI Translation Reference specification and is in the process of being included. In driver, for any write command, in the completion entry, if SCT = 1h and SC = 82h, the following sense data is returned to the kernel: SrbStatus = SRB_STATUS_ERROR StatusCode = SCSISTAT_CHECK_CONDITION SenseKey = SCSI_SENSE_DATA_PROTECT ASC = SCSI_ADSENSE_WRITE_PROTECT ASCQ = SCSI_ADSENSE_NO_SENSE For which the kernel sends the mode sense with Page code 0x3f, which is translated to Get log page for SMART Health information, which returns critical warning field, with bit 3 set to 1. In response to the mode sense command, in mode parameter header, in Device specific parameter, the WP(write protect) bit is set. After the mode sense response is returned, the disk in the disk manager is shown as 'Read Only' and no more write commands are sent to the device. We have tested this implementation in following ways - 1. Insert a RO device and start the PC. After PC is booted, the disk is shown as Read Only in disk management. 2. Hot inserted the RO device and disk management shows disk are Read Only. 3. Executed IOmeter on the NVMe disk. Once the disk become Read Only, The 'Error Count' field in IOmeter start increases and IOPs starts dropping. Disk managements shows disk as Read Only. 4. Tried copying files to Read Only drive and got pop up messages as Drive is write protected. 5. When the Available Spare field in the SMART information log is 10%, started copying files to the disk. And when disk becomes Read Only, got pop up message as Driver has become write protected. Thanks, Suman On Wed, Apr 15, 2015 at 12:30 AM, wrote: > Send nvmewin mailing list submissions to > nvmewin at lists.openfabrics.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.openfabrics.org/mailman/listinfo/nvmewin > or, via email, send a message with subject or body 'help' to > nvmewin-request at lists.openfabrics.org > > You can reach the person managing the list at > nvmewin-owner at lists.openfabrics.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of nvmewin digest..." > > > Today's Topics: > > 1. Re: nvmewin Digest, Vol 40, Issue 3 (Brandon Schulz) > 2. Re: nvmewin (Tom Fones-SSI) > 3. Re: nvmewin (Robles, Raymond C) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 13 Apr 2015 21:01:16 +0000 > From: Brandon Schulz > To: suman prakash , > "nvmewin at lists.openfabrics.org" > Subject: Re: [nvmewin] nvmewin Digest, Vol 40, Issue 3 > Message-ID: > < > BN1PR0401MB09316D3E00BDAD9B0F65B9D3F2E70 at BN1PR0401MB0931.namprd04.prod.outlook.com > > > > Content-Type: text/plain; charset="us-ascii" > > Suman - > > Do you know what you are going to use as a trigger for entering read-only > mode at drive EOL? > > Brandon > > -----Original Message----- > From: nvmewin-bounces at lists.openfabrics.org [mailto: > nvmewin-bounces at lists.openfabrics.org] On Behalf Of suman prakash > Sent: Friday, April 10, 2015 7:39 AM > To: nvmewin at lists.openfabrics.org > Subject: Re: [nvmewin] nvmewin Digest, Vol 40, Issue 3 > > All, > > Samsung would like to take up the following 3 patches - > > 1. Feature - Optimizing driver initialization performance. > Description - Instead of learning cores, use StorPortInitializePerfOpts() > to get the array of MSI numbers corresponding to each logical processor and > make the Llogical processor-Queue-MSIx mapping. > Submitter - Samsung (Suman) > Date - End of June > > 2. Feature - Handling device surprise removal in IOCTL path using Win 8.1 > Timers. > Description - The existing implementation of detecting surprise removal > during IO using the StorPortNotification(RequestTimerCall,..) does not work > when IOCTL commands are outstanding. Starting from Windows 8 kernel, > StorPortRequestTimer() is supported which handles the surprise removal in > IOCTL path too. For Windows 7 kernel, this will be a limitation. > Submitter - Samsung (Suman) > Date - End of July > > 3. Feature - Device EOF support (Read Only) Description - Read only > support for devices at EOL. Detection at init, hot plug, or run-time. > Submitter - Samsung (Suman) > Date - End of August > > Thanks, > Suman > > > -----Original Message----- > From: nvmewin-bounces at lists.openfabrics.org > [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of > nvmewin-request at lists.openfabrics.org > Sent: Friday, April 10, 2015 6:00 AM > To: nvmewin at lists.openfabrics.org > Subject: nvmewin Digest, Vol 40, Issue 3 > > Send nvmewin mailing list submissions to > nvmewin at lists.openfabrics.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.openfabrics.org/mailman/listinfo/nvmewin > or, via email, send a message with subject or body 'help' to > nvmewin-request at lists.openfabrics.org > > You can reach the person managing the list at > nvmewin-owner at lists.openfabrics.org > > When replying, please edit your Subject line so it is more specific than > "Re: Contents of nvmewin digest..." > > > Today's Topics: > > 1. OFA Release Plan: Release #1 2015 -- Call for patch > volunteers (Robles, Raymond C) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 10 Apr 2015 00:29:00 +0000 > From: "Robles, Raymond C" > To: "nvmewin at lists.openfabrics.org" > Subject: [nvmewin] OFA Release Plan: Release #1 2015 -- Call for patch > volunteers > Message-ID: > > <49158E750348AA499168FD41D88983606B63477F at fmsmsx117.amr.corp.intel.com> > > Content-Type: text/plain; charset="us-ascii" > > All, > > As we enter Q2, I'm happy to announce that we a have a very good feature > plan in place for both Q2 and Q4 releases in 2015 of the OFA driver. The > list of requested features is included below for final review. > > I would like to formally ask for volunteers for patch submissions. As of > today, there are no volunteers for any of the below patches. > > Intel would like to start with the volunteering... we will volunteer to > provide the namespace management patch. > > 2015 Release #1 (Q2/Q3 - 2015) > > Feature > > Description > > Submitter > > Date > > Concurrent Channels > > Start I/O Concurrent Channels allows StartIo to be called in parallel > resulting in improved IOPS. > > > > > > Perf Opts > > Instead of learning cores, use perf opts. Shave off 2 seconds in init > code... using Storport initialize perf opts. No need for source core > interrupt steering code in driver. > > > > > > Win 8.1 Timers > > Storport Notification usage. Hot plug and IOCTLs, this does not work, for > Win8.1... StorportRequestTimer() function needed. > > > > > > CFS Bit Monitoring > > CFS bit monitoring and handling. Look into adding additional handling code > just to monitor CSTS.CFS. > > > > > > EOL - Read Only > > Read only support for devices at EOL. Detection at init, hot plug, or > run-time. > > > > > > Namespace Mgmt > > Namespace management - creation and deletion of namespaces. > > Intel (Carolyn) > > End of May > > WHQL > > WHQL test suite run (any bug fixes). > > > > > > > > 2015 Release #2 (Q4 - 2015) > > Feature > > Description > > Submitter > > Date > > Multi-Path > > Multipath feature set from 1.1 spec (Multi-path I/O, Namespace Sharing, > Reservations) > > > > > > RTD3 > > Active/idle RTD3 > > > > > > Temp Thresholds > > Temperature thresholds (Get/Set Feature and AER trigger) > > > > > > Live FW Update > > Live firmware update > > > > > > Atomicity > > Atomicity Enhancements > > > > > > Win 10 > > Win 10 support (push to Q4 release) > > > > > > SNTL > > SNTL 1.5 doc updates > > > > > > WHQL > > WHQL test suite run (any bug fixes) - for each release of OFA > > > > > > > > Thanks, > Ray > > [cid:image001.png at 01CB3870.4BB88E70] > Raymond C. Robles > NSG ISE Host Storage Software > Intel Corporation > Office: 480-554-2600 > Mobile: 480-399-0645 > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > < > http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150410/3fb7f51 > 9/attachment.html> > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: image001.png > Type: image/png > Size: 1756 bytes > Desc: image001.png > URL: > < > http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150410/3fb7f51 > 9/attachment.png> > > ------------------------------ > > _______________________________________________ > nvmewin mailing list > nvmewin at lists.openfabrics.org > http://lists.openfabrics.org/mailman/listinfo/nvmewin > > > End of nvmewin Digest, Vol 40, Issue 3 > ************************************** > > _______________________________________________ > nvmewin mailing list > nvmewin at lists.openfabrics.org > http://lists.openfabrics.org/mailman/listinfo/nvmewin > > > ------------------------------ > > Message: 2 > Date: Mon, 13 Apr 2015 21:36:35 +0000 > From: Tom Fones-SSI > To: suman prakash , > "nvmewin at lists.openfabrics.org" > Subject: Re: [nvmewin] nvmewin > Message-ID: > < > EEAA00CCA2889D429E22F360CC0B0DC105C868 at SSIEXCH-MB3.ssi.samsung.com> > Content-Type: text/plain; charset="us-ascii" > > > May I ask the community if anyone has tried to install and use a custom > storage class driver > (replacement for Disk.sys in Windows) on an NVMe disk, and if so have they > had any success ? > > Thanks in advance, > Tom Fones @ Samsung > > > ------------------------------ > > Message: 3 > Date: Mon, 13 Apr 2015 23:01:03 +0000 > From: "Robles, Raymond C" > To: 'Tom Fones-SSI' , suman prakash > , "nvmewin at lists.openfabrics.org" > > Subject: Re: [nvmewin] nvmewin > Message-ID: > < > 49158E750348AA499168FD41D88983606B636AC9 at fmsmsx117.amr.corp.intel.com> > > Content-Type: text/plain; charset="us-ascii" > > I have not heard of any such experiments. > > Thanks, > Ray > > -----Original Message----- > From: nvmewin-bounces at lists.openfabrics.org [mailto: > nvmewin-bounces at lists.openfabrics.org] On Behalf Of Tom Fones-SSI > Sent: Monday, April 13, 2015 2:37 PM > To: suman prakash; nvmewin at lists.openfabrics.org > Subject: Re: [nvmewin] nvmewin > > > May I ask the community if anyone has tried to install and use a custom > storage class driver (replacement for Disk.sys in Windows) on an NVMe disk, > and if so have they had any success ? > > Thanks in advance, > Tom Fones @ Samsung > _______________________________________________ > nvmewin mailing list > nvmewin at lists.openfabrics.org > http://lists.openfabrics.org/mailman/listinfo/nvmewin > > > ------------------------------ > > _______________________________________________ > nvmewin mailing list > nvmewin at lists.openfabrics.org > http://lists.openfabrics.org/mailman/listinfo/nvmewin > > > End of nvmewin Digest, Vol 40, Issue 5 > ************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From raymond.c.robles at intel.com Wed Apr 15 11:02:05 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Wed, 15 Apr 2015 18:02:05 +0000 Subject: [nvmewin] out of memory in the NVMePreparePRPs function In-Reply-To: <2015031315273640372817@memblaze.com> References: <2015031315273640372817@memblaze.com> Message-ID: <49158E750348AA499168FD41D88983606B6381A1@fmsmsx117.amr.corp.intel.com> Hi Cheng, Thanks for bringing this issue up. I reviewed the code and see the potential issue. Arguably, TxLength should never be larger than the MDTS set by our driver during setup/enum (Storport will honor this max transfer size), but the bug is in the code nevertheless. Generally, the process for the OFA driver is that when someone, or some company, finds a bug in the OFA driver then they are also asked to submit a patch to resolve that issue. Are you able to submit a patch to resolve this issue? Thanks, Ray From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of cheng.peng at memblaze.com Sent: Friday, March 13, 2015 12:28 AM To: nvmewin Cc: Ԭ�� Subject: [nvmewin] out of memory in the NVMePreparePRPs function Hi, I get a BSOD when the parameter TxLength of the NVMePreparePRPs function is assigned to a big number(e.g. 1572864) In this case��pSrbExt->numberOfPrpEntries will be a wrong number due to out of memory I have temporarily solved this problem by setting MAX_TX_SIZE to (2*1024*1024) I think there should be a better solution thank you ________________________________ cheng.peng at memblaze.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From raymond.c.robles at intel.com Wed Apr 15 11:20:04 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Wed, 15 Apr 2015 18:20:04 +0000 Subject: [nvmewin] don't create the disk device In-Reply-To: <201503051450187766495@memblaze.com> References: <201503051450187766495@memblaze.com> Message-ID: <49158E750348AA499168FD41D88983606B6381FE@fmsmsx117.amr.corp.intel.com> Hi Cheng, I'm not sure I understand your question. Could you please elaborate? When the driver is loaded, if can see the drive in "Device Manager" and "Disk Manager", then all the necessary structures were created and/or populated. Thanks, Ray From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of cheng.peng at memblaze.com Sent: Wednesday, March 04, 2015 11:50 PM To: nvmewin Subject: [nvmewin] don't create the disk device when driver is loaded, ScsiAdapter device is created, but disk device isn't created. 00000000 0.00000000 STORMINI: StorPortInitialize returns Status(0x0) 00000001 0.02776694 STORMINI: Access Range, VirtualAddr=0xFFFFF8800654F000. 00000002 0.02778550 STORMINI: NVMeFindAdapter: Stride Size set to 0x4 00000003 0.02785815 STORMINI: NVMeEnumNumaCores: # of NUMA node(s) = 1. 00000004 0.02786289 STORMINI: NVMeEnumNumaCores: Number of groups = 1. 00000005 0.02786644 STORMINI: NVMeEnumNumaCores: Group(0) affinity mask(0x3). 00000006 0.02786920 STORMINI: NVMeEnumNumaCores: Total 2 logical processors 00000007 0.02787118 STORMINI: NVMeEnumNumaCores: NUMA Node#0 00000008 0.02787394 STORMINI: Core mask is 0x3 in Group(0) 00000009 0.02787749 STORMINI: There are 2 cores in Node#0. 00000010 0.02787986 STORMINI: The total number of CPU cores 2. 00000011 0.02829325 STORMINI: NVMeEnumMsiMessages: Msg granted=2 00000012 0.02831062 STORMINI: NVMeAllocateMem: Succeeded! 00000013 0.02832010 STORMINI: NVMeAllocateMem: Succeeded! 00000014 0.02833590 STORMINI: NVMeInitSubQueue : SQ 0x0 pSubTDBL 0xFFFFF88006550000 at index 0x0 00000015 0.02835406 STORMINI: NVMeInitCplQueue : CQ 0x0 pCplHDBL 0xFFFFF88006550004 at index 0x1 00000016 0.02836788 STORMINI: NVMeEnableAdapter: Setting EN... 00000017 0.02837617 STORMINI: NVMeAllocateMem: Succeeded! 00000018 0.02838446 STORMINI: NVMeAllocateMem: Succeeded! 00000019 0.02874849 STORMINI: NVMeRunningWaitOnRDY: Waiting... 00000020 0.03745769 STORMINI: NVMeRunningWaitOnRDY: RDY has been set 00000021 0.05304605 STORMINI: NVMeGetIdentifyStructures: IDEN_CONTROLLER 00000022 0.05310448 STORMINI: NVMeInitCallback: Driver state: 33 00000023 0.06864980 STORMINI: NVMeGetIdentifyStructures: IDEN_NAMESPACE 00000024 0.06865493 STORMINI: NVMeGetIdentifyStructures: Get NS INFO for NSID 0x1 tgt lun 0x0 00000025 0.06867468 STORMINI: NVMeInitCallback: Driver state: 34 00000026 0.08686497 STORMINI: NVMeInitCallback: Driver state: 35 00000027 0.09989244 STORMINI: NVMeInitCallback: Driver state: 35 00000028 0.11546224 STORMINI: NVMeInitCallback: Driver state: 35 00000029 0.11546777 STORMINI: pLbaRangeTypeEntry type : 0x0 lun id 0 nsid 0x1 00000030 0.11547054 STORMINI: NVMeSetFeaturesCompletion: FYI LnuExt at 0 has been cleared (NSID not visible) 00000031 0.13106994 STORMINI: NVMeAllocateMem: Succeeded! 00000032 0.13109048 STORMINI: NVMeAllocateMem: Succeeded! 00000033 0.13111298 STORMINI: NVMeAllocIoQueues: Core 0x0 ---> QueueID 0x1 00000034 0.13112088 STORMINI: NVMeAllocateMem: Succeeded! 00000035 0.13113983 STORMINI: NVMeAllocateMem: Succeeded! 00000036 0.13116075 STORMINI: NVMeAllocIoQueues: Core 0x1 ---> QueueID 0x2 00000037 0.13116352 STORMINI: NVMeMsiMapCores: Core(0x0)Msg#(0x0) 00000038 0.13116549 STORMINI: NVMeMsiMapCores: Core(0x1)Msg#(0x1) 00000039 0.13117695 STORMINI: NVMeInitSubQueue : SQ 0x1 pSubTDBL 0xFFFFF88006550008 at index 0x2 00000040 0.13121486 STORMINI: NVMeInitSubQueue : SQ 0x2 pSubTDBL 0xFFFFF88006550010 at index 0x4 00000041 0.13125157 STORMINI: NVMeInitCplQueue : CQ 0x1 pCplHDBL 0xFFFFF8800655000C at index 0x3 00000042 0.13126460 STORMINI: NVMeInitCplQueue : CQ 0x2 pCplHDBL 0xFFFFF88006550014 at index 0x5 00000043 0.14669226 STORMINI: NVMeInitCallback: Driver state: 38 00000044 0.16231970 STORMINI: NVMeInitCallback: Driver state: 38 00000045 0.17787489 STORMINI: NVMeInitCallback: Driver state: 39 00000046 0.19351892 STORMINI: NVMeInitCallback: Driver state: 39 00000047 0.22342743 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa0 BTL 0 0 0 00000048 0.22343650 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa0 BTL 0 0 0 00000049 0.22344086 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa0 BTL 0 0 0 00000050 0.22344598 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0x12 BTL 0 0 0 00000051 0.22344993 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0x12 BTL 0 0 0 00000052 0.22345348 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0x12 BTL 0 0 0 00000053 0.22369038 STORMINI: FYI: SRB status 0x6 scsi 0x8 for CDB 0x0 BTL 0 0 0 00000054 0.22462179 STORMINI: NVMeRunning: StorPortReady... please tell me the reason, thank you ________________________________ cheng.peng at memblaze.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mikeb at bustrace.com Wed Apr 15 12:08:20 2015 From: mikeb at bustrace.com (Mike Berhan) Date: Wed, 15 Apr 2015 13:08:20 -0600 Subject: [nvmewin] don't create the disk device In-Reply-To: <49158E750348AA499168FD41D88983606B6381FE@fmsmsx117.amr.corp.intel.com> References: <201503051450187766495@memblaze.com> <49158E750348AA499168FD41D88983606B6381FE@fmsmsx117.amr.corp.intel.com> Message-ID: <016f01d077af$8a7b6870$9f723950$@bustrace.com> It looks like STORPORT is calling you to enumerate your devices (i.e. Report LUNs, Inquiry, TUR) but you're failing the requests with SRB_STATUS_INVALID_REQUEST: 00000047 0.22342743 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa0 BTL 0 0 0 00000048 0.22343650 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa0 BTL 0 0 0 00000049 0.22344086 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa0 BTL 0 0 0 00000050 0.22344598 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0x12 BTL 0 0 0 00000051 0.22344993 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0x12 BTL 0 0 0 00000052 0.22345348 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0x12 BTL 0 0 0 00000053 0.22369038 STORMINI: FYI: SRB status 0x6 scsi 0x8 for CDB 0x0 BTL 0 0 0 Trace through your SRB handler for these commands and you'll likely find the root cause. Mike From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Robles, Raymond C Sent: Wednesday, April 15, 2015 12:20 PM To: cheng.peng at memblaze.com; nvmewin Subject: Re: [nvmewin] don't create the disk device Hi Cheng, I'm not sure I understand your question. Could you please elaborate? When the driver is loaded, if can see the drive in "Device Manager" and "Disk Manager", then all the necessary structures were created and/or populated. Thanks, Ray From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of cheng.peng at memblaze.com Sent: Wednesday, March 04, 2015 11:50 PM To: nvmewin Subject: [nvmewin] don't create the disk device when driver is loaded, ScsiAdapter device is created, but disk device isn't created. 00000000 0.00000000 STORMINI: StorPortInitialize returns Status(0x0) 00000001 0.02776694 STORMINI: Access Range, VirtualAddr=0xFFFFF8800654F000. 00000002 0.02778550 STORMINI: NVMeFindAdapter: Stride Size set to 0x4 00000003 0.02785815 STORMINI: NVMeEnumNumaCores: # of NUMA node(s) = 1. 00000004 0.02786289 STORMINI: NVMeEnumNumaCores: Number of groups = 1. 00000005 0.02786644 STORMINI: NVMeEnumNumaCores: Group(0) affinity mask(0x3). 00000006 0.02786920 STORMINI: NVMeEnumNumaCores: Total 2 logical processors 00000007 0.02787118 STORMINI: NVMeEnumNumaCores: NUMA Node#0 00000008 0.02787394 STORMINI: Core mask is 0x3 in Group(0) 00000009 0.02787749 STORMINI: There are 2 cores in Node#0. 00000010 0.02787986 STORMINI: The total number of CPU cores 2. 00000011 0.02829325 STORMINI: NVMeEnumMsiMessages: Msg granted=2 00000012 0.02831062 STORMINI: NVMeAllocateMem: Succeeded! 00000013 0.02832010 STORMINI: NVMeAllocateMem: Succeeded! 00000014 0.02833590 STORMINI: NVMeInitSubQueue : SQ 0x0 pSubTDBL 0xFFFFF88006550000 at index 0x0 00000015 0.02835406 STORMINI: NVMeInitCplQueue : CQ 0x0 pCplHDBL 0xFFFFF88006550004 at index 0x1 00000016 0.02836788 STORMINI: NVMeEnableAdapter: Setting EN... 00000017 0.02837617 STORMINI: NVMeAllocateMem: Succeeded! 00000018 0.02838446 STORMINI: NVMeAllocateMem: Succeeded! 00000019 0.02874849 STORMINI: NVMeRunningWaitOnRDY: Waiting... 00000020 0.03745769 STORMINI: NVMeRunningWaitOnRDY: RDY has been set 00000021 0.05304605 STORMINI: NVMeGetIdentifyStructures: IDEN_CONTROLLER 00000022 0.05310448 STORMINI: NVMeInitCallback: Driver state: 33 00000023 0.06864980 STORMINI: NVMeGetIdentifyStructures: IDEN_NAMESPACE 00000024 0.06865493 STORMINI: NVMeGetIdentifyStructures: Get NS INFO for NSID 0x1 tgt lun 0x0 00000025 0.06867468 STORMINI: NVMeInitCallback: Driver state: 34 00000026 0.08686497 STORMINI: NVMeInitCallback: Driver state: 35 00000027 0.09989244 STORMINI: NVMeInitCallback: Driver state: 35 00000028 0.11546224 STORMINI: NVMeInitCallback: Driver state: 35 00000029 0.11546777 STORMINI: pLbaRangeTypeEntry type : 0x0 lun id 0 nsid 0x1 00000030 0.11547054 STORMINI: NVMeSetFeaturesCompletion: FYI LnuExt at 0 has been cleared (NSID not visible) 00000031 0.13106994 STORMINI: NVMeAllocateMem: Succeeded! 00000032 0.13109048 STORMINI: NVMeAllocateMem: Succeeded! 00000033 0.13111298 STORMINI: NVMeAllocIoQueues: Core 0x0 ---> QueueID 0x1 00000034 0.13112088 STORMINI: NVMeAllocateMem: Succeeded! 00000035 0.13113983 STORMINI: NVMeAllocateMem: Succeeded! 00000036 0.13116075 STORMINI: NVMeAllocIoQueues: Core 0x1 ---> QueueID 0x2 00000037 0.13116352 STORMINI: NVMeMsiMapCores: Core(0x0)Msg#(0x0) 00000038 0.13116549 STORMINI: NVMeMsiMapCores: Core(0x1)Msg#(0x1) 00000039 0.13117695 STORMINI: NVMeInitSubQueue : SQ 0x1 pSubTDBL 0xFFFFF88006550008 at index 0x2 00000040 0.13121486 STORMINI: NVMeInitSubQueue : SQ 0x2 pSubTDBL 0xFFFFF88006550010 at index 0x4 00000041 0.13125157 STORMINI: NVMeInitCplQueue : CQ 0x1 pCplHDBL 0xFFFFF8800655000C at index 0x3 00000042 0.13126460 STORMINI: NVMeInitCplQueue : CQ 0x2 pCplHDBL 0xFFFFF88006550014 at index 0x5 00000043 0.14669226 STORMINI: NVMeInitCallback: Driver state: 38 00000044 0.16231970 STORMINI: NVMeInitCallback: Driver state: 38 00000045 0.17787489 STORMINI: NVMeInitCallback: Driver state: 39 00000046 0.19351892 STORMINI: NVMeInitCallback: Driver state: 39 00000047 0.22342743 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa0 BTL 0 0 0 00000048 0.22343650 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa0 BTL 0 0 0 00000049 0.22344086 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa0 BTL 0 0 0 00000050 0.22344598 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0x12 BTL 0 0 0 00000051 0.22344993 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0x12 BTL 0 0 0 00000052 0.22345348 STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0x12 BTL 0 0 0 00000053 0.22369038 STORMINI: FYI: SRB status 0x6 scsi 0x8 for CDB 0x0 BTL 0 0 0 00000054 0.22462179 STORMINI: NVMeRunning: StorPortReady... please tell me the reason, thank you _____ cheng.peng at memblaze.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremy.tsai.911 at gmail.com Thu Apr 23 17:06:31 2015 From: jeremy.tsai.911 at gmail.com (GoogleCalendar) Date: Thu, 23 Apr 2015 17:06:31 -0700 Subject: [nvmewin] NVMe device unable to started Message-ID: <45DC73B6-C776-41CF-BDD7-52FDD1EF7706@gmail.com> Hello, I tried to install the release 1.4, but there’s an issue causing the device unable to start. Originally, I use the standard driver from MS for the NVMe device. The device is started and recognized by the disk drive. After I updating the driver to name-1.4 driver, the community 1.0e driver, The device was not started and not recognized by the disk drive. Based on the event log I saw, I only know there’s a problem: 0x15. (firstly configured by oem73.inf, then unable to start due to name) Can you guys have any ideas about how to fix the starting failure. Or what information, Windows log I can look up into? The attached file is the Event Log, Event ID 411. -------------- next part -------------- A non-text attachment was scrubbed... Name: FailedDeviceEventLog.evtx Type: application/octet-stream Size: 69632 bytes Desc: not available URL: -------------- next part -------------- Regards. Jeremy From raymond.c.robles at intel.com Fri Apr 24 11:09:41 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Fri, 24 Apr 2015 18:09:41 +0000 Subject: [nvmewin] NVMe device unable to started In-Reply-To: <45DC73B6-C776-41CF-BDD7-52FDD1EF7706@gmail.com> References: <45DC73B6-C776-41CF-BDD7-52FDD1EF7706@gmail.com> Message-ID: <49158E750348AA499168FD41D88983606B64ECDD@fmsmsx117.amr.corp.intel.com> Hi Jeremy, Thanks for reaching out to the OFA NVMe Windows distribution list. First off, could you please officially subscribe to the NVMe mailing list? People who are not on the mailing list are not allowed to send emails to the distribution. As the chair of the OFA NVMe Windows driver, I got the notification of your email and approved it (we get a lot of spam that I have to filter through). As for your issue, a little more information would be helpful: - What NVMe device/drive are you attempting to run? - Windows kernel event logs are not much help. To best analyze your failing scenario, we would need to see a couple of things: o A full kernel memory dump (not a mini-dump), or o The debug kernel output (this can either be form WinDbg or a program like DebugView). Basically what we would need is the print statements from the driver trying to load. If you could provide this info, we could provide more insight into your problem? Thanks, Ray From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of GoogleCalendar Sent: Thursday, April 23, 2015 5:07 PM To: nvmewin at lists.openfabrics.org Subject: [nvmewin] NVMe device unable to started Hello, I tried to install the release 1.4, but there’s an issue causing the device unable to start. Originally, I use the standard driver from MS for the NVMe device. The device is started and recognized by the disk drive. After I updating the driver to name-1.4 driver, the community 1.0e driver, The device was not started and not recognized by the disk drive. Based on the event log I saw, I only know there’s a problem: 0x15. (firstly configured by oem73.inf, then unable to start due to name) Can you guys have any ideas about how to fix the starting failure. Or what information, Windows log I can look up into? The attached file is the Event Log, Event ID 411. Regards. Jeremy _______________________________________________ nvmewin mailing list nvmewin at lists.openfabrics.org http://lists.openfabrics.org/mailman/listinfo/nvmewin -------------- next part -------------- An HTML attachment was scrubbed... URL: From raymond.c.robles at intel.com Fri Apr 24 23:49:00 2015 From: raymond.c.robles at intel.com (Robles, Raymond C) Date: Sat, 25 Apr 2015 06:49:00 +0000 Subject: [nvmewin] NVMe device unable to started In-Reply-To: <6B417037-CF21-4097-92F7-EE30CE4E4B5A@gmail.com> References: <45DC73B6-C776-41CF-BDD7-52FDD1EF7706@gmail.com> <49158E750348AA499168FD41D88983606B64ECDD@fmsmsx117.amr.corp.intel.com> <6B417037-CF21-4097-92F7-EE30CE4E4B5A@gmail.com> Message-ID: <49158E750348AA499168FD41D88983606B64F292@fmsmsx117.amr.corp.intel.com> If you are using WinDbg, you will have to enable prints for Storport Miniports. The command is ed KD_STORMINIPORT_MASK 0xf For DebugView, you shouldn’t have to modify any settings. But you will need to insure you set all the correct capture settings in the tool itself. Here are 2 links for reference… https://debugviewpp.wordpress.com/2014/01/04/7/ http://nutsaboutnets.com/faqs/dbgview/ Be sure you are capturing kernel output. From: GoogleCalendar [mailto:jeremy.tsai.911 at gmail.com] Sent: Friday, April 24, 2015 5:13 PM To: Robles, Raymond C Subject: Re: [nvmewin] NVMe device unable to started Hi, Thank you for your kind feedback, Sir. I have subscribed the mailing list. The device is Samsung NVMe SSD Controller 171X Express Flash NVMe XS1715, trying to install on a Win 8.1 machine. As for the memory dump and debug outputs, I couldn’t find any MEMORY.DUMP under my /Windows/ directory after I tried to duplicate the issue. Using DebugView, I saw some outputs but couldn’t find anything about NVMe devices. Is there any options or configurations I need to do before logging the debug kernel outputs? Thanks. Regards. Jeremy Robles, Raymond C > 於 2015年4月24日 11:09 寫道: Hi Jeremy, Thanks for reaching out to the OFA NVMe Windows distribution list. First off, could you please officially subscribe to the NVMe mailing list? People who are not on the mailing list are not allowed to send emails to the distribution. As the chair of the OFA NVMe Windows driver, I got the notification of your email and approved it (we get a lot of spam that I have to filter through). As for your issue, a little more information would be helpful: - What NVMe device/drive are you attempting to run? - Windows kernel event logs are not much help. To best analyze your failing scenario, we would need to see a couple of things: o A full kernel memory dump (not a mini-dump), or o The debug kernel output (this can either be form WinDbg or a program like DebugView). Basically what we would need is the print statements from the driver trying to load. If you could provide this info, we could provide more insight into your problem? Thanks, Ray From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of GoogleCalendar Sent: Thursday, April 23, 2015 5:07 PM To: nvmewin at lists.openfabrics.org Subject: [nvmewin] NVMe device unable to started Hello, I tried to install the release 1.4, but there’s an issue causing the device unable to start. Originally, I use the standard driver from MS for the NVMe device. The device is started and recognized by the disk drive. After I updating the driver to name-1.4 driver, the community 1.0e driver, The device was not started and not recognized by the disk drive. Based on the event log I saw, I only know there’s a problem: 0x15. (firstly configured by oem73.inf, then unable to start due to name) Can you guys have any ideas about how to fix the starting failure. Or what information, Windows log I can look up into? The attached file is the Event Log, Event ID 411. Regards. Jeremy _______________________________________________ nvmewin mailing list nvmewin at lists.openfabrics.org http://lists.openfabrics.org/mailman/listinfo/nvmewin -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremy.tsai.911 at gmail.com Tue Apr 28 15:58:25 2015 From: jeremy.tsai.911 at gmail.com (Cheng-Kuan Tsai) Date: Tue, 28 Apr 2015 15:58:25 -0700 Subject: [nvmewin] NVMe device unable to started In-Reply-To: <49158E750348AA499168FD41D88983606B64F292@fmsmsx117.amr.corp.intel.com> References: <45DC73B6-C776-41CF-BDD7-52FDD1EF7706@gmail.com> <49158E750348AA499168FD41D88983606B64ECDD@fmsmsx117.amr.corp.intel.com> <6B417037-CF21-4097-92F7-EE30CE4E4B5A@gmail.com> <49158E750348AA499168FD41D88983606B64F292@fmsmsx117.amr.corp.intel.com> Message-ID: <09EF53DC-0E6E-4FCC-99E7-90A735273BAE@gmail.com> Hi, Sir Before re-installing the NVMe driver and reboot, DebugView is configured with Capture verbose kernel outputs and Log boot. The following outputs are captured by DebugView after reboot. There are some more outputs after the line, WskKnrInit, but seems nothing to do with the NVMe or STORMINI. I also borrowed an Intel SSD with NVMe support. The device works well, recognized and can be formatted. Hope this log will help. Thanks. 00000001 0.00000000 00000002 0.00000030 Copyright(C) Intel Corporation 1994-2012 00000003 0.00000060 Intel Rapid Storage Technology 12.0.1.1018 00000004 0.00002234 iastora::DriverEntry: MultiPhaseResume: ENABLED 00000005 0.02770679 9531250 - STORMINI: alloc: TotalBytesAllocated: 176 Size: 176 VirtStart: FFFFE00151DC8B40 VirtEnd: FFFFE00151DC8BF0 00000006 0.02771071 9531250 - STORMINI: alloc: TotalBytesAllocated: 560 Size: 384 VirtStart: FFFFE00151DBD010 VirtEnd: FFFFE00151DBD190 00000007 0.02870478 9531250 - STORMINI: alloc: TotalBytesAllocated: 3104 Size: 2544 VirtStart: FFFFE00151EC9010 VirtEnd: FFFFE00151EC9A00 00000008 0.02875368 9531250 - STORMINI: alloc: TotalBytesAllocated: 37392 Size: 34288 VirtStart: FFFFE00151E79000 VirtEnd: FFFFE00151E815F0 00000009 0.02875700 9531250 - STORMINI: alloc: TotalBytesAllocated: 37568 Size: 176 VirtStart: FFFFE00151DC3DD0 VirtEnd: FFFFE00151DC3E80 00000010 0.02877270 9531250 - STORMINI: alloc: TotalBytesAllocated: 828096 Size: 790528 VirtStart: FFFFE00154400000 VirtEnd: FFFFE001544C1000 00000011 0.02877874 9531250 - STORMINI: alloc: TotalBytesAllocated: 828272 Size: 176 VirtStart: FFFFE00151E1AF50 VirtEnd: FFFFE00151E1B000 00000012 0.02878236 9531250 - STORMINI: alloc: TotalBytesAllocated: 1618800 Size: 790528 VirtStart: FFFFE001544C1000 VirtEnd: FFFFE00154582000 00000013 0.02878810 9531250 - STORMINI: alloc: TotalBytesAllocated: 1618976 Size: 176 VirtStart: FFFFE00151DCA610 VirtEnd: FFFFE00151DCA6C0 00000014 0.02879142 9531250 - STORMINI: alloc: TotalBytesAllocated: 1625312 Size: 6336 VirtStart: FFFFE00151E3A000 VirtEnd: FFFFE00151E3B8C0 00000015 0.02879594 9531250 - STORMINI: alloc: TotalBytesAllocated: 1625488 Size: 176 VirtStart: FFFFE00151E005F0 VirtEnd: FFFFE00151E006A0 00000016 0.02879927 9531250 - STORMINI: alloc: TotalBytesAllocated: 1629592 Size: 4104 VirtStart: FFFFE00151E38000 VirtEnd: FFFFE00151E39008 00000017 0.02880228 9531250 - STORMINI: alloc: TotalBytesAllocated: 1629768 Size: 176 VirtStart: FFFFE00151DC3F50 VirtEnd: FFFFE00151DC4000 00000018 0.02880560 9531250 - STORMINI: alloc: TotalBytesAllocated: 1654736 Size: 24968 VirtStart: FFFFE00151E82000 VirtEnd: FFFFE00151E88188 00000019 0.03116081 9531250 - STORMINI: alloc: TotalBytesAllocated: 1655464 Size: 728 VirtStart: FFFFE00151DBCD20 VirtEnd: FFFFE00151DBCFF8 00000020 0.03116474 9531250 - STORMINI: alloc: TotalBytesAllocated: 1655472 Size: 8 VirtStart: FFFFE00151EE3220 VirtEnd: FFFFE00151EE3228 00000021 0.03116746 9531250 - STORMINI: alloc: TotalBytesAllocated: 1655480 Size: 8 VirtStart: FFFFE00152A8C080 VirtEnd: FFFFE00152A8C088 00000022 0.03117048 9531250 - STORMINI: alloc: TotalBytesAllocated: 1656208 Size: 728 VirtStart: FFFFE00151DC5330 VirtEnd: FFFFE00151DC5608 00000023 0.03117349 9531250 - STORMINI: alloc: TotalBytesAllocated: 1656216 Size: 8 VirtStart: FFFFE00152A9F390 VirtEnd: FFFFE00152A9F398 00000024 0.03117621 9531250 - STORMINI: alloc: TotalBytesAllocated: 1656224 Size: 8 VirtStart: FFFFE00151EDB7D0 VirtEnd: FFFFE00151EDB7D8 00000025 0.03117923 9531250 - STORMINI: alloc: TotalBytesAllocated: 1656952 Size: 728 VirtStart: FFFFE00151E25190 VirtEnd: FFFFE00151E25468 00000026 0.03118225 9531250 - STORMINI: alloc: TotalBytesAllocated: 1656960 Size: 8 VirtStart: FFFFE00152A9E870 VirtEnd: FFFFE00152A9E878 00000027 0.03118497 9531250 - STORMINI: alloc: TotalBytesAllocated: 1656968 Size: 8 VirtStart: FFFFE00152A923E0 VirtEnd: FFFFE00152A923E8 00000028 0.03118798 9531250 - STORMINI: alloc: TotalBytesAllocated: 1657696 Size: 728 VirtStart: FFFFE00151DCA7A0 VirtEnd: FFFFE00151DCAA78 00000029 0.03119100 9531250 - STORMINI: alloc: TotalBytesAllocated: 1657704 Size: 8 VirtStart: FFFFE00152A943E0 VirtEnd: FFFFE00152A943E8 00000030 0.03119372 9531250 - STORMINI: alloc: TotalBytesAllocated: 1657712 Size: 8 VirtStart: FFFFE00151F66BF0 VirtEnd: FFFFE00151F66BF8 00000031 0.03119644 9531250 - STORMINI: alloc: TotalBytesAllocated: 1658440 Size: 728 VirtStart: FFFFE00151DC1010 VirtEnd: FFFFE00151DC12E8 00000032 0.03119976 9531250 - STORMINI: alloc: TotalBytesAllocated: 1658448 Size: 8 VirtStart: FFFFE00151EDB270 VirtEnd: FFFFE00151EDB278 00000033 0.03120247 9531250 - STORMINI: alloc: TotalBytesAllocated: 1658456 Size: 8 VirtStart: FFFFE00151F857D0 VirtEnd: FFFFE00151F857D8 00000034 0.03120549 9531250 - STORMINI: alloc: TotalBytesAllocated: 1659184 Size: 728 VirtStart: FFFFE00151E2FD20 VirtEnd: FFFFE00151E2FFF8 00000035 0.03120851 9531250 - STORMINI: alloc: TotalBytesAllocated: 1659192 Size: 8 VirtStart: FFFFE00152B49F70 VirtEnd: FFFFE00152B49F78 00000036 0.03121123 9531250 - STORMINI: alloc: TotalBytesAllocated: 1659200 Size: 8 VirtStart: FFFFE00152AA2F70 VirtEnd: FFFFE00152AA2F78 00000037 0.03121515 9531250 - STORMINI: alloc: TotalBytesAllocated: 1666560 Size: 7360 VirtStart: FFFFE00151E36000 VirtEnd: FFFFE00151E37CC0 00000038 0.03122783 9531250 - STORMINI: CStatePackageMgr::reg LakeTinySkuWorkaround 0 00000039 0.03123055 9531250 - STORMINI: alloc: TotalBytesAllocated: 1674752 Size: 8192 VirtStart: FFFFE00151E34000 VirtEnd: FFFFE00151E36000 00000040 0.03124443 9531250 - STORMINI: alloc: TotalBytesAllocated: 3591912 Size: 1917160 VirtStart: FFFFE00154600000 VirtEnd: FFFFE001547D40E8 00000041 0.03131719 9531250 - STORMINI: alloc: TotalBytesAllocated: 3592088 Size: 176 VirtStart: FFFFE00151DC9550 VirtEnd: FFFFE00151DC9600 00000042 0.03132232 9531250 - STORMINI: alloc: TotalBytesAllocated: 3657632 Size: 65544 VirtStart: FFFFE00151E89000 VirtEnd: FFFFE00151E99008 00000043 0.03134888 initParms->cachedMemSize = 0x293018 (2699288) 00000044 0.03135069 initParms->nonCachedMemSize = 0x1270f0 (1208560) 00000045 0.03135220 cachedMemSize + nonCachedMemSize = 0x3ba108 (3907848) 00000046 0.03137454 9531250 - STORMINI: alloc: TotalBytesAllocated: 7565480 Size: 3907848 VirtStart: FFFFE00154800000 VirtEnd: FFFFE00154BBA108 00000047 0.03144065 initOsVersion - isOsVistaOrAbove - TRUE - Maj: 6 Min: 3 00000048 0.03144246 initOsVersion - isOsWin8OrAbove - TRUE - Maj: 6 Min: 3 00000049 0.29456350 IOINIT: Built-in driver \Driver\hwpolicy failed to initialize with status - 0xC000025E 00000050 2.34740210 32656250 - STORMINI: DsmIoctlRequest: CRASHDUMP_FILE_PROFILE: DataSetRangesCount: 1 00000051 2.34740639 32656250 - STORMINI: RANGE0: StartingOffset(Bytes): 0000000FD4D28000 LengthInBytes: 0000000220000000 00000052 2.49084306 34062500 - STORMINI: StorPortInitialize returns Status(0x0) 00000053 7.37320852 Entered WinDriver v10.11 Jungo (c) 1997 - 2010 Build Date: Jan 17 2010 x86_64 64bit SYS. 00000054 7.37326765 kernel_dbg_get_registry: kernel debugger is OFF 00000055 7.72576189 AMD KMD (kernel mode GPU driver) for Windows8, Windows7 and Vista. 00000056 8.77508736 55781250 - STORMINI: DsmIoctlRequest: HIBERNATE_FILE_PROFILE: DataSetRangesCount: 2 00000057 8.77509117 55781250 - STORMINI: RANGE0: StartingOffset(Bytes): 000000028E95E000 LengthInBytes: 00000001265C8000 00000058 8.84462643 56562500 - STORMINI: Access Range, VirtualAddr=0xFFFFD000A75A5000. 00000059 8.84464073 56562500 - STORMINI: NVMeFindAdapter: Stride Size set to 0x4 00000060 8.84468079 56562500 - STORMINI: NVMeEnumNumaCores: # of NUMA node(s) = 1. 00000061 8.84468269 56562500 - STORMINI: NVMeEnumNumaCores: Number of groups = 1. 00000062 8.84468460 56562500 - STORMINI: NVMeEnumNumaCores: Group(0) affinity mask(0xff). 00000063 8.84468746 56562500 - STORMINI: NVMeEnumNumaCores: Total 8 logical processors 00000064 8.84468842 56562500 - STORMINI: NVMeEnumNumaCores: NUMA Node#0 00000065 8.84468937 56562500 - STORMINI: Core mask is 0xff in Group(0) 00000066 8.84469223 56562500 - STORMINI: There are 8 cores in Node#0. 00000067 8.84469318 56562500 - STORMINI: The total number of CPU cores 8. 00000068 8.84481144 56562500 - STORMINI: NVMeEnumMsiMessages: Msg granted=8 00000069 8.84481812 56562500 - STORMINI: NVMeAllocateMem: Succeeded! 00000070 8.84482098 56562500 - STORMINI: NVMeAllocateMem: Succeeded! 00000071 8.84483242 56562500 - STORMINI: NVMeInitSubQueue : SQ 0x0 pSubTDBL 0xFFFFD000A75A6000 at index 0x0 00000072 8.84484386 56562500 - STORMINI: NVMeInitCplQueue : CQ 0x0 pCplHDBL 0xFFFFD000A75A6004 at index 0x1 00000073 8.84485054 56562500 - STORMINI: NVMeEnableAdapter: Setting EN... 00000074 8.84485340 56562500 - STORMINI: NVMeAllocateMem: Succeeded! 00000075 8.84485722 56562500 - STORMINI: NVMeAllocateMem: Succeeded! 00000076 8.84521294 56562500 - STORMINI: NVMeRunningWaitOnRDY: Waiting... 00000077 8.85554409 56718750 - STORMINI: NVMeRunningWaitOnRDY: RDY has been set 00000078 8.87116241 56875000 - STORMINI: NVMeGetIdentifyStructures: IDEN_CONTROLLER 00000079 8.87120914 56875000 - STORMINI: NVMeInitCallback: Driver state: 33 00000080 8.88678741 57031250 - STORMINI: NVMeGetIdentifyStructures: IDEN_NAMESPACE 00000081 8.88678837 57031250 - STORMINI: NVMeGetIdentifyStructures: Get NS INFO for NSID 0x1 tgt lun 0x0 00000082 8.88680840 57031250 - STORMINI: NVMeInitCallback: Driver state: 34 00000083 8.90500259 57187500 - STORMINI: NVMeInitCallback: Driver state: 35 00000084 8.91804981 57343750 - STORMINI: NVMeInitCallback: Driver state: 35 00000085 8.93367100 57500000 - STORMINI: NVMeInitCallback: Driver state: 35 00000086 8.93367290 57500000 - STORMINI: pLbaRangeTypeEntry type : 0x0 lun id 0 nsid 0x1 00000087 8.93367577 57500000 - STORMINI: NVMeSetFeaturesCompletion: FYI LnuExt at 0 has been cleared (NSID not visible) 00000088 8.94929790 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000089 8.94930553 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000090 8.94931602 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x0 ---> QueueID 0x1 00000091 8.94932842 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000092 8.94933510 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000093 8.94934559 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x1 ---> QueueID 0x2 00000094 8.94934750 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000095 8.94935417 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000096 8.94936466 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x2 ---> QueueID 0x3 00000097 8.94936657 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000098 8.94937325 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000099 8.94938374 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x3 ---> QueueID 0x4 00000100 8.94938564 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000101 8.94939232 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000102 8.94940281 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x4 ---> QueueID 0x5 00000103 8.94940472 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000104 8.94941139 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000105 8.94942188 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x5 ---> QueueID 0x6 00000106 8.94943237 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000107 8.94944000 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000108 8.94945049 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x6 ---> QueueID 0x7 00000109 8.94945240 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000110 8.94945908 57656250 - STORMINI: NVMeAllocateMem: Succeeded! 00000111 8.94946957 57656250 - STORMINI: NVMeAllocIoQueues: Core 0x7 ---> QueueID 0x8 00000112 8.94947147 57656250 - STORMINI: NVMeMsiMapCores: Core(0x0)Msg#(0x0) 00000113 8.94947338 57656250 - STORMINI: NVMeMsiMapCores: Core(0x1)Msg#(0x1) 00000114 8.94947433 57656250 - STORMINI: NVMeMsiMapCores: Core(0x2)Msg#(0x2) 00000115 8.94947529 57656250 - STORMINI: NVMeMsiMapCores: Core(0x3)Msg#(0x3) 00000116 8.94947720 57656250 - STORMINI: NVMeMsiMapCores: Core(0x4)Msg#(0x4) 00000117 8.94947910 57656250 - STORMINI: NVMeMsiMapCores: Core(0x5)Msg#(0x5) 00000118 8.94948006 57656250 - STORMINI: NVMeMsiMapCores: Core(0x6)Msg#(0x6) 00000119 8.94948196 57656250 - STORMINI: NVMeMsiMapCores: Core(0x7)Msg#(0x7) 00000120 8.94949150 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x1 pSubTDBL 0xFFFFD000A75A6008 at index 0x2 00000121 8.94951439 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x2 pSubTDBL 0xFFFFD000A75A6010 at index 0x4 00000122 8.94953632 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x3 pSubTDBL 0xFFFFD000A75A6018 at index 0x6 00000123 8.94955730 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x4 pSubTDBL 0xFFFFD000A75A6020 at index 0x8 00000124 8.94957924 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x5 pSubTDBL 0xFFFFD000A75A6028 at index 0xa 00000125 8.94960117 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x6 pSubTDBL 0xFFFFD000A75A6030 at index 0xc 00000126 8.94962311 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x7 pSubTDBL 0xFFFFD000A75A6038 at index 0xe 00000127 8.94964409 57656250 - STORMINI: NVMeInitSubQueue : SQ 0x8 pSubTDBL 0xFFFFD000A75A6040 at index 0x10 00000128 8.94966602 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x1 pCplHDBL 0xFFFFD000A75A600C at index 0x3 00000129 8.94967556 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x2 pCplHDBL 0xFFFFD000A75A6014 at index 0x5 00000130 8.94968605 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x3 pCplHDBL 0xFFFFD000A75A601C at index 0x7 00000131 8.94969559 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x4 pCplHDBL 0xFFFFD000A75A6024 at index 0x9 00000132 8.94970512 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x5 pCplHDBL 0xFFFFD000A75A602C at index 0xb 00000133 8.94971752 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x6 pCplHDBL 0xFFFFD000A75A6034 at index 0xd 00000134 8.94972801 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x7 pCplHDBL 0xFFFFD000A75A603C at index 0xf 00000135 8.94973755 57656250 - STORMINI: NVMeInitCplQueue : CQ 0x8 pCplHDBL 0xFFFFD000A75A6044 at index 0x11 00000136 8.96496868 57812500 - STORMINI: NVMeInitCallback: Driver state: 38 00000137 8.98058510 57968750 - STORMINI: NVMeInitCallback: Driver state: 38 00000138 8.99621010 58125000 - STORMINI: NVMeInitCallback: Driver state: 38 00000139 9.01183414 58281250 - STORMINI: NVMeInitCallback: Driver state: 38 00000140 9.02746010 58437500 - STORMINI: NVMeInitCallback: Driver state: 38 00000141 9.04308605 58593750 - STORMINI: NVMeInitCallback: Driver state: 38 00000142 9.05871105 58750000 - STORMINI: NVMeInitCallback: Driver state: 38 00000143 9.07434368 58906250 - STORMINI: NVMeInitCallback: Driver state: 38 00000144 9.08995247 59062500 - STORMINI: NVMeInitCallback: Driver state: 39 00000145 9.10557652 59218750 - STORMINI: NVMeInitCallback: Driver state: 39 00000146 9.12120247 59375000 - STORMINI: NVMeInitCallback: Driver state: 39 00000147 9.13682747 59531250 - STORMINI: NVMeInitCallback: Driver state: 39 00000148 9.15245247 59687500 - STORMINI: NVMeInitCallback: Driver state: 39 00000149 9.16807747 59843750 - STORMINI: NVMeInitCallback: Driver state: 39 00000150 9.18370247 60000000 - STORMINI: NVMeInitCallback: Driver state: 39 00000151 9.19933605 60156250 - STORMINI: NVMeInitCallback: Driver state: 39 00000152 9.21771336 60312500 - STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa6d07970 BTL 0 0 0 00000153 9.21772003 60312500 - STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa6d07970 BTL 0 0 0 00000154 9.21772194 60312500 - STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa6d07970 BTL 0 0 0 00000155 9.21772575 60312500 - STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa6d07940 BTL 0 0 0 00000156 9.21772861 60312500 - STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa6d07940 BTL 0 0 0 00000157 9.21773148 60312500 - STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0xa6d07940 BTL 0 0 0 00000158 9.23055840 60468750 - STORMINI: NVMeRunning: StorPortReady... 00000159 11.80643463 86250000 - STORMINI: BuildIo: SRB_FUNCTION_WMI 00000160 11.80643654 86250000 - STORMINI: NVMeStartIo: SRB_FUNCTION_WMI 00000161 11.80643940 86250000 - STORMINI: Entering DispatchWmi. WMISubFunction: 0x8 WMI Flags: 0x1 00000162 13.15415096 WERKERNELHOST: ZwOpenKey failed with scode 0xc0000034 00000163 13.15415859 WERKERNELHOST: ZwOpenKey failed with scode 0xc0000034 00000164 14.85404587 116562500 - STORMINI: DsmIoctlRequest: PAGE_FILE_PROFILE: DataSetRangesCount: 1 00000165 14.85404968 116562500 - STORMINI: RANGE0: StartingOffset(Bytes): 0000000FD4D28000 LengthInBytes: 0000000220000000 00000166 14.86392689 116718750 - STORMINI: DsmIoctlRequest: PAGE_FILE_PROFILE: DataSetRangesCount: 1 00000167 14.86393070 116718750 - STORMINI: RANGE0: StartingOffset(Bytes): 000000027C250000 LengthInBytes: 0000000010000000 00000168 15.09635735 Error[PP_PowerPlay]: processpptables.c[974] -- Assertion '(0 != pTable->numEntries)' has failed: Invalid PowerPlay Table! 00000169 18.18836784 150156250 - STORMINI: CStatePackageMgr: set power scheme callback is called 00000170 22.18370628 +++++>WskKnrInit. Regard > Robles, Raymond C 於 2015年4月24日 23:49 寫道: > > If you are using WinDbg, you will have to enable prints for Storport Miniports. The command is > > ed KD_STORMINIPORT_MASK 0xf > ? <> > For DebugView, you shouldn’t have to modify any settings. But you will need to insure you set all the correct capture settings in the tool itself. Here are 2 links for reference… > > https://debugviewpp.wordpress.com/2014/01/04/7/ > http://nutsaboutnets.com/faqs/dbgview/ > > Be sure you are capturing kernel output. > > From: GoogleCalendar [mailto:jeremy.tsai.911 at gmail.com] > Sent: Friday, April 24, 2015 5:13 PM > To: Robles, Raymond C > Subject: Re: [nvmewin] NVMe device unable to started > > Hi, > > Thank you for your kind feedback, Sir. > > I have subscribed the mailing list. > > The device is Samsung NVMe SSD Controller 171X Express Flash NVMe XS1715, > trying to install on a Win 8.1 machine. > > As for the memory dump and debug outputs, > > I couldn’t find any MEMORY.DUMP under my /Windows/ directory after I tried to duplicate the issue. > > Using DebugView, I saw some outputs but couldn’t find anything about NVMe devices. > > Is there any options or configurations I need to do before logging the debug kernel outputs? > > Thanks. > > Regards. > Jeremy > > Robles, Raymond C > 於 2015年4月24日 11:09 寫道: > > Hi Jeremy, > > Thanks for reaching out to the OFA NVMe Windows distribution list. > > First off, could you please officially subscribe to the NVMe mailing list? People who are not on the mailing list are not allowed to send emails to the distribution. As the chair of the OFA NVMe Windows driver, I got the notification of your email and approved it (we get a lot of spam that I have to filter through). > > As for your issue, a little more information would be helpful: > > - What NVMe device/drive are you attempting to run? > - Windows kernel event logs are not much help. To best analyze your failing scenario, we would need to see a couple of things: > o A full kernel memory dump (not a mini-dump), or > o The debug kernel output (this can either be form WinDbg or a program like DebugView). Basically what we would need is the print statements from the driver trying to load. > > If you could provide this info, we could provide more insight into your problem? > > Thanks, > Ray > > From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org ] On Behalf Of GoogleCalendar > Sent: Thursday, April 23, 2015 5:07 PM > To: nvmewin at lists.openfabrics.org > Subject: [nvmewin] NVMe device unable to started > > Hello, > > I tried to install the release 1.4, > > but there’s an issue causing the device unable to start. > > Originally, I use the standard driver from MS for the NVMe device. > > The device is started and recognized by the disk drive. > > After I updating the driver to name-1.4 driver, the community 1.0e driver, > > The device was not started and not recognized by the disk drive. > > Based on the event log I saw, I only know there’s a problem: 0x15. > (firstly configured by oem73.inf, then unable to start due to name) > > Can you guys have any ideas about how to fix the starting failure. > > Or what information, Windows log I can look up into? > > The attached file is the Event Log, Event ID 411. > > > Regards. > Jeremy > _______________________________________________ > nvmewin mailing list > nvmewin at lists.openfabrics.org > http://lists.openfabrics.org/mailman/listinfo/nvmewin -------------- next part -------------- An HTML attachment was scrubbed... URL: