linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: Missing interrupts in kernel 4.5.0-21.cavium.el7.aarch64
Date: Mon, 9 Oct 2017 08:49:45 -0600	[thread overview]
Message-ID: <20171009144945.GB19329@localhost.localdomain> (raw)
In-Reply-To: <CAGSHeY1uhgMT5oQBt8fxEzO1k=s9q9eBaFGm+oVt9a31_Ga9aA@mail.gmail.com>

On Fri, Oct 06, 2017@02:49:06PM -0700, Yogi Wannabe wrote:
> Our NVMe controller works fine with Kernel 3.9.xx. On kernel
> 4.5.0-21.cavium.el7.aarch64 we see some issues with interrupts.
> 
> Upon nvme driver load it, sends an Identify cmd.. The controller
> processes the cmd and sends a completion interrupt. The driver does
> not see this interrupt nor is it visible in /proc/interrupts. After
> admin timeout duration, driver disables controller and calls
> free_irq(). As soon as free_irq() is called, interrupt reaches driver
> and nvme_irq() is called. The interrupt vector is usually 17.
> 
> Are there any known issues that could be causing this weird behavior?

4.5 removed the completion queue polling, relying exclusively on
interrupts to find these sorts of problems.

After that, lots of people reported failures with device initialization.

I don't believe the root caused was found since no issues were reported
when we enabled MSI/MSIx for early init in 4.6.

For more details, see:

  http://lists.infradead.org/pipermail/linux-nvme/2016-May/004653.html

This unfortauntely was not picked up by the 4.5-stable.

      parent reply	other threads:[~2017-10-09 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 21:49 Missing interrupts in kernel 4.5.0-21.cavium.el7.aarch64 Yogi Wannabe
2017-10-08  6:24 ` Christoph Hellwig
2017-10-09 14:49 ` 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=20171009144945.GB19329@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).