Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Dileep Sankhla <dileepsankhla.ds@gmail.com>
Cc: linux-nvme@lists.infradead.org
Subject: Re: Bug while creating the first i/o completion queue (NVMe over PCIe)
Date: Fri, 9 Aug 2024 09:18:00 -0700	[thread overview]
Message-ID: <ZrZBOMOSAgvd581z@kbusch-mbp> (raw)
In-Reply-To: <CAHxc4btbwU7z1AhYqUBzTeuULpRZbZpDj5Zodvr_p39FNPi44A@mail.gmail.com>

On Thu, Aug 08, 2024 at 06:55:14PM +0530, Dileep Sankhla wrote:
> Raam Raam sa _/\_,
> 
> can anyone immediately help me in solving this issue asap:
> https://github.com/robstat7/Raam/issues/4
>
> In the nvme driver, while creating the first i/o completion queue, it
> is failing with the status code 2 (Invalid Field in Command). The status
> code type is 1 (Command Specific Status).

You're reading the spec wrong. A SCT value of 1 with SC 2 means "Invalid
Queue Size".

And this is the Linux kernel nvme driver mailing list. This isn't the
right place to get help for whatever your driver is.


      reply	other threads:[~2024-08-09 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 13:25 Bug while creating the first i/o completion queue (NVMe over PCIe) Dileep Sankhla
2024-08-09 16:18 ` 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=ZrZBOMOSAgvd581z@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=dileepsankhla.ds@gmail.com \
    --cc=linux-nvme@lists.infradead.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