From: keith.busch@intel.com (Keith Busch)
Subject: [GIT PULL] nvme fix for 4.16-rc6
Date: Thu, 22 Mar 2018 15:09:17 -0600 [thread overview]
Message-ID: <20180322210917.GK12909@localhost.localdomain> (raw)
In-Reply-To: <e8fecf76-08db-154b-fcfb-b15acbc7acac@kernel.dk>
On Wed, Mar 21, 2018@03:44:32PM -0600, Jens Axboe wrote:
>
> [ 30.241598] nvme nvme2: pci function 0000:0b:00.0
> [ 30.247205] nvme nvme3: pci function 0000:81:00.0
> [ 30.252684] nvme nvme4: pci function 0000:82:00.0
> [ 30.258144] nvme nvme5: pci function 0000:83:00.0
> [ 30.263606] nvme nvme6: pci function 0000:84:00.0
> [ 30.360555] nvme nvme3: could not set timestamp (8194)
> [ 30.481649] nvme nvme6: Shutdown timeout set to 8 seconds
> [ 38.790949] nvme nvme4: Device not ready; aborting initialisation
> [ 38.797857] nvme nvme4: Removing after probe failure status: -19
> [ 60.708816] nvme nvme3: I/O 363 QID 8 timeout, completion polled
> [ 60.708820] nvme nvme6: I/O 781 QID 7 timeout, completion polled
> [ 68.068772] nvme nvme2: I/O 769 QID 28 timeout, completion polled
> [ 91.108626] nvme nvme6: I/O 781 QID 7 timeout, completion polled
> [ 98.660581] nvme nvme2: I/O 769 QID 28 timeout, completion polled
> [ 121.702691] nvme nvme6: I/O 100 QID 7 timeout, completion polled
> [ 128.998648] nvme nvme3: I/O 387 QID 4 timeout, completion polled
> [ 152.038523] nvme nvme6: I/O 781 QID 7 timeout, completion polled
>
> This is just doing an fdisk -l after load. No interrupts triggering,
> looking at /proc/interrupts for the queues that timeout.
So no interrupts triggered for the queues that timeout, but you are
getting interrupts for other queues. Are there by chance many spurious
interrupts for those other queues?
next prev parent reply other threads:[~2018-03-22 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 16:01 [GIT PULL] nvme fix for 4.16-rc6 Keith Busch
2018-03-16 16:14 ` Jens Axboe
2018-03-16 16:16 ` Christoph Hellwig
2018-03-16 16:26 ` Jens Axboe
2018-03-16 16:53 ` Keith Busch
2018-03-21 20:59 ` Keith Busch
2018-03-21 21:02 ` Jens Axboe
2018-03-21 21:44 ` Jens Axboe
2018-03-21 22:08 ` Keith Busch
2018-03-22 21:09 ` Keith Busch [this message]
2018-03-22 21:32 ` Jens Axboe
2018-03-22 22:02 ` Keith Busch
2018-03-22 22:09 ` Jens Axboe
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=20180322210917.GK12909@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