linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: nvme: controller resets
Date: Wed, 11 Nov 2015 22:14:33 +0000	[thread overview]
Message-ID: <20151111221433.GA11250@localhost.localdomain> (raw)
In-Reply-To: <CAKajsGNGvWw1+B7X8HxdvP0MyvAawb_PStu_adOC8wogOF-Fbg@mail.gmail.com>

On Thu, Nov 12, 2015@03:26:04AM +0530, Vedant Lath wrote:
> [  235.496753] nvme: submit: QID 1 CMD opcode 2 flags 0 cid 1 NSID 1
> [  235.496755] nvme: submit: rsvd2 0 metadata 0 prp1 5897535488 prp2
> 2318221568 slba 41495303 length 0 control 0 dsmgmt 0 reftag 0 apptag 0
> appmask 0

Let's examine the above command.

You've got PRP1 set to 0x15f854000, and length set to 0 (1 block). Based
on other info provided on this device, a block is 4k.

Seeing PRP1 is 4k aligned and you're transferring 4k of data should
mean you only need one PRP. Your command however shows PRP2 is used and
pointing to a list (must be a list rather than data since the offset is
0x100 aligned).

Either your new prints are incomplete, or there's a nasty bug somewhere.

  parent reply	other threads:[~2015-11-11 22:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 14:30 nvme: controller resets Stephan Günther
2015-11-10 15:51 ` Keith Busch
2015-11-10 20:45   ` Stephan Günther
2015-11-10 21:16     ` Vedant Lath
2015-11-10 21:34       ` Stephan Günther
2015-11-10 21:43         ` Vedant Lath
2015-11-10 22:02           ` Stephan Günther
2015-11-10 22:28   ` Vedant Lath
2015-11-11 21:56     ` Vedant Lath
2015-11-11 22:09       ` Stephan Günther
2015-11-12 14:02         ` Vedant Lath
2015-11-11 22:14       ` Keith Busch [this message]
2015-11-12  9:45         ` Vedant Lath
2015-11-12 11:26           ` Vedant Lath
2015-11-16 21:33           ` Stephan Günther

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=20151111221433.GA11250@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;
as well as URLs for NNTP newsgroup(s).