From: keith.busch@intel.com (Keith Busch)
Subject: NVME card works on kernel 3.19.8 but not on 4.19.31
Date: Sun, 6 Aug 2017 23:17:40 -0400 [thread overview]
Message-ID: <20170807031740.GC842@localhost.localdomain> (raw)
In-Reply-To: <CAGSHeY0H82iiKtYDiAmqdH_C6PytitvfkrmgYmQVcFnnmVWhmA@mail.gmail.com>
On Fri, Aug 04, 2017@06:04:23PM -0700, Yogi Wannabe wrote:
> Hi,
>
> Our NVME card works fine on Centos 7.3 with kernel 3.19.8. But with
> Centos 7.3 and kernel 4.19.31 the driver
>
> 1. detects the board
> 2. creates I/O submission and completion queues
> 3. sends identify cmd to retrive controller information
> 4. /dev/nvme0 node is created.
>
> However, /dev/nvme0n1 is not created and the drive does not show up in
> /proc/partitions. Two things we have observed are that
>
> 1. identify cmd to retrive namespace information is not called
> 2. BLK_DEV_NVME_SCSI is not set in .config file on the running kernel
>
> Any clues on what could be going wrong?
I'm not actually sure what kernel you're using since 4.19 doesn't exist
yet. I'll assume that was just a typo.
Usually that would mean the drive failed to create IO queues, or it simply
doesn't have any namespaces. If the problem is the former, you should see
a message in the kernel log/dmesg that says "Could not set queue count".
If you don't see any error messages, could you attach the identify
command data? As long as /dev/nvme0 was created, you should be able to
get that information from the shell with nvme-cli. The command to run is
'nvme id-ctrl /dev/nvme0'.
I think Centos 7.3 makes nvme-cli available as a package, so you may be
able to can get it with 'yum install nvme-cli'. Otherwise, you can get
the source from here:
https://github.com/linux-nvme/nvme-cli
prev parent reply other threads:[~2017-08-07 3:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 1:04 NVME card works on kernel 3.19.8 but not on 4.19.31 Yogi Wannabe
2017-08-07 3:17 ` Keith Busch [this message]
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=20170807031740.GC842@localhost.localdomain \
--to=keith.busch@intel.com \
/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