diff options
| author | Keith Busch <[email protected]> | 2025-07-15 19:16:27 +0000 |
|---|---|---|
| committer | Christoph Hellwig <[email protected]> | 2025-07-17 15:46:33 +0000 |
| commit | 5b2c214a95942f7997d1916a4c44017becbc3cac (patch) | |
| tree | ee04bae5c7f948c90060a469ddd09adf83a36651 /lib/crypto/mpi/mpi-add.c | |
| parent | nvmet: pci-epf: Do not complete commands twice if nvmet_req_init() fails (diff) | |
| download | kernel-5b2c214a95942f7997d1916a4c44017becbc3cac.tar.gz kernel-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 <[email protected]>
Reviewed-by: Chaitanya Kulkarni <[email protected]>
Reviewed-by: Nitesh Shetty <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'lib/crypto/mpi/mpi-add.c')
0 files changed, 0 insertions, 0 deletions
