Announcement

Collapse
No announcement yet.

Kernel error in log file

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Kernel error in log file

    I took a look at my log file after a fresh install of 19.04 and noticed the following error:

    7/19/19 10:31 AM kernel pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
    7/19/19 10:31 AM kernel pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
    7/19/19 10:31 AM kernel pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00001000/00002000
    7/19/19 10:31 AM kernel pcieport 0000:00:1c.5: [12] Timeout

    I am running Kubuntu on a Dell i7 laptop with 8 gigs of memory a 128 gig SSD, and a 1 TB HDD. I have a 535 mb /boot/efi partition on the SSD along with the / "root" partition taking up the remainder of the space. On the HDD I have a 4gig /swap partition with the remainder being the /home partition. Everything is working fine, the system boots fast and all the programs load quickly with no issues. I am not sure if I should try to correct the error or ignore it. Any suggestions or help on how to correct the Kernel error would be appreciated.
    Last edited by Snowhog; Jul 19, 2019, 10:13 AM.

    #2
    Ignore it. There are simply "too many" boot time 'errors' that are simply not critical and don't affect system running at all. IF your system is booting fine, and operating fine, you don't have to worry.
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      Originally posted by Snowhog View Post
      Ignore it. There are simply "too many" boot time 'errors' that are simply not critical and don't affect system running at all. IF your system is booting fine, and operating fine, you don't have to worry.
      Yeah, that was kind of what I was thinking, as long as everything is working as expected there is really no need to try to correct the error. Thank you for the quick reply.

      Comment

      Working...
      X