diff options
| author | Andy Lutomirski <luto@kernel.org> | 2016-12-02 21:14:15 -0700 |
|---|---|---|
| committer | Jens Axboe <axboe@fb.com> | 2016-12-13 21:07:08 -0700 |
| commit | d2a61918401ea8db8a6f922e98e86a66b4930cec (patch) | |
| tree | 86146d83d19701e535012a589223db27329fee06 /fs | |
| parent | bcc7f5b4bee8e327689a4d994022765855c807ff (diff) | |
nvme/pci: Log PCI_STATUS when the controller dies
When debugging nvme controller crashes, it's nice to know whether
the controller died cleanly so that the failure is just reflected in
CSTS, it died and put an error in PCI_STATUS, or whether it died so
badly that it stopped responding to PCI configuration space reads.
I've seen a failure that gives 0xffff in PCI_STATUS on a Samsung
"SM951 NVMe SAMSUNG 256GB" with firmware "BXW75D0Q".
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Andy Lutomirski <luto@kernel.org>
Reviewed-by: Keith Busch <keith.busch@intel.com>
Fixed up white space and hunk reject.
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions