Bug 199695

Summary: AER corrected errors from Samsung NVMe during suspend
Product: Drivers Reporter: Bjorn Helgaas (bjorn)
Component: PCIAssignee: drivers_pci (drivers_pci)
Status: NEW ---    
Severity: normal    
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: v4.16 Subsystem:
Regression: No Bisected commit-id:
Attachments: dmesg log
lspci -vv output

Description Bjorn Helgaas 2018-05-11 15:58:31 UTC 
From Jesse Vincent <jesse@fsck.com> via Andrew Lutomirski <amluto@gmail.com>:

A friend of mine [Jesse] has a brand new LG laptop that has intermittent NVMe
failures.  They mostly happen during a suspend/resume cycle
(apparently during suspend, not resume).  Unlike the earlier
Dell/Samsung issue, the NVMe device isn't completely gone -- MMIO
reads fail, but PCI configuration space is apparently still there:

nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10

and it comes with a nice AER dump:

[12720.894411] pcieport 0000:00:1c.0: AER: Multiple Corrected error
received: id=00e0
[12720.909747] pcieport 0000:00:1c.0: PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e0(Transmitter ID)
[12720.909751] pcieport 0000:00:1c.0:   device [8086:9d14] error
status/mask=00001001/00002000
[12720.909754] pcieport 0000:00:1c.0:    [ 0] Receiver Error         (First)
[12720.909756] pcieport 0000:00:1c.0:    [12] Replay Timer Timeout
...
Comment 1 Bjorn Helgaas 2018-05-11 15:59:25 UTC 
Created attachment 275919 [details]
dmesg log
Comment 2 Bjorn Helgaas 2018-05-11 15:59:43 UTC 
Created attachment 275921 [details]
lspci -vv output