this post was submitted on 31 Mar 2024
10 points (91.7% liked)

Linux

47988 readers
1597 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
10
submitted 7 months ago* (last edited 7 months ago) by Infernal_pizza@lemmy.world to c/linux@lemmy.ml
 

I’ve just installed Arch on my laptop and I’ve noticed the WiFi card seems to be generating a load of errors. I’m also dual booting Ubuntu server and it looks like that’s been generating similar logs although I’ve only ever used Ethernet on there:

Under Arch it has these 2 errors over and over again in journalctl:

Mar 31 00:38:58 Laptop kernel: ath10k_pci 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID)

Mar 31 01:13:08 Laptop kernel: pcieport 0000:00:1c.5: AER: Correctable error message received from 0000:03:00.0

And under Ubuntu it has this instead:

Mar 30 23:28:22 Laptop kernel: pcieport 0000:00:1c.5: AER: can't find device of ID00e5 Mar 30 23:28:22 Laptop kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5 Mar 30 23:28:22 Laptop kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Mar 30 23:28:22 Laptop kernel: pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000 Mar 30 23:28:22 Laptop kernel: pcieport 0000:00:1c.5: [ 0] RxErr

Lspci detects the card as this:

03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 30) Subsystem: Foxconn International, Inc. QCA9377 802.11ac Wireless Network Adapter Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci

But the chip itself is labelled as a Qualcomm Atheros QCNFA435 (which matches what the laptop specs are listed as online)

As far as I can tell the WiFi is working properly, is there anything I should do to fix these errors in either distro or should I just add the pci=noaer parameter to suppress the messages?

top 4 comments
sorted by: hot top controversial new old
[–] db2@lemmy.world 4 points 7 months ago (1 children)

The chip label and driver are correct, and if it's loading ath10k (probably ath10k_pci since it's an m.2 card) then you might have a bad card or damaged pcie (m.2) socket.

Since it's not actually built in you could swap it out for another brand of card like Intel.

[–] Infernal_pizza@lemmy.world 4 points 7 months ago (1 children)

In that case if it still works should I just ignore the error for now and replace the card if it causes any issues?

[–] db2@lemmy.world 3 points 7 months ago* (last edited 7 months ago) (1 children)

I'd say yeah, as long as you're not getting unreasonable slow downs or corrupted data. Without others issues like that I wouldn't go buy a new card right away.

In case you don't know: Slow downs could happen from bus communication errors, corrupt data could also cause slow downs as data gets requested again to fix the bad data, so you could see either problem alone or both together. It's also possible you could have the problem you're seeing right now for years to come and not have it appreciably impact you beyond seeing the error messages.

Edit: it also occurs to me that heat might be the issue, is the machine physically clean inside?

[–] Infernal_pizza@lemmy.world 3 points 7 months ago

That makes sense, for the amount I use this laptop I won’t worry about it for now! It wasn’t noticeably dusty when I opened it yesterday, and the errors occur immediately after booting so I wouldn’t expect it to heat up that fast