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: Fri, 15 Apr 2016 16:22:42 +0000 [thread overview]
Message-ID: <20160415162242.GC30635@localhost.localdomain> (raw)
In-Reply-To: <9EB299CB-C271-4F3D-A91A-5D3F5BD7C120@fastmail.com>
On Fri, Apr 15, 2016@09:38:45AM +1000, Sam McLeod wrote:
> Thank you all involved, is there anything we can set in the mean time to prevent this or do you suggest rolling back to a much older kernel?
Hi Sam,
Until we get the fix submitted to stable, you'll unfortunately have
to use kernels older than 4.4 or use 4.6 when the fix is applied to
mainline. There's no viable work-around without changing the driver.
If you want to apply a kernel patch to your own tree in the meantime,
a possible work-around patch is provided here:
http://lists.infradead.org/pipermail/linux-nvme/2016-March/004277.html
prev parent reply other threads:[~2016-04-15 16:22 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
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 [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=20160415162242.GC30635@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.