linux-kernel - bug: many pcieport errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Thu, 2 Aug 2018 19:16:16 +0200
From:   Berto Gerard <gerard.berto@...autia.com>
To:     linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: bug: many pcieport errors

Hello,

I help on the Ubuntu French forum and we see many times the same 
problem: kern.log and syslog are filled with an error which is repeated. 
Here is the error:

|[ 22.275320] pcieport 0000:00:1c.4: device [8086:9d14] error 
status/mask=00000001/00000000 [ 22.275322] pcieport 0000:00:1c.4: [ 0] 
Receiver Error (First) [ 22.277322] pcieport 0000:00:1c.4: PCIe Bus 
Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID) [ 
22.277325] pcieport 0000:00:1c.4: device [8086:9d14] error 
status/mask=00000001/00000000 [ 22.277327] pcieport 0000:00:1c.4: [ 0] 
Receiver Error (First) [ 22.278793] pcieport 0000:00:1c.4: PCIe Bus 
Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID) [ 
22.278795] pcieport 0000:00:1c.4: device [8086:9d14] error 
status/mask=00000001/00000000 [ 22.278796] pcieport 0000:00:1c.4: [ 0] 
Receiver Error (First) [ 22.279211] pcieport 0000:00:1c.4: PCIe Bus 
Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID) [ 
22.279214] pcieport 0000:00:1c.4: device [8086:9d14] error 
status/mask=00000001/00000000 [ 22.279216] pcieport 0000:00:1c.4: [ 0] 
Receiver Error (First) [ 22.279605] pcieport 0000:00:1c.4: PCIe Bus 
Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID) [ 
22.279608] pcieport 0000:00:1c.4: device [8086:9d14] error 
status/mask=00000001/00000000 [ 22.279610] pcieport 0000:00:1c.4: [ 0] 
Receiver Error (First) [ 22.399607] pcieport 0000:00:1c.4: PCIe Bus 
Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID) [ 
22.399611] pcieport 0000:00:1c.4: device [8086:9d14] error 
status/mask=00000001/00000000 [ 22.399613] pcieport 0000:00:1c.4: [ 0] 
Receiver Error (First) [ 22.538521] pcieport 0000:00:1c.4: PCIe Bus 
Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID) [ 
22.538525] pcieport 0000:00:1c.4: device [8086:9d14] error 
status/mask=00000001/00000000 [ 22.538527] pcieport 0000:00:1c.4: [ 0] 
Receiver Error (First) |||||

||This problem leads to filled hard drive (and it's fast!) for Ubuntu 
16.04 versions, and for the 18.04.1 version, the live session can't be 
used: screen remains black with these errors written in white.

These two boot parameters avoid the problem but they have drawbacks, so 
it's a just a bypass solution: "pci=noaer" or "pci_aspm=off"

We also see that

|[8086:9d14]|

in the error is an intel bridge (Skylake architecture), and

|0000:00:1c.4|

is the RTL8723BE wifi card.
Many of the Ubuntu's French forum threads have the RTL8723BE card, and 
every thread has this intel bridge. So I don't know if it's specific of 
the RTL8723BE card, but on my pc, I don't have the problem and I have 
the RTL8723BE card but not the same intel bridge (Haswell architecture) 
and I tried with Xubuntu 16.04.1, Ubuntu 16.04.3 and Xubuntu 18.04.1 and 
no errors logged.

When we do
sudo modprobe -r rtl8723be
the errors stop logged. So maybe the boot parameter 
"modprobe.blacklist=rtl8723be" could be useful for tests.

That's all we know. If you have questions or some tests for finding 
where the problem is, don't hesitate.
Best regards

Content of type "text/html" skipped