[nvmewin] NVMe device unable to started

[Robles, Raymond C]

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 <raymond.c.robles at intel.com<mailto:raymond.c.robles at intel.com>> 於 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> [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<mailto: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<mailto:nvmewin at lists.openfabrics.org>
http://lists.openfabrics.org/mailman/listinfo/nvmewin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150425/92f029e9/attachment.html>