• Pop!_Planet is still very much under development. Data for the wiki is being sourced from the Arch Linux and Ubuntu wikis, along with a bunch of completely unique content specific to Pop!_OS, and sourcing, converting and updating that content takes time; please be patient. If you can't find what you're looking for here, check the Arch Linux and Ubuntu wikis.
  • Welcome!

    I'll get straight to the point.

    When I started Pop!_Planet, I launched it because I saw a need for a centralized community for Pop!_OS. To be frank, I never expected the level of popularity it has achieved. Over the last year, we have gone from under 50 users, to almost 400 users. That's awesome! However... it also comes with a downside. We are rapidly running out of disk space on our server, and the bandwidth costs go up every month.

    Pop!_Planet is not affiliated with System76 in any way, and is funded completely out of pocket. From day one, I said that I'd never use on-site ads (I hate them as much as you do), so the only monetization we get is through donations. Right now, the donations we receive don't even cover our overhead.

    I know that most users will ignore this message, and that's ok. However, if even a few of our users are willing and able to donate a few dollars to help offset our expenses, it would be greatly appreciated.

    Support Pop!_Planet

    Thank you for your time,

    Dan Griffiths
    Pop!_Planet Founder

Question Beginner Boot drive slowly filling with "PCI error" log files

QuesterLEJ

Member
Mar 28, 2019
49
3
11
38
Hello all,

Relatively new Linux user here. Some time back I posted a thread about my computer suddenly and inexplicably running out of space on its 50 GB SSD boot drive. This has happened a number of times,m and I've resorted to reinstalling Pop!_OS when it does.

However, digging as I get my Linux sealegs has revealed that my drive quite literally fills itself to the brim with log files chronicling the below such string of errors:

Code:
│Apr  5 23:29:50 pop-os kernel: [71136.951156] pcieport 0000:00:1c.6: AER:    [ 0] RxErr                                                                                 │
│Apr  5 23:29:51 pop-os kernel: [71136.956759] pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6                                                        │
│Apr  5 23:29:51 pop-os kernel: [71136.956763] pcieport 0000:00:1c.6: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)                        │
│Apr  5 23:29:51 pop-os kernel: [71136.956765] pcieport 0000:00:1c.6: AER:   device [8086:a116] error status/mask=00000001/00002000                                      │
│Apr  5 23:29:51 pop-os kernel: [71136.956766] pcieport 0000:00:1c.6: AER:    [ 0] RxErr                                                                                 │
│Apr  5 23:29:51 pop-os kernel: [71136.969432] pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6                                                        │
│Apr  5 23:29:51 pop-os kernel: [71136.969437] pcieport 0000:00:1c.6: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)                        │
│Apr  5 23:29:51 pop-os kernel: [71136.969439] pcieport 0000:00:1c.6: AER:   device [8086:a116] error status/mask=00000001/00002000                                      │
│Apr  5 23:29:51 pop-os kernel: [71136.969440] pcieport 0000:00:1c.6: AER:    [ 0] RxErr                                                                                 │
│Apr  5 23:29:51 pop-os kernel: [71136.970632] pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6                                                        │
│Apr  5 23:29:51 pop-os kernel: [71136.970636] pcieport 0000:00:1c.6: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)                        │
│Apr  5 23:29:51 pop-os kernel: [71136.970638] pcieport 0000:00:1c.6: AER:   device [8086:a116] error status/mask=00000001/00002000                                      │
│Apr  5 23:29:51 pop-os kernel: [71136.970640] pcieport 0000:00:1c.6: AER:    [ 0] RxErr                                                                                 │
│Apr  5 23:29:51 pop-os kernel: [71136.986926] pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6                                                        │
│Apr  5 23:29:51 pop-os kernel: [71136.986931] pcieport 0000:00:1c.6: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)                        │
│Apr  5 23:29:51 pop-os kernel: [71136.986933] pcieport 0000:00:1c.6: AER:   device [8086:a116] error status/mask=00000001/00002000                                      │
│Apr  5 23:29:51 pop-os kernel: [71136.986935] pcieport 0000:00:1c.6: AER:    [ 0] RxErr                                                                                 │
│Apr  5 23:29:51 pop-os kernel: [71136.994306] pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6                                                        │
│Apr  5 23:29:51 pop-os kernel: [71136.994310] pcieport 0000:00:1c.6: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)                        │
│Apr  5 23:29:51 pop-os kernel: [71136.994312] pcieport 0000:00:1c.6: AER:   device [8086:a116] error status/mask=00000001/00002000                                      │
│Apr  5 23:29:51 pop-os kernel: [71136.994313] pcieport 0000:00:1c.6: AER:    [ 0] RxErr                                                                                 │
│Apr  5 23:29:51 pop-os kernel: [71137.020268] pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6                                                        │
│Apr  5 23:29:51 pop-os kernel: [71137.020272] pcieport 0000:00:1c.6: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)                        │
│Apr  5 23:29:51 pop-os kernel: [71137.020275] pcieport 0000:00:1c.6: AER:   device [8086:a116] error status/mask=00000001/00002000
How can I stop this error, whatever it means, from occurring or displaying? It obviously details a problem with my PCI bus or some such, but as far as I can tell all my devices are functioning as I'd expect. Also, once I resolve this issue, what's a good tool someone can use to clean log files? I've tried Bleachbit, but it doesn't seem to work well for some reason.

Luke
 

lightsaber

New member
Apr 28, 2020
6
1
4
pci=noaer will disable error reporting for all pci devices.

It's the Wi-Fi card that's throeing all these errors.
It can be selectively disabled,

Follow this

Adapt the values in this file as per your hardware.
 

Members online

Latest projects

Forum statistics

Threads
784
Messages
3,563
Members
721
Latest member
HarryPEthan