Keith Busch 524ce0f943 nvme-pci: try function level reset on init failure ... [ Upstream commit 5b2c214a95 ] NVMe devices from multiple vendors appear to get stuck in a reset state that we can't get out of with an NVMe level Controller Reset. The kernel would report these with messages that look like: Device not ready; aborting reset, CSTS=0x1 These have historically required a power cycle to make them usable again, but in many cases, a PCIe FLR is sufficient to restart operation without a power cycle. Try it if the initial controller reset fails during any nvme reset attempt. Signed-off-by: Keith Busch <kbusch@kernel.org> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com> Reviewed-by: Nitesh Shetty <nj.shetty@samsung.com> Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Sasha Levin <sashal@kernel.org>		2025-08-28 16:28:14 +02:00
..
common
host	nvme-pci: try function level reset on init failure	2025-08-28 16:28:14 +02:00
target	nvmet-fcloop: access fcpreq only when holding reqlock	2025-06-19 15:28:43 +02:00
Kconfig
Makefile