Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Gerd Bayer <gbayer@linux.ibm.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
	Sagi Grimberg <sagi@grimberg.me>,
	Niklas Schnelle <schnelle@linux.ibm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Chaitanya Kulkarni <kch@nvidia.com>,
	Wilfred Mallawa <wilfred.mallawa@wdc.com>,
	John Garry <john.g.garry@oracle.com>,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] nvme-pci: Log failures to probe
Date: Mon, 27 Oct 2025 10:13:03 -0600	[thread overview]
Message-ID: <aP-aD_Mh3ttRkxay@kbusch-mbp> (raw)
In-Reply-To: <20251024-nvme_probefail-v3-0-5386f905378b@linux.ibm.com>

On Fri, Oct 24, 2025 at 01:05:30PM +0200, Gerd Bayer wrote:
> occasionally, an NVMe drive fails to reply to MMIO reads despite the PCI
> link being operational. In these situations (obviously not on the
> boot-device :) it is preferred to have this reported in the kernel log
> instead of deducing that something is wrong by comparing expectated vs.
> observed number of nvme devices.

Thanks, applied to nvme-6.19.


      parent reply	other threads:[~2025-10-27 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24 11:05 [PATCH v3 0/2] nvme-pci: Log failures to probe Gerd Bayer
2025-10-24 11:05 ` [PATCH v3 1/2] nvme-pci: Print error message on failure in nvme_probe Gerd Bayer
2025-10-26  7:20   ` Wilfred Mallawa
2025-10-24 11:05 ` [PATCH v3 2/2] nvme-pci: Add debug message on fail to read CSTS Gerd Bayer
2025-10-27 16:13 ` 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=aP-aD_Mh3ttRkxay@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=gbayer@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=john.g.garry@oracle.com \
    --cc=kch@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=schnelle@linux.ibm.com \
    --cc=wilfred.mallawa@wdc.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