From: keith.busch@intel.com (Keith Busch)
Subject: I/O 0 QID 0 timeout, disable controller - kernel 4.4 / 4.5 NVMe controller dropouts
Date: Thu, 14 Apr 2016 13:21:14 +0000 [thread overview]
Message-ID: <20160414132113.GA21794@localhost.localdomain> (raw)
In-Reply-To: <1DC99E13-F6CB-4B7F-AFD7-187825DEE523@fastmail.com>
On Thu, Apr 14, 2016@03:13:22PM +1000, Sam McLeod wrote:
> We have 6 Supermicro servers all of the same (or very similar spec),
>
> Since Kernel 4.4 / 4.5 we've had NVMe devices randomly dropping.
> It does not relate to a particular server, disk, controller etc... and downgrading to kernel 4.1.
>
> With kernel 4.4 the servers would load and the disk randomly disappear.
> With 4.5 the server loads with one of the disks missing every time.
>
>
> ```
> [ 66.856719] nvme 0000:03:00.0: I/O 0 QID 0 timeout, disable controller
> [ 66.957911] nvme 0000:03:00.0: Identify Controller failed (-4)
> [ 66.957961] nvme 0000:03:00.0: Removing after probe failure status: -5
> ```
Looks like more fallout from reducing the scope of admin queue completion
polling...
Jens:
Could we please apply the MSI-x fix commit to 4.6 instead of 4.7 so 4.6
isn't equally broken? Currently staged in for-next here:
http://git.kernel.dk/?p=linux-block.git;a=commitdiff;h=788e15abbb9408c9399d7e3445ac9afb3b2fd7d6;hp=e0489487ec9cd79ee1fa0dc5d3789c08b0e51a2c
I'd also like to submit an apporpriate port to stable if no objections.
Thanks,
Keith
next prev parent reply other threads:[~2016-04-14 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 5:13 I/O 0 QID 0 timeout, disable controller - kernel 4.4 / 4.5 NVMe controller dropouts Sam McLeod
2016-04-14 13:21 ` Keith Busch [this message]
2016-04-14 14:08 ` Jens Axboe
2016-04-14 15:23 ` Christoph Hellwig
2016-04-14 20:03 ` Jens Axboe
2016-04-14 23:38 ` Sam McLeod
2016-04-15 16:22 ` Keith Busch
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=20160414132113.GA21794@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.