From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH v2] nvme/pci: Log PCI_STATUS when the controller dies
Date: Fri, 02 Dec 2016 14:19:05 -0800 [thread overview]
Message-ID: <1480717145.26702.28.camel@linux.intel.com> (raw)
In-Reply-To: <f028ad4073488a571f2e19e19ccff0f6daa4af33.1480639321.git.luto@kernel.org>
On Thu, 2016-12-01@16:42 -0800, Andy Lutomirski wrote:
> When debugging nvme controller crashes, it's nice to know whether
> the controller died cleanly so that the failure is just reflected in
> CSTS, it died and put an error in PCI_STATUS, or whether it died so
> badly that it stopped responding to PCI configuration space reads.
>
> Signed-off-by: Andy Lutomirski <luto at kernel.org>
> ---
> ?drivers/nvme/host/pci.c | 20 ++++++++++++++++----
> ?1 file changed, 16 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> index 0248d0e21fee..f8dd83be01d9 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/drivers/nvme/host/pci.c
> @@ -1292,10 +1292,22 @@ static void nvme_watchdog_timer(unsigned long
> data)
> ?
> ? /* Skip controllers under certain specific conditions. */
> ? if (nvme_should_reset(dev, csts)) {
> - if (!nvme_reset(dev))
> - dev_warn(dev->dev,
> - "Failed status: 0x%x, reset
> controller.\n",
> - csts);
> + if (!nvme_reset(dev)) {
> + /* Read a config register to help see what
> died. */
> + u16 pci_status;
> + int result;
> +
> + result =
> pci_read_config_word(to_pci_dev(dev->dev),
> + ??????PCI_STATUS,
> &pci_status);
> + if (result == PCIBIOS_SUCCESSFUL)
> + dev_warn(dev->dev,
> + ?"controller is down; will
> reset: CSTS=0x%x, PCI_STATUS=0x%hx\n",
> + ?csts, pci_status);
> + else
> + dev_warn(dev->dev,
> + ?"controller is down; will
> reset: CSTS=0x%x, PCI_STATUS read failed (%d)\n",
> + ?csts, result);
> + }
> ? return;
Looks a lot more like what Keith suggested.
Reviewed-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
prev parent reply other threads:[~2016-12-02 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 0:42 [PATCH v2] nvme/pci: Log PCI_STATUS when the controller dies Andy Lutomirski
2016-12-02 13:26 ` Christoph Hellwig
2016-12-02 16:57 ` Andy Lutomirski
2016-12-02 22:19 ` J Freyensee [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=1480717145.26702.28.camel@linux.intel.com \
--to=james_p_freyensee@linux.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).