(In reply to Bjarne Thomsen from comment #0)
> Created attachment 8143 [details]
> Output from dmesg with lots of "PCIe Bus Error".
> 
> I noticed this large amount og "PCIe Bus Error". I am not sure if they are
> a problem. However, at the same time the hardlock on Wi-Fi had gone!

the complete error, here unrepeated, is:

[    7.109859] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[    7.109867] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[    7.109914] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
[    7.110286] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)



And in your lspcidrake -v output in attachment 8050 [details] of your wifi bug 18756
device [8086:9d15] is:

shpchp          : Intel Corporation|Sunrise Point-LP PCI Express Root Port #6 [BRIDGE_PCI] (vendor:8086 device:9d15) (rev: f1)

However, I don't know what's next, just guessing that assigning this report to tmb is a good idea.

Please reassign if needed :-)

CC: (none) => marja11
Assignee: bugsquad => tmb

Apparently, at least some "PCIe Bus Error"s are related to Wi-Fi.
When I blacklisted asus_nb_wmi and asus_wmi dmesg produced a lot
of PCIe Bus Errors, but Wi-Fi now works.
I am not sure what asus_nb_wmi is doing. Maybe it prevents me
from using Wi-Fi when I am not using secure boot.

Created attachment 8149 [details]
Output from lspcidrake -v

Device 9d15 is PCI Express Root port #6
Apparently no problems with port #5.
WiFi problem has been solved with wapf=4

After a short while there are about 600 Mb of errors in errors.log and info.log
in /var/log/kernel
The same amout of error logs is found in messages, syslog and journal.
Accordingly the PC runs into no space due to 3Gb+ log files.
I have limited space for Mageia6 as it is installed in the space reclaimed
from Windows 10.

This is really too old to be relevant.

Then you can close it as you are the reporter

Resolution: (none) => OLD
Status: NEW => RESOLVED