aboutsummaryrefslogtreecommitdiffstats
path: root/lib/crypto/mpi/mpi-sub-ui.c
diff options
context:
space:
mode:
authorKeith Busch <kbusch@kernel.org>2025-07-15 12:16:27 -0700
committerChristoph Hellwig <hch@lst.de>2025-07-17 17:46:33 +0200
commit5b2c214a95942f7997d1916a4c44017becbc3cac (patch)
treeee04bae5c7f948c90060a469ddd09adf83a36651 /lib/crypto/mpi/mpi-sub-ui.c
parentnvmet: pci-epf: Do not complete commands twice if nvmet_req_init() fails (diff)
downloadlinux-5b2c214a95942f7997d1916a4c44017becbc3cac.tar.gz
linux-5b2c214a95942f7997d1916a4c44017becbc3cac.zip
nvme-pci: try function level reset on init failure
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>
Diffstat (limited to 'lib/crypto/mpi/mpi-sub-ui.c')
0 files changed, 0 insertions, 0 deletions