[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251022-nvme_probefail-v2-0-26bbdf94280e@linux.ibm.com>
Date: Wed, 22 Oct 2025 12:33:15 +0200
From: Gerd Bayer <gbayer@...ux.ibm.com>
To: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>
Cc: Niklas Schnelle <schnelle@...ux.ibm.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Chaitanya Kulkarni <kchk@...dia.com>,
Wilfred Mallawa <wilfred.mallawa@....com>,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org,
Gerd Bayer <gbayer@...ux.ibm.com>, Chaitanya Kulkarni <kch@...dia.com>
Subject: [PATCH v2 0/2] nvme-pci: Log failures to probe
Hi,
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.
- 1/2 adds a clear indication that the device driver failed to probe an
NVMe drive and will not register a nvme device.
- 2/2 adds a debug log that allows to further zoom in on the exact
failure
I've split this into two patches, since 2/2 might be less important wrt
to back-ports, etc.
Thanks,
Gerd
Signed-off-by: Gerd Bayer <gbayer@...ux.ibm.com>
---
Changes in v2:
- Patch 1/2:
- Replace dev_err() with dev_err_probe(), now last before return
- Drop R-b from Wilfred Mallawa
- Patch 2/2: Reword as suggested by Christoph Hellwig, pick up R-b's
- Link to v1: https://lore.kernel.org/r/20251020-nvme_probefail-v1-0-a420046d98f0@linux.ibm.com
---
Gerd Bayer (2):
nvme-pci: Print error message on failure in nvme_probe
nvme-pci: Add debug message on fail to read CSTS
drivers/nvme/host/pci.c | 2 ++
1 file changed, 2 insertions(+)
---
base-commit: 211ddde0823f1442e4ad052a2f30f050145ccada
change-id: 20251015-nvme_probefail-3976120a4719
Best regards,
--
Gerd Bayer <gbayer@...ux.ibm.com>
Powered by blists - more mailing lists