You are not logged in.

#1 2017-12-15 02:50:12

sashok724
Member
Registered: 2013-12-17
Posts: 19

Startup errors (warnings) about PCI-E device and Wi-Fi

Every time i boot Arch Linux, i see following error messages:

[    0.705024] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID)
[    0.705053] pcieport 0000:00:1c.4:   device [8086:a294] error status/mask=00000001/00002000                                                                                                                                                     
[    0.705076] pcieport 0000:00:1c.4:    [ 0] Receiver Error         (First)

Also there's error (warning) messages when connecting to Wi-Fi network, but Wi-Fi itself works perfectly fine and stable at full speed:

[  956.840787] brcmfmac: brcmf_p2p_set_firmware: failed to update device address ret -23
[  956.841055] brcmfmac: brcmf_p2p_create_p2pdev: set p2p_disc error
[  956.841064] brcmfmac: brcmf_cfg80211_add_iface: add iface p2p-dev-wlp4s0 type 10 failed: err=-23
[  960.070807] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23

Is there any way to 'fix' such errors without turning any functionality off?
BTW, my Wi-Fi card is ASUS PCE-AC88 with firmware extracted from router with same chipset

Offline

#2 2017-12-15 15:44:00

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: Startup errors (warnings) about PCI-E device and Wi-Fi

For the first one I'd say you should double check the card is properly seated and if the contacts are clean, if that doesn't help try connecting it in another pcie slot if possible and try the card in another known good motherboard, if the errors persist I'd consider broken hardware, either due to malfunction or not complying with some pcie specification. If the errors go away in another board then I would suspect something wrong with your motherboard.

For the second batch of errors, at first sight they seems to be software/firmware related and probably not related to the first batch of errors (specially because both are not close in time) but I would try to solve the hardware errors first just to rule out any possible influence.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

Board footer

Powered by FluxBB