All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>,
	Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>,
	Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH 0/4] nvme-pci: support device coredump
Date: Thu, 2 May 2019 06:57:23 -0600	[thread overview]
Message-ID: <20190502125722.GA28470@localhost.localdomain> (raw)
In-Reply-To: <1556787561-5113-1-git-send-email-akinobu.mita@gmail.com>

On Thu, May 02, 2019 at 05:59:17PM +0900, Akinobu Mita wrote:
> This enables to capture snapshot of controller information via device
> coredump machanism, and it helps diagnose and debug issues.
> 
> The nvme device coredump is triggered before resetting the controller
> caused by I/O timeout, and creates the following coredump files.
> 
> - regs: NVMe controller registers, including each I/O queue doorbell
>         registers, in nvme-show-regs style text format.

You're supposed to treat queue doorbells as write-only. Spec says:

  The host should not read the doorbell registers. If a doorbell register
  is read, the value returned is vendor specific.

WARNING: multiple messages have this Message-ID (diff)
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 0/4] nvme-pci: support device coredump
Date: Thu, 2 May 2019 06:57:23 -0600	[thread overview]
Message-ID: <20190502125722.GA28470@localhost.localdomain> (raw)
In-Reply-To: <1556787561-5113-1-git-send-email-akinobu.mita@gmail.com>

On Thu, May 02, 2019@05:59:17PM +0900, Akinobu Mita wrote:
> This enables to capture snapshot of controller information via device
> coredump machanism, and it helps diagnose and debug issues.
> 
> The nvme device coredump is triggered before resetting the controller
> caused by I/O timeout, and creates the following coredump files.
> 
> - regs: NVMe controller registers, including each I/O queue doorbell
>         registers, in nvme-show-regs style text format.

You're supposed to treat queue doorbells as write-only. Spec says:

  The host should not read the doorbell registers. If a doorbell register
  is read, the value returned is vendor specific.

  parent reply	other threads:[~2019-05-02 13:03 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02  8:59 [PATCH 0/4] nvme-pci: support device coredump Akinobu Mita
2019-05-02  8:59 ` Akinobu Mita
2019-05-02  8:59 ` [PATCH 1/4] devcoredump: use memory_read_from_buffer Akinobu Mita
2019-05-02  8:59   ` Akinobu Mita
2019-05-02 12:42   ` Johannes Berg
2019-05-02 12:42     ` Johannes Berg
2019-05-02  8:59 ` [PATCH 2/4] devcoredump: allow to create several coredump files in one device Akinobu Mita
2019-05-02  8:59   ` Akinobu Mita
2019-05-02 12:47   ` Johannes Berg
2019-05-02 12:47     ` Johannes Berg
2019-05-03  3:41     ` Akinobu Mita
2019-05-03  3:41       ` Akinobu Mita
2019-05-02  8:59 ` [PATCH 3/4] nvme-pci: add device coredump support Akinobu Mita
2019-05-02  8:59   ` Akinobu Mita
2019-05-04 10:04   ` Minwoo Im
2019-05-04 10:04     ` Minwoo Im
2019-05-04 14:26     ` Akinobu Mita
2019-05-04 14:26       ` Akinobu Mita
2019-05-04 14:38       ` Minwoo Im
2019-05-04 14:38         ` Minwoo Im
2019-05-04 14:46         ` Minwoo Im
2019-05-04 14:46           ` Minwoo Im
2019-05-02  8:59 ` [PATCH 4/4] nvme-pci: trigger device coredump before resetting controller Akinobu Mita
2019-05-02  8:59   ` Akinobu Mita
2019-05-02 12:57 ` Keith Busch [this message]
2019-05-02 12:57   ` [PATCH 0/4] nvme-pci: support device coredump Keith Busch
2019-05-03  3:38   ` Akinobu Mita
2019-05-03  3:38     ` Akinobu Mita
2019-05-03 12:12     ` Keith Busch
2019-05-03 12:12       ` Keith Busch
2019-05-03 12:20       ` Christoph Hellwig
2019-05-03 12:20         ` Christoph Hellwig
2019-05-04  4:20         ` Akinobu Mita
2019-05-04  4:20           ` Akinobu Mita
2019-05-04  9:40           ` Minwoo Im
2019-05-04  9:40             ` Minwoo Im
2019-05-04 14:36             ` Akinobu Mita
2019-05-04 14:36               ` Akinobu Mita

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=20190502125722.GA28470@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=akinobu.mita@gmail.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.