Help decipher huge log files eating up hdd and cpu usage

Questions about other topics - please check if your question fits better in another category before posting here
Forum rules
Before you post please read how to get help
Post Reply
isaac12345
Level 2
Level 2
Posts: 51
Joined: Thu Sep 12, 2013 5:17 pm

Help decipher huge log files eating up hdd and cpu usage

Post by isaac12345 » Tue Dec 26, 2017 1:16 pm

Hi all!

Just today my / partition has been filled today with log files ranging from 2.5gb to 4.0gb with the CPU usage constantly at a high 90%. I had a look around the net and found out that I could use the tail command to view the problem. However I cant understand the output and would appreciate if someone could help me out with the problem.

Below is the output of the files from the tail [filename] command-

Kern.log.1 - 4GB

Dec 26 02:24:41 [compname] kernel: [ 324.513791] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00000000
Dec 26 02:24:41 [compname] kernel: [ 324.513800] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Dec 26 02:24:41 [compname] kernel: [ 324.515452] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Dec 26 02:24:41 [compname] kernel: [ 324.515464] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Dec 26 02:24:41 [compname] kernel: [ 324.515473] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00000000
Dec 26 02:24:41 [compname] kernel: [ 324.515479] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Dec 26 02:24:41 [compname] kernel: [ 324.517036] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Dec 26 02:24:41 [compname] kernel: [ 324.517047] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Dec 26 02:24:41 [compname] kernel: [ 324.517056] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00000000
Dec 26 02:24:41 [compname] kernel: [ 324.517064] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)

syslog.1 - 3.8GB

Dec 26 02:24:41 [[compname] kernel: [ 324.513800] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Dec 26 02:24:41 [compname] kernel: [ 324.515452] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Dec 26 02:24:41 [compname] kernel: [ 324.515464] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Dec 26 02:24:41 [compname] kernel: [ 324.515473] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00000000
Dec 26 02:24:41 [compname] kernel: [ 324.515479] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Dec 26 02:24:41 [compname] kernel: [ 324.517036] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Dec 26 02:24:41 [compname] kernel: [ 324.517047] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Dec 26 02:24:41 [compname] kernel: [ 324.517056] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00000000
Dec 26 02:24:41 [compname] kernel: [ 324.517064] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Dec 26 02:24:41 [compname] rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="905" x-info="http://www.rsyslog.com"] rsyslogd was HUPed

syslog - 2.5GB

Dec 26 21:48:34 [compname] kernel: [11580.615517] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Dec 26 21:48:34 [compname] kernel: [11580.616161] pcieport 0000:00:1c.5: can't find device of ID00e5
Dec 26 21:48:34 [compname] kernel: [11580.616175] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Dec 26 21:48:34 [compname] kernel: [11580.616180] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Dec 26 21:48:34 [compname] kernel: [11580.616182] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Dec 26 21:48:34 [compname] kernel: [11580.616184] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Dec 26 21:48:34 [compname] kernel: [11580.616198] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Dec 26 21:48:34 [compname] kernel: [11580.616203] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Dec 26 21:48:34 [compname] kernel: [11580.616205] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000

kern.log - 2.5GB

Dec 26 21:48:34 [compname] kernel: [11580.605761] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Dec 26 21:48:34 [compname] kernel: [11580.605768] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Dec 26 21:48:34 [compname] kernel: [11580.605774] pcieport 0000:00:1c.5: can't find device of ID00e5
Dec 26 21:48:34 [compname] kernel: [11580.605782] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Dec 26 21:48:34 [compname] kernel: [11580.605786] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Dec 26 21:48:34 [compname] kernel: [11580.605788] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Dec 26 21:48:34 [compname] kernel: [11580.605789] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Dec 26 21:48:34 [compname] kernel: [11580.613096] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Dec 26 21:48:34 [compname] kernel: [11580.613767] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Dec 26 21:48:34 [compname] kernel: [11580.613771] pcieport 0000:00:1c.5:

Thanks! :)

User avatar
xenopeek
Level 24
Level 24
Posts: 22180
Joined: Wed Jul 06, 2011 3:58 am
Location: The Netherlands

Re: Help decipher huge log files eating up hdd and cpu usage

Post by xenopeek » Tue Dec 26, 2017 1:44 pm

Google finds that PCI device 8086:9d15 is the "Intel Corporation Sunrise Point-LP PCI Express Root Port #6". It also finds that others have had the same exact error on laptops with Intel Skylake processors. I've not seen a solution except to suggest trying a newer kernel. If you are on Linux Mint 18 or newer, open Update Manager from your menu, go to its View>Linux kernels menu, and in the left sidebar select the newest kernel release and then on the right select the newest version of that. Install that one. Reboot and see if the problem has gone away.

If not, you can try the workaround noted at the top here: https://bugs.launchpad.net/ubuntu/+sour ... ug/1521173. Edit the grub configuration file with this command run from terminal:
gksudo xed /etc/default/grub
Then follow step 1, 2 and 3 from there.

noaer is the kernel boot option to disable PCIE advanced error reporting.
Image

Post Reply

Return to “Other topics”