From: cgxu519 <cgxu519 at gmx.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] nvme hello_world report error
Date: Thu, 24 Jan 2019 13:35:29 +0800 [thread overview]
Message-ID: <cef933d4-4e4f-6902-4562-9686d6a7f6b2@gmx.com> (raw)
In-Reply-To: CA+0_kCKZQUSFSuwX9OQooHj2RqDXWd36GWPwBnAjUGpB2gBEiw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
Have you unbound kernel driver?
Thanks,
Chengguang
On 1/24/19 1:23 PM, Jing Liu wrote:
> Hi,
>
> I started from trying the hello_world in examples/nvme/ but got errors like
> this:
> """
> Starting SPDK v18.04.1 / DPDK 18.02.0 initialization...
> [ DPDK EAL parameters: hello_world -c 0x1 --file-prefix=spdk0
> --base-virtaddr=0x1000000000 --proc-type=auto ]
> EAL: Detected 16 lcore(s)
> EAL: Auto-detected process type: PRIMARY
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: Debug dataplane logs available - lower performance
> EAL: Multi-process socket /var/run/.spdk0_unix
> EAL: Probing VFIO support...
> EAL: no supported IOMMU extensions found!
> EAL: VFIO support could not be initialized
> Initializing NVMe Controllers
> EAL: PCI device 0000:05:00.0 on NUMA socket 0
> EAL: probe driver: 144d:a802 spdk_nvme
> EAL: Requested device 0000:05:00.0 cannot be used
> no NVMe controllers found
> """
> kernel: 4.7, SSD: Samsung Electronics Co Ltd Device a802
>
> After days of searching I still cannot figure out the problem. I'm
> wondering if I can get some clue about this error?
>
> Thanks,
> Jing
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2019-01-24 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 5:35 cgxu519 [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-24 18:24 [SPDK] nvme hello_world report error Jing Liu
2019-01-24 16:59 Walker, Benjamin
2019-01-24 5:23 Jing Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cef933d4-4e4f-6902-4562-9686d6a7f6b2@gmx.com \
--to=spdk@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox