aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorAndy Lutomirski <[email protected]>2016-12-02 21:14:15 -0700
committerJens Axboe <[email protected]>2016-12-13 21:07:08 -0700
commitd2a61918401ea8db8a6f922e98e86a66b4930cec (patch)
tree86146d83d19701e535012a589223db27329fee06 /tools/perf/scripts/python
parentbcc7f5b4bee8e327689a4d994022765855c807ff (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 <[email protected]> Signed-off-by: Andy Lutomirski <[email protected]> Reviewed-by: Keith Busch <[email protected]> Fixed up white space and hunk reject. Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions