* PCIe errors after resume from hibernate
@ 2023-01-24 8:30 Mika Penttilä
0 siblings, 0 replies; only message in thread
From: Mika Penttilä @ 2023-01-24 8:30 UTC (permalink / raw)
To: linux-pci
Hi,
While debugging failure (in recent mainline linux kernels) to restore
screen contents after hibernate (S4), there seem to be bad looking PCIe
errors in the logs. GPU is not responding, and network card is not
working. Everything is locked up.
Anyone seen similar or any ideas?
--Mika
[ 79.321993] pcieport 0000:6f:02.0: AER: aer_status: 0x00001000,
aer_mask: 0x00000000
[ 79.321997] pcieport 0000:6f:02.0: [12] Timeout
[ 79.321999] pcieport 0000:6f:02.0: AER: aer_layer=Data Link Layer,
aer_agent=Transmitter ID
[ 79.322014] nvme 0000:70:00.0: AER: aer_status: 0x00000001, aer_mask:
0x00000000
[ 79.322016] nvme 0000:70:00.0: [ 0] RxErr (First)
[ 79.322017] nvme 0000:70:00.0: AER: aer_layer=Physical Layer,
aer_agent=Receiver ID
[ 84.371185] {9}[Hardware Error]: Hardware error from APEI Generic
Hardware Error Source: 0
[ 84.371188] {9}[Hardware Error]: It has been corrected by h/w and
requires no further action
[ 84.371190] {9}[Hardware Error]: event severity: corrected
[ 84.371191] {9}[Hardware Error]: Error 0, type: corrected
[ 84.371192] {9}[Hardware Error]: section_type: PCIe error
[ 84.371193] {9}[Hardware Error]: port_type: 0, PCIe end point
[ 84.371193] {9}[Hardware Error]: version: 3.0
[ 84.371194] {9}[Hardware Error]: command: 0x0547, status: 0x0010
[ 84.371195] {9}[Hardware Error]: device_id: 0000:70:00.0
[ 84.371196] {9}[Hardware Error]: slot: 0
[ 84.371196] {9}[Hardware Error]: secondary_bus: 0x00
[ 84.371197] {9}[Hardware Error]: vendor_id: 0x15b7, device_id: 0x5011
[ 84.371198] {9}[Hardware Error]: class_code: 020801
[ 84.371223] nvme 0000:70:00.0: AER: aer_status: 0x00000001, aer_mask:
0x00000000
[ 84.371227] nvme 0000:70:00.0: [ 0] RxErr (First)
[ 84.371229] nvme 0000:70:00.0: AER: aer_layer=Physical Layer,
aer_agent=Receiver ID
[ 84.382169] nvme 0000:70:00.0: AER: aer_status: 0x00000001, aer_mask:
0x00000000
[ 84.382173] nvme 0000:70:00.0: [ 0] RxErr (First)
[ 84.382176] nvme 0000:70:00.0: AER: aer_layer=Physical Layer,
aer_agent=Receiver ID
[ 85.650235] nvme 0000:70:00.0: AER: aer_status: 0x00000001, aer_mask:
0x00000000
[ 85.650241] nvme 0000:70:00.0: [ 0] RxErr (First)
[ 85.650243] nvme 0000:70:00.0: AER: aer_layer=Physical Layer,
aer_agent=Receiver ID
[ 85.804828] No UUID available providing old NGUID
[ 86.367475] nvme 0000:70:00.0: AER: aer_status: 0x00000001, aer_mask:
0x00000000
[ 86.367482] nvme 0000:70:00.0: [ 0] RxErr (First)
[ 86.367483] nvme 0000:70:00.0: AER: aer_layer=Physical Layer,
aer_agent=Receiver ID
[ 86.851162] nvme 0000:70:00.0: AER: aer_status: 0x00000001, aer_mask:
0x00000000
[ 86.851171] nvme 0000:70:00.0: [ 0] RxErr (First)
[ 86.851174] nvme 0000:70:00.0: AER: aer_layer=Physical Layer,
aer_agent=Receiver ID
[ 87.154895] nvme 0000:70:00.0: AER: aer_status: 0x00000001, aer_mask:
0x00000000
[ 87.154901] nvme 0000:70:00.0: [ 0] RxErr (First)
[ 87.154903] nvme 0000:70:00.0: AER: aer_layer=Physical Layer,
aer_agent=Receiver ID
[ 87.481288] nvme 0000:70:00.0: AER: aer_status: 0x00000001, aer_mask:
0x00000000
[ 87.481294] nvme 0000:70:00.0: [ 0] RxErr (First)
[ 87.481296] nvme 0000:70:00.0: AER: aer_layer=Physical Layer,
aer_agent=Receiver ID
[ 88.318209] nvme 0000:70:00.0: AER: aer_status: 0x00000001, aer_mask:
0x00000000
[ 88.318216] nvme 0000:70:00.0: [ 0] RxErr (First)
[ 88.318218] nvme 0000:70:00.0: AER: aer_layer=Physical Layer,
aer_agent=Receiver ID
[ 88.578533] nvme 0000:70:00.0: AER: aer_status: 0x00000001, aer_mask:
0x00000000
[ 88.578540] nvme 0000:70:00.0: [ 0] RxErr (First)
[ 88.578544] nvme 0000:70:00.0: AER: aer_layer=Physical Layer,
aer_agent=Receiver ID
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-01-24 8:31 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-24 8:30 PCIe errors after resume from hibernate Mika Penttilä
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).