huge log files eating up disc space

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun »

I think i should move on
Seems like this is not going to fix any soon.
Please suggest some good stable distro

User avatar
catweazel
Level 19
Level 19
Posts: 9910
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: huge log files eating up disc space

Post by catweazel »

UnwantedArun wrote:
Sat Aug 25, 2018 1:47 am
catweazel wrote:
Sat Aug 25, 2018 1:00 am
The problem is a known kernel bug and it can be worked around using the pcie_aspm=off kernel boot parameter in GrUB.
This has disabled the grub. But the problem still continues
What do you mean, it disabled grub?
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.

User avatar
catweazel
Level 19
Level 19
Posts: 9910
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: huge log files eating up disc space

Post by catweazel »

UnwantedArun wrote:
Sat Aug 25, 2018 1:56 am
I think i should move on
Seems like this is not going to fix any soon.
Please suggest some good stable distro
We would all like to get to the bottom of this. I have the very same problem and the fix I posted works fine for me.
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun »

catweazel wrote:
Sat Aug 25, 2018 1:59 am
What do you mean, it disabled grub?
not showing grub. booting directly into arch linux.
It is not even showing the recovery mode options

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun »

Boot into recovery mode, run

Code: Select all

sudo nano /etc/default/grub
Find the line starting with GRUB_CMDLINE_LINUX_DEFAULT and add pcie_aspm=off so that it looks similar to this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=off"
Ctrl+S and Ctrl+X to save and exit, then

Code: Select all

sudo update-grub
and then

Code: Select all

reboot
Is this is the way ?
Or should i add it as another line ?

User avatar
catweazel
Level 19
Level 19
Posts: 9910
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: huge log files eating up disc space

Post by catweazel »

UnwantedArun wrote:
Sat Aug 25, 2018 2:08 am
Boot into recovery mode, run

Code: Select all

sudo nano /etc/default/grub
Find the line starting with GRUB_CMDLINE_LINUX_DEFAULT and add pcie_aspm=off so that it looks similar to this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=off"
Ctrl+S and Ctrl+X to save and exit, then

Code: Select all

sudo update-grub
and then

Code: Select all

reboot
Is this is the way ?
Yes, that's correct.
Or should i add it as another line ?
No.

Here is the relevant part of my grub config:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash elevator=deadline pcie_aspm=off"

Ignore elevator=deadline, otherwise it's exactly the same.

Cheers.
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun »

It disabled my grub menu and didn't fixed the problem.

User avatar
catweazel
Level 19
Level 19
Posts: 9910
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: huge log files eating up disc space

Post by catweazel »

UnwantedArun wrote:
Sat Aug 25, 2018 2:06 am
catweazel wrote:
Sat Aug 25, 2018 1:59 am
What do you mean, it disabled grub?
not showing grub. booting directly into arch linux.
It is not even showing the recovery mode options
Hold down the shift key after the machine's initial BIOS boot sequence but before grub appears.
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun »

I don't care if the grub didn't appeared.
I could manage that.
Please help me to fix the main problem.
not showing grub. booting directly into arch linux.
It is not even showing the recovery mode options

Hold down the shift key after the machine's initial BIOS boot sequence but before grub appears.

gm10
Level 20
Level 20
Posts: 10882
Joined: Thu Jun 21, 2018 5:11 pm

Re: huge log files eating up disc space

Post by gm10 »

Anyway, thanks for the screenshots, I could access them at that newest link. Based on that we know that it's your wi-fi that's connected to the problematic root complex. If you don't need wi-fi we could also just disable the device completely.

I'll also attach you a script, if you extract that to your home folder and then run that with sudo ~/disable-aspm.sh you can disable ASPM on the fly, which should also stop the log spam if disabling ASPM works at all (the GRUB option should have already disabled it but maybe run this just in case you made a mistake with that).
Attachments
disable-aspm.sh.tar.bz2
(3.16 KiB) Downloaded 7 times

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun »

I'll check it. Just a sec

User avatar
catweazel
Level 19
Level 19
Posts: 9910
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: huge log files eating up disc space

Post by catweazel »

UnwantedArun wrote:
Sat Aug 25, 2018 2:25 am
I'll check it. Just a sec
Don't forget to delete the old logs, btw, before you reboot.
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.

Laurent85
Level 16
Level 16
Posts: 6233
Joined: Tue May 26, 2015 10:11 am

Re: huge log files eating up disc space

Post by Laurent85 »

UnwantedArun wrote:
Fri Aug 24, 2018 11:59 pm
I've done this exactly as you said
Created that file.
Put

Code: Select all

:syslogtag, contains, "pcieport"   stop
in to it.
Executed the 3rd query to restart.

But it didn't worked. Same thing happens.
As i said, i done it through recovery mode.
Because i only get 1-2 minutes before the log file eats up my entire disc.
You missed my second post saying the correct rule was actually:

Code: Select all

:msg, contains, "pcieport"   stop
post link
viewtopic.php?p=1516756#p1516684
Image

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun »

Thank you so much guys. It did worked.
But the kern.log and syslog files are still growing. But with low speed.
syslog file

Code: Select all

Aug 25 12:15:53 The256 kernel: [  405.978118] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 25 12:15:58 The256 kernel: [  410.842423] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 25 12:15:58 The256 kernel: [  410.842439] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 25 12:15:58 The256 kernel: [  410.842453] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
Aug 25 12:15:58 The256 kernel: [  410.842463] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 25 12:16:03 The256 kernel: [  415.962287] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 25 12:16:03 The256 kernel: [  415.962306] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 25 12:16:03 The256 kernel: [  415.962324] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
Aug 25 12:16:03 The256 kernel: [  415.962336] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
kern.log file

Code: Select all

Aug 25 12:16:48 The256 kernel: [  461.017626] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 25 12:16:53 The256 kernel: [  465.881997] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 25 12:16:53 The256 kernel: [  465.882012] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 25 12:16:53 The256 kernel: [  465.882025] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
Aug 25 12:16:53 The256 kernel: [  465.882035] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 25 12:16:58 The256 kernel: [  471.005214] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 25 12:16:58 The256 kernel: [  471.005235] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 25 12:16:58 The256 kernel: [  471.005253] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
Aug 25 12:16:58 The256 kernel: [  471.005265] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 25 12:17:03 The256 kernel: [  475.865714] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 25 12:17:03 The256 kernel: [  475.865722] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 25 12:17:03 The256 kernel: [  475.865729] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
Aug 25 12:17:03 The256 kernel: [  475.865733] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)

gm10
Level 20
Level 20
Posts: 10882
Joined: Thu Jun 21, 2018 5:11 pm

Re: huge log files eating up disc space

Post by gm10 »

UnwantedArun wrote:
Sat Aug 25, 2018 2:47 am
Thank you so much guys. It did worked.
What did you do that worked and what did it change exactly, just the log frequency?

Note that syslog just aggregates other logs including kern.log, you don't need to keep looking at it. The only relevant log here is kern.log, and the convenient way to read that is just to run dmesg.

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun »

It reduced the growth speed to about 1kbps
Still both of them are growing.
same error message

Is there's any way to stop this logging process ?

Code: Select all

[    7.808220] systemd[1]: Detected architecture x86-64.
[    7.817541] systemd[1]: Set hostname to <The256>.
[    9.998699] systemd[1]: Created slice User and Session Slice.
[    9.998750] systemd[1]: Reached target Remote File Systems.
[    9.998786] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    9.998795] systemd[1]: Reached target User and Group Name Lookups.
[    9.998884] systemd[1]: Created slice System Slice.
[    9.998899] systemd[1]: Reached target Slices.
[    9.998942] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[   10.693043] EXT4-fs (sda7): re-mounted. Opts: errors=remount-ro
[   11.004313] lp: driver loaded but no devices found
[   11.018980] systemd-journald[346]: Received request to flush runtime journal from PID 1
[   11.214691] ppdev: user-space parallel port driver
[   22.337612] input: Asus Wireless Radio Control as /devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/input/input9
[   22.350328] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
[   22.350336] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
[   22.452917] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[   22.461934] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
[   22.465186] idma64 idma64.0: Found Intel integrated DMA 64-bit
[   22.470569] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
[   22.474548] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   22.476074] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002)
[   22.476417] idma64 idma64.1: Found Intel integrated DMA 64-bit
[   22.484164] i2c_hid i2c-FTE1001:00: i2c-FTE1001:00 supply vdd not found, using dummy regulator
[   22.497999] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   22.498295] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   22.532012] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532019] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.532024] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.532027] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.532164] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532173] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532175] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532180] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532182] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532191] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.532194] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.532197] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.532201] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532342] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532343] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532352] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532354] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532359] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532361] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532366] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532368] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532376] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.532379] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.532381] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.532386] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532527] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532528] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532537] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532539] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532545] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532546] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532555] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.532559] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.532562] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.532566] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532707] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532708] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532717] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532719] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532724] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532726] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532731] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532733] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532741] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.532744] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.532747] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.532751] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532892] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532893] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532903] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532904] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532910] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532911] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532917] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.532918] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.532927] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.532929] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.532932] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.532936] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533077] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533078] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533088] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533089] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533095] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533096] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533101] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533103] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533112] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.533114] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.533117] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.533121] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533262] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533264] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533273] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533275] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533280] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533281] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533287] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533288] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533297] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.533300] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.533302] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.533306] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533447] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533448] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533458] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533459] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533464] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533466] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533472] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533477] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533482] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.533485] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.533487] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.533491] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.533610] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.533955] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.534018] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.534021] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.534024] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.534028] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.534037] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.534040] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.534042] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.534046] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.534187] pcieport 0000:00:1c.5: can't find device of ID00e5
[   22.534217] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.534222] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.534225] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.534228] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.534415] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.534420] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.534423] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.534425] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.534617] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.534622] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.534624] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.534627] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.534812] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.534817] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.534820] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.534822] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.535011] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.535016] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.535019] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.535022] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.535214] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.535219] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.535222] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.535225] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.535408] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.535413] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.535416] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.535419] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.535607] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.535612] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.535615] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.535618] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.535805] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.535811] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.535814] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.535816] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.536007] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.536012] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.536015] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.536018] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.536201] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.536206] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.536209] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.536212] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.536399] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.536404] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.536407] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.536410] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.536599] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.536604] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.536607] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.536610] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.536796] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.536802] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.536805] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.536807] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.536997] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[   22.537002] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[   22.537005] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00000000
[   22.537008] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
[   22.537193] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5


User avatar
catweazel
Level 19
Level 19
Posts: 9910
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: huge log files eating up disc space

Post by catweazel »

UnwantedArun wrote:
Sat Aug 25, 2018 3:03 am
Is there's any way to stop this logging process ?
Possibly. I would look at a BIOS update first, then at a different kernel.
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.

Post Reply

Return to “Newbie Questions”