[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aP-aD_Mh3ttRkxay@kbusch-mbp>
Date: Mon, 27 Oct 2025 10:13:03 -0600
From: Keith Busch <kbusch@...nel.org>
To: Gerd Bayer <gbayer@...ux.ibm.com>
Cc: Jens Axboe <axboe@...nel.dk>, Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
Niklas Schnelle <schnelle@...ux.ibm.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Chaitanya Kulkarni <kch@...dia.com>,
Wilfred Mallawa <wilfred.mallawa@....com>,
John Garry <john.g.garry@...cle.com>,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/2] nvme-pci: Log failures to probe
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.
Powered by blists - more mailing lists