Pcie bus error severity corrected type data link layer transmitter id - Исправление ошибок и поиск оптимальных решений проблем

После обновления Linux, при следующем выключении компьютера на экран повалилась куча одинаковых сообщений об ошибке: «pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer«. Причём длится это безобразие довольно долго, так что рука тянется принудительно выключить компьютер с кнопки, что я пару раз и проделал, пока не нашёл решения проблемы.

Как я уже сказал выше, выключение или перезагрузка компьютера стала адовой процедурой — лог повторяющихся ошибок бежал по экрану в течении (!) двух минут. Оказалось, что данная проблема постигла практически всех владельцев интеловских процессоров и, по всей видимости, связана с попытками понизить питание на порту PCIe. На тематических Linux-форумах предлагается добавить следующие два параметра при загрузке ядра:

pci = nomsi — отключает использование прерываний MSI; pci = noaer — отключает расширенный отчёт об ошибках ядра.

Однако, возвращаться к использованию устаревших методов доставки прерываний мне совсем не хотелось — костыли, так себе. Решил пойти другим путём и просто отключить технологию ASPM (Active-State Power Management).

ASPM позволяет управлять энергопотреблением шин PCI Express (PCIe) посредством их перевода в энергосберегающий режим, если устройство не используются. В то же время, активация ASPM приводит к задержке ответа от устройств, так как требуется некоторое время на переключение режимов работы шины.

Поведением ASPM можно управлять, добавив параметр pcie_aspm в загрузчик или внеся изменения в файле /sys/module/pcie_aspm/parameters/policy (pcie_aspm=off отключает ASPM, а pcie_aspm=force принудительно задействует, даже на поддерживающих технологию устройствах). Я подправил загрузчик GRUB:

# открываем файл настроек grub в текстовом редакторе
sudo editor /etc/default/grub
# добавляем параметр pcie_aspm=off
GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=off"
# сохраняем и обновляем загрузчик
sudo update-grub

В моём случае, ошибку выдавал встроенный Wi-Fi адаптер, который в принципе не отличался стабильностью в работе и постоянно отваливался. Отдельно отключить энергосбережение для WiFi поможет продвинутая консольная утилита для управления питанием TLP (/etc/default/tlp):

WIFI_PWR_ON_AC=off
WIFI_PWR_ON_BAT=off

Подписывайтесь на канал

Яндекс.Дзен

и узнавайте первыми о новых материалах, опубликованных на сайте.

Источник

Recently I was trying to install Mint on several nodes in my institute. At times, I was not able to install and got lots of ‘PCIe Bus’ errors on the screen. I have also observed similar issue with Ubuntu 18.04.

I got stuck into it for more than a month, after using many solution and observations (solution is the same, but observation and treatment may be different), I found something which was helpful for me and I think could be helpful for other Ubuntu and Linux Mint users.

Observations about PCIe Bus Error severity Corrected

It happened with my HP system and it seems that there is some compatibility issues with the HP hardware. The PCIe Bus Error is basically the Linux kernel reporting the hardware issue.

This error reporting turns into nightmare because of the frequency of error messages generated by the system. I have noticed in various Linux forums that many HP user have encountered this error, probably HP needs to improve Linux support for their hardware.

Do note that this doesn’t necessarily mean that you cannot use Linux on your HP system. You might be able to use Linux like everyone else. It’s just that seeing this message flashing on the screen on every boot is annoying and sometimes, it could lead to bigger troubles.

If the system keeps on reporting, it will increase the log size. If you have limited space for root, it could mean that your system will stuck at the black screen displaying the PCIe error message and your system won’t be able to boot.

Now that you know a few things, let’s see how to tackle this error.

Handling PCIe Bus Error messages if you can boot in to your Linux system

If you see the PCIe Bus Error message on the screen while booting but you are still able to log in, you could do a workaround for this annoyance.

You can do little on the hardware compatibility front. I mean you (most probably) cannot go ahead and start coding drivers for your hardware or fix the existing drivers code. If your system works fine, your main concern should be that too much of error reporting doesn’t eat up the disk space.

In that regard, you can change the Linux kernel parameter and ask it to stop reporting the PCIe errors. To do that, you need to edit the grub configuration.

Basically, you just have to use a text editor for editing the file.

First thing first, make a backup of your grub config file so that you can revert in case if you are not sure of things you changed. Open a terminal and use the following command:

cp /etc/default/grub ~/grub.back

Now open the file with Gedit for editing:

sudo gedit /etc/default/grub

Look for the line that has GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”

Add pci=noaer in this line. AER stands for Advanced Error Reporting and ‘noaer’ asks the kernel to not use/log Advanced Error Reporting. The changed line should look like this:

 GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"

Once you have saved the file, you should update the grub using this command:

sudo update-grub

Restart Ubuntu and you shouldn’t see the ‘PCIe Bus Error severity Corrected messages’ anymore.

If this doesn’t fix the issue for you, you can try to change other kernel parameters.

Further troubleshooting: Disable MSI

Now you are resorting to hit and trial. You may try disabling MSI. Though Linux kernel supports MSI for several years now, a wrong implementation of MSI from some hardware manufacturer may lead to the PCIe errors.

The drill is practically the same as you saw in the previous section. You edit the grub configuration and make the GRUB_CMDLINE_LINUX_DEFAULT line look like this:

 GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi"

Update grub and reboot the system:

sudo update-grub

Even further troubleshooting: Disable mmconf

I know it’s getting repetitive but if you are still facing the issue, it could be worth to give this a last try. This time, disable the mmconf parameter in Linux kernel.

mmconf means memory mapped config and if you have an old computer, a buggy BIOS may lead to this issue.

The steps remain the same. Just change the line GRUB_CMDLINE_LINUX_DEFAULT in your grub config to make it look like:

 GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nommconf"

Can’t boot! How to edit grub config now?

In some cases, if you are not even able to boot at all, perhaps your root is out of space. An idea here would be to delete old log files and see if you could boot now and if yes, change the grub config.

On reboot, if you stuck with logs on the screen and do a hard boot (use power button to turn it off and on again). When you power on, choose to go in to recovery mode from the grub screen. It should be under Advanced options.

Advanced boot options in Grub menu of Ubuntu

If your system doesn’t show the grub screen, press and hold shift key at boot. In some systems, pressing the Esc key brings the grub screen.

In the advanced option->recovery mode:

Drop into root shell:

Root shell prompt allows you to reset password in Ubuntu

If you use the ls command to find large files, you’ll see that sys.log and kern.log take huge space:

ls -s -S /var/log

You can empty the log files in Linux command line this way:

$ > syslog
$ > kern.log

Once that is done, reboot your system. You should be able to log in. You should quickly change the grub parameters as discussed above. Adding pci=noaer should help you in this case.

I know it’s more of a workaround than solution. But this is something that troubled me long and helped me get around the error. Otherwise I had to reinstall the system.

I just wanted to share what worked for me with the community here. I hope it helps you as well.

This article is written by Arun Shrimali. Arun is IT Head at Resonance Institute in India and he tries to implement Open Source Software across his organization.

The article has been edited by Abhishek Prakash.

Источник

Forum
The Ubuntu Forum Community
Ubuntu Official Flavours Support
Installation & Upgrades
[ubuntu] PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Just installed the latest (18.10 LTS) on brand new desktop (see attached spec).

The problem is that the PC hangs after being up for a few hours.

Before rebooting I found many of the following errors

Code:

Sep  4 22:52:24 inges2 kernel: [11889.915252] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Transmitter ID)
Sep  4 22:52:24 inges2 kernel: [11889.915258] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
Sep  4 22:52:24 inges2 kernel: [11889.915263] pcieport 0000:00:01.2:    [12] Replay Timer Timeout
Sep  4 22:52:27 inges2 kernel: [11893.127616] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:52:27 inges2 kernel: [11893.127626] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Transmitter ID)
Sep  4 22:52:27 inges2 kernel: [11893.127632] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
Sep  4 22:52:27 inges2 kernel: [11893.127636] pcieport 0000:00:01.2:    [12] Replay Timer Timeout
Sep  4 22:52:33 inges2 kernel: [11899.060595] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:52:33 inges2 kernel: [11899.060605] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Transmitter ID)
Sep  4 22:52:33 inges2 kernel: [11899.060612] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
Sep  4 22:52:33 inges2 kernel: [11899.060617] pcieport 0000:00:01.2:    [12] Replay Timer Timeout
Sep  4 22:52:35 inges2 kernel: [11900.898788] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:52:35 inges2 kernel: [11900.898798] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Transmitter ID)
Sep  4 22:52:35 inges2 kernel: [11900.898805] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
Sep  4 22:52:35 inges2 kernel: [11900.898809] pcieport 0000:00:01.2:    [12] Replay Timer Timeout
Sep  4 22:52:36 inges2 kernel: [11901.824599] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:52:36 inges2 kernel: [11901.824608] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Transmitter ID)
Sep  4 22:52:36 inges2 kernel: [11901.824616] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
Sep  4 22:52:36 inges2 kernel: [11901.824620] pcieport 0000:00:01.2:    [12] Replay Timer Timeout
Sep  4 22:52:37 inges2 kernel: [11903.241021] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:52:37 inges2 kernel: [11903.241032] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Receiver ID)
Sep  4 22:52:37 inges2 kernel: [11903.241039] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00000080/00006000
Sep  4 22:52:37 inges2 kernel: [11903.241043] pcieport 0000:00:01.2:    [ 7] Bad DLLP
Sep  4 22:52:38 inges2 kernel: [11904.131122] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:52:38 inges2 kernel: [11904.131132] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Transmitter ID)
Sep  4 22:52:38 inges2 kernel: [11904.131139] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
Sep  4 22:52:38 inges2 kernel: [11904.131144] pcieport 0000:00:01.2:    [12] Replay Timer Timeout
Sep  4 22:52:43 inges2 kernel: [11909.141886] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:52:43 inges2 kernel: [11909.141895] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Transmitter ID)
Sep  4 22:52:43 inges2 kernel: [11909.141902] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
Sep  4 22:52:43 inges2 kernel: [11909.141907] pcieport 0000:00:01.2:    [12] Replay Timer Timeout
Sep  4 22:52:50 inges2 kernel: [11916.470504] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:52:50 inges2 kernel: [11916.470515] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Transmitter ID)
Sep  4 22:52:50 inges2 kernel: [11916.470521] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
Sep  4 22:52:50 inges2 kernel: [11916.470526] pcieport 0000:00:01.2:    [12] Replay Timer Timeout

All seems to be on device [1022:15d3

After rebooting this device initially seems to be ok.

Code:

Sep  4 22:56:51 inges2 kernel: [    0.080847] pci_bus 0000:00: root bus resource [mem 0xfee00000-0xffffffff window]
Sep  4 22:56:51 inges2 kernel: [    0.080848] pci_bus 0000:00: root bus resource [bus 00-ff]
Sep  4 22:56:51 inges2 kernel: [    0.080857] pci 0000:00:00.0: [1022:15d0] type 00 class 0x060000
Sep  4 22:56:51 inges2 kernel: [    0.080984] pci 0000:00:00.2: [1022:15d1] type 00 class 0x080600
Sep  4 22:56:51 inges2 kernel: [    0.081133] pci 0000:00:01.0: [1022:1452] type 00 class 0x060000
Sep  4 22:56:51 inges2 kernel: [    0.081242] pci 0000:00:01.2: [1022:15d3] type 01 class 0x060400
Sep  4 22:56:51 inges2 kernel: [    0.081346] pci 0000:00:01.2: PME# supported from D0 D3hot D3cold
Sep  4 22:56:51 inges2 kernel: [    0.081462] pci 0000:00:08.0: [1022:1452] type 00 class 0x060000
Sep  4 22:56:51 inges2 kernel: [    0.081572] pci 0000:00:08.1: [1022:15db] type 01 class 0x060400
Sep  4 22:56:51 inges2 kernel: [    0.081624] pci 0000:00:08.1: enabling Extended Tags
Sep  4 22:56:51 inges2 kernel: [    0.081680] pci 0000:00:08.1: PME# supported from D0 D3hot D3cold
Sep  4 22:56:51 inges2 kernel: [    0.081768] pci 0000:00:08.2: [1022:15dc] type 01 class 0x060400
Sep  4 22:56:51 inges2 kernel: [    0.081819] pci 0000:00:08.2: enabling Extended Tags
Sep  4 22:56:51 inges2 kernel: [    0.081870] pci 0000:00:08.2: PME# supported from D0 D3hot D3cold
Sep  4 22:56:51 inges2 kernel: [    0.081987] pci 0000:00:14.0: [1022:790b] type 00 class 0x0c0500
Sep  4 22:56:51 inges2 kernel: [    0.082164] pci 0000:00:14.3: [1022:790e] type 00 class 0x060100

Until later

Code:

Sep  4 22:56:51 inges2 kernel: [    0.808498] ehci-platform: EHCI generic platform driver
Sep  4 22:56:51 inges2 kernel: [    0.808502] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep  4 22:56:51 inges2 kernel: [    0.808503] ohci-pci: OHCI PCI platform driver
Sep  4 22:56:51 inges2 kernel: [    0.808508] ohci-platform: OHCI generic platform driver
Sep  4 22:56:51 inges2 kernel: [    0.808511] uhci_hcd: USB Universal Host Controller Interface driver
Sep  4 22:56:51 inges2 kernel: [    0.808609] xhci_hcd 0000:15:00.0: xHCI Host Controller
Sep  4 22:56:51 inges2 kernel: [    0.808613] xhci_hcd 0000:15:00.0: new USB bus registered, assigned bus number 1
Sep  4 22:56:51 inges2 kernel: [    0.812499] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:56:51 inges2 kernel: [    0.812506] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Transmitter ID)
Sep  4 22:56:51 inges2 kernel: [    0.812551] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
Sep  4 22:56:51 inges2 kernel: [    0.812588] pcieport 0000:00:01.2:    [12] Replay Timer Timeout
Sep  4 22:56:51 inges2 kernel: [    0.812615] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:56:51 inges2 kernel: [    0.812627] pcieport 0000:15:00.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=1502(Transmitter ID)
Sep  4 22:56:51 inges2 kernel: [    0.812666] pcieport 0000:15:00.2:   device [1022:43c6] error status/mask=00003000/00002000
Sep  4 22:56:51 inges2 kernel: [    0.812698] pcieport 0000:15:00.2:    [12] Replay Timer Timeout
Sep  4 22:56:51 inges2 kernel: [    0.838643] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:56:51 inges2 kernel: [    0.838650] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Transmitter ID)
Sep  4 22:56:51 inges2 kernel: [    0.838698] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
Sep  4 22:56:51 inges2 kernel: [    0.838736] pcieport 0000:00:01.2:    [12] Replay Timer Timeout
Sep  4 22:56:51 inges2 kernel: [    0.848299] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:56:51 inges2 kernel: [    0.848307] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Transmitter ID)
Sep  4 22:56:51 inges2 kernel: [    0.848376] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00001000/00006000
Sep  4 22:56:51 inges2 kernel: [    0.848429] pcieport 0000:00:01.2:    [12] Replay Timer Timeout
Sep  4 22:56:51 inges2 kernel: [    0.861603] xhci_hcd 0000:15:00.0: hcc params 0x0200ef81 hci version 0x110 quirks 0x00000410
Sep  4 22:56:51 inges2 kernel: [    0.861793] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep  4 22:56:51 inges2 kernel: [    0.861795] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep  4 22:56:51 inges2 kernel: [    0.861796] usb usb1: Product: xHCI Host Controller

Code:

Sep  4 22:56:51 inges2 kernel: [    3.397757] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:56:51 inges2 kernel: [    3.399429] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Receiver ID)
Sep  4 22:56:51 inges2 kernel: [    3.400552] random: fast init done
Sep  4 22:56:51 inges2 kernel: [    3.402018] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00000040/00006000
Sep  4 22:56:51 inges2 kernel: [    3.403300] pcieport 0000:00:01.2:    [ 6] Bad TLP
Sep  4 22:56:51 inges2 kernel: [    3.403971] random: systemd-udevd: uninitialized urandom read (16 bytes read)
Sep  4 22:56:51 inges2 kernel: [    3.403980] random: systemd-udevd: uninitialized urandom read (16 bytes read)
Sep  4 22:56:51 inges2 kernel: [    3.403991] random: systemd-udevd: uninitialized urandom read (16 bytes read)
Sep  4 22:56:51 inges2 kernel: [    3.423125] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:56:51 inges2 kernel: [    3.424700] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Receiver ID)
Sep  4 22:56:51 inges2 kernel: [    3.425928] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00000040/00006000
Sep  4 22:56:51 inges2 kernel: [    3.427164] pcieport 0000:00:01.2:    [ 6] Bad TLP
Sep  4 22:56:51 inges2 kernel: [    3.428399] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:56:51 inges2 kernel: [    3.429631] pcieport 0000:15:00.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=1502(Transmitter ID)
Sep  4 22:56:51 inges2 kernel: [    3.430691] pcieport 0000:15:00.2:   device [1022:43c6] error status/mask=00001000/00002000
Sep  4 22:56:51 inges2 kernel: [    3.431678] pcieport 0000:15:00.2:    [12] Replay Timer Timeout
Sep  4 22:56:51 inges2 kernel: [    3.436127] pcieport 0000:00:01.2: AER: Corrected error received: id=0008
Sep  4 22:56:51 inges2 kernel: [    3.437103] pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000a(Receiver ID)
Sep  4 22:56:51 inges2 kernel: [    3.438094] pcieport 0000:00:01.2:   device [1022:15d3] error status/mask=00000040/00006000
Sep  4 22:56:51 inges2 kernel: [    3.439081] pcieport 0000:00:01.2:    [ 6] Bad TLP

I literally get hundreds of these, but not sure as to the cause (or fix)
Thanks

Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Since you say the desktop is brand-new, the errors are probably benign. Try appending `pci=nomsi` to the kernel command line to silence the error messages.
Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

I will try this, but I don’t think this is benign as it hangs the machine
Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install
Have added the suggested switch, but that really hangs the box. Maybe it’s go something to do with the ecnrypted disk, but I don’t get the prompt for the password when the grub command line looks like this (see attached fails.txt)
Code:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi"
Without this it boots ok (see normal boot .txt)
Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Attached is the output of
Still logs a large amount of warnings and hangs the machine occasionally
Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Those error will happen when mounting a second disk the wrong way … do you have multiple drives ?
If so, the solution involves editing your `/etc/fstab`

backup current file `sudo cp /etc/fstab /etc/fstab~prior.art`

show all partitions by issuing `sudo blkid`

partial output will look similar to

/dev/sdb7: LABEL=»1810v01″ UUID=»61450f7b-44bf-429f-951e-6c8c17de5f43″ TYPE=»ext4″ PARTUUID=»2f0454ca-ed4a-4744-9c65-00b5a07a3741″

above is a partition on my second disk I want to auto mount on boot

IMPORTANT — take notice of value of UUID and TYPE

now I need to decide what full path I want that to get mounted to on my main drive … let say I want `/media/aha/1810v01` so just create this now as it must exist prior to doing the mount

`sudo mkdir -p /media/aha`

`sudo chown aha:ahs /media/aha`

now as myself ( aha ) issue

`mkdir /media/aha/1810v01`

now add a new line at bottom of `/etc/fstab` to define the mount as per

`sudo vi /etc/fstab`

now add following line

`UUID=61450f7b-44bf-429f-951e-6c8c17de5f43 /media/aha/1810v01 ext4 defaults 0 0`

now just reboot and those errors will go away
Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Bug was gone (fixed, I think) in my PC today after installing new Kernel version «linux-image-4.15.0-50-generic» in Ubuntu 18.04.2 x86_64.
Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Bookmarks

Posting Permissions

Источник

# 3 года, 11 месяцев назад (отредактировано 3 года, 11 месяцев назад)
Темы: 1 Сообщения: 18 Участник с: 28 февраля 2019	Здравствуйте, такая история: Плохо разбираюсь в Linux, однако решил установить Arch на новый ноутбук. Сразу после загрузки с usb в консоле с рандомной частотой выскакивает ошибка: `pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Transmitter ID) pcieport 0000:00:1d.0: device [8086:9d18] error status/mask=00001000/00000000 pcieport 0000:00:1d.0: [12] Timeout` Всё остальное вроде как работает без проблем. Но заниматься установкой системы нереально с этой проблемой. Вроде похожие проблемы на просторах интернета уже поднимались (https://unix.stackexchange.com/questions/330103/pcie-bus-error-when-booting-archiso-and-when-using-wifi-menu https://www.reddit.com/r/archlinux/comments/7wmio5/pcie_bus_error_during_installation/). Но во-первых там немного другое сообщение ошибки (там Physical Layer, у меня Data Link Layer), во-вторых решение насколько я понимаю лишь убирает вывод ошибки. Плюс я не понимаю, как добавить параметры загрузи ядра, если я загружаюсь в usb не через grub, а через uefi. И что вообще означает ошибка? Извиняюсь за фото экрана https://imgur.com/a/E191ugj, ничего другого не придумал. Upd: проблема решилась заменой драйвера r8169 на r8168

#
3 года, 11 месяцев назад

(отредактировано

3 года, 11 месяцев назад)

Темы:

Сообщения:

Участник с: 28 февраля 2019

Здравствуйте, такая история:
Плохо разбираюсь в Linux, однако решил установить Arch на новый ноутбук. Сразу после загрузки с usb в консоле с рандомной частотой выскакивает ошибка:

pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Transmitter ID)
pcieport 0000:00:1d.0:   device [8086:9d18] error status/mask=00001000/00000000
pcieport 0000:00:1d.0:     [12] Timeout

Всё остальное вроде как работает без проблем. Но заниматься установкой системы нереально с этой проблемой.

Вроде похожие проблемы на просторах интернета уже поднимались (https://unix.stackexchange.com/questions/330103/pcie-bus-error-when-booting-archiso-and-when-using-wifi-menu https://www.reddit.com/r/archlinux/comments/7wmio5/pcie_bus_error_during_installation/). Но во-первых там немного другое сообщение ошибки (там Physical Layer, у меня Data Link Layer), во-вторых решение насколько я понимаю лишь убирает вывод ошибки. Плюс я не понимаю, как добавить параметры загрузи ядра, если я загружаюсь в usb не через grub, а через uefi.

И что вообще означает ошибка?
Извиняюсь за фото экрана https://imgur.com/a/E191ugj, ничего другого не придумал.

Upd: проблема решилась заменой драйвера r8169 на r8168

heider	# 3 года, 11 месяцев назад
Темы: 0 Сообщения: 83 Участник с: 09 декабря 2015	Ошибка шины PCI. Думаю, что это повод отнести ноутбук назад в магазин.

heider

#
3 года, 11 месяцев назад

Темы:

Сообщения:

Участник с: 09 декабря 2015

Ошибка шины PCI. Думаю, что это повод отнести ноутбук назад в магазин.

vs220	# 3 года, 11 месяцев назад (отредактировано 3 года, 11 месяцев назад)
Темы: 22 Сообщения: 8090 Участник с: 16 августа 2009	heider Ошибка шины PCI Судя по id вроде isa. И вот вопрос зачем она на ноуте, и нет ли в биос ее отключения А нет не туда глянул Sunrise Point-LP PCI Express Root Port #9

vs220

#
3 года, 11 месяцев назад

(отредактировано

3 года, 11 месяцев назад)

Темы:

Сообщения:

8090

Участник с: 16 августа 2009

heider
Ошибка шины PCI

Судя по id вроде isa. И вот вопрос зачем она на ноуте, и нет ли в биос ее отключения
А нет не туда глянул
Sunrise Point-LP PCI Express Root Port #9

heider	# 3 года, 11 месяцев назад
Темы: 0 Сообщения: 83 Участник с: 09 декабря 2015	vs220 Судя по id вроде isa. И вот вопрос зачем она на ноуте, и нет ли в биос ее отключения У меня на нетбуке есть мост ISA, правда, с другим id. vs220 А нет не туда глянул Sunrise Point-LP PCI Express Root Port #9 Туда. Рут порт это 9d15, а у ТС проблема с 9d18

heider

#
3 года, 11 месяцев назад

Темы:

Сообщения:

Участник с: 09 декабря 2015

vs220
Судя по id вроде isa. И вот вопрос зачем она на ноуте, и нет ли в биос ее отключения

У меня на нетбуке есть мост ISA, правда, с другим id.

vs220
А нет не туда глянул
Sunrise Point-LP PCI Express Root Port #9

Туда. Рут порт это 9d15, а у ТС проблема с 9d18

vs220	# 3 года, 11 месяцев назад
Темы: 22 Сообщения: 8090 Участник с: 16 августа 2009	heider Рут порт это 9d15, а у ТС проблема с 9d18 Судя по картике и по id это тоже рут порт. А вот что на нем висит не понятно

vs220

#
3 года, 11 месяцев назад

Темы:

Сообщения:

8090

Участник с: 16 августа 2009

heider
Рут порт это 9d15, а у ТС проблема с 9d18

Судя по картике и по id это тоже рут порт. А вот что на нем висит не понятно

heider	# 3 года, 11 месяцев назад
Темы: 0 Сообщения: 83 Участник с: 09 декабря 2015	vs220 heider Рут порт это 9d15, а у ТС проблема с 9d18 Судя по картике и по id это тоже рут порт. А вот что на нем висит не понятно Ага, уже рассмотрел. Там глаза сломать можно.

heider

#
3 года, 11 месяцев назад

Темы:

Сообщения:

Участник с: 09 декабря 2015

vs220

heider
Рут порт это 9d15, а у ТС проблема с 9d18

Судя по картике и по id это тоже рут порт. А вот что на нем висит не понятно

Ага, уже рассмотрел. Там глаза сломать можно.

l1onsun	# 3 года, 11 месяцев назад
Темы: 1 Сообщения: 18 Участник с: 28 февраля 2019	Так что думаете стоит в ремонт отнести? Винда у меня без проблем работает кстати

l1onsun

#
3 года, 11 месяцев назад

Темы:

Сообщения:

Участник с: 28 февраля 2019

Так что думаете стоит в ремонт отнести? Винда у меня без проблем работает кстати

heider	# 3 года, 11 месяцев назад (отредактировано 3 года, 11 месяцев назад)
Темы: 0 Сообщения: 83 Участник с: 09 декабря 2015	Если винда работает, то можно глянуть в диспетчере устройств, что там на порту Express Root.

heider

#
3 года, 11 месяцев назад

(отредактировано

3 года, 11 месяцев назад)

Темы:

Сообщения:

Участник с: 09 декабря 2015

Если винда работает, то можно глянуть в диспетчере устройств, что там на порту Express Root.

vasek	# 3 года, 11 месяцев назад (отредактировано 3 года, 11 месяцев назад)
Темы: 47 Сообщения: 11417 Участник с: 17 февраля 2013	Сначала посмотри что там сидит на 1d — lspci -tv , lspci -vbs 00:1d Заодно в выводе lspci -vbs 00:1d посмотри, что там с драйверами l1onsun во-вторых решение насколько я понимаю лишь убирает вывод ошибки. Вывод сообщений убирает параметр pci=noaer, пробуй загрузиться с параметром pci=nomsi или pci=nommconf Ошибки не исчезают с опытом — они просто умнеют

vasek

#
3 года, 11 месяцев назад

(отредактировано

3 года, 11 месяцев назад)

Темы:

Сообщения:

11417

Участник с: 17 февраля 2013

Сначала посмотри что там сидит на 1d — lspci -tv , lspci -vbs 00:1d
Заодно в выводе lspci -vbs 00:1d посмотри, что там с драйверами

l1onsun
во-вторых решение насколько я понимаю лишь убирает вывод ошибки.

Вывод сообщений убирает параметр pci=noaer, пробуй загрузиться с параметром pci=nomsi или pci=nommconf

Ошибки не исчезают с опытом — они просто умнеют

vs220	# 3 года, 11 месяцев назад
Темы: 22 Сообщения: 8090 Участник с: 16 августа 2009	l1onsun Так что думаете стоит в ремонт отнести? Винда у меня без проблем работает кстати Может просто драйверов нет подходяших на исошке для того что на порту висит.

vs220

#
3 года, 11 месяцев назад

Темы:

Сообщения:

8090

Участник с: 16 августа 2009

l1onsun
Так что думаете стоит в ремонт отнести? Винда у меня без проблем работает кстати

Может просто драйверов нет подходяших на исошке для того что на порту висит.

Источник

Как правильно задавать вопросы

Правильно сформулированный вопрос и его грамотное оформление способствует высокой вероятности получения достаточно содержательного и по существу ответа. Общая рекомендация по составлению тем: 1. Для начала воспользуйтесь поиском форума. 2. Укажите версию ОС вместе с разрядностью. Пример: LM 19.3 x64, LM Sarah x32 3. DE. Если вопрос касается двух, то через запятую. (xfce, KDE, cinnamon, mate) 4. Какое железо. (достаточно вывод inxi -Fxz в спойлере (как пользоваться спойлером смотрим здесь)) или же дать ссылку на hw-probe 5. Суть. Желательно с выводом консоли, логами. 6. Скрин. Просьба указывать 2, 3 и 4 независимо от того, имеет ли это отношение к вопросу или нет. Так же не забываем об общих правилах Как пример вот

Dja: Сообщения: 6633; Зарегистрирован: 27 авг 2016, 20:03; Решено: 28; Откуда: Voskresensk; Благодарил (а): 1188 раз; Поблагодарили: 698 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

21 авг 2018, 02:45

Взял ноут

System:    Host: dja-work Kernel: 4.13.0-43-generic x86_64 (64 bit gcc: 5.4.0) Desktop: Xfce 4.12.3 (Gtk 2.24.28)
           Distro: Linux Mint 18.3 Sylvia
Machine:   System: ASUSTeK (portable) product: X541UVK v: 1.0
           Mobo: ASUSTeK model: X541UVK v: 1.0 Bios: American Megatrends v: X541UVK.308 date: 01/30/2018
CPU:       Dual core Intel Core i3-6006U (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 7968
           clock speeds: max: 2000 MHz 1: 1669 MHz 2: 1569 MHz 3: 1663 MHz 4: 1503 MHz
Graphics:  Card-1: Intel Sky Lake Integrated Graphics bus-ID: 00:02.0
           Card-2: NVIDIA Device 134f bus-ID: 01:00.0
           Display Server: X.Org 1.18.4 driver: nvidia Resolution: 1920x1080@60.05hz
           GLX Renderer: GeForce 920MX/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 384.130 Direct Rendering: Yes
Audio:     Card Intel Sunrise Point-LP HD Audio driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.13.0-43-generic
Network:   Card-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
           driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 02:00.2
           IF: enp2s0f2 state: down mac: <filter>
           Card-2: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be port: c000 bus-ID: 03:00.0
           IF: wlp3s0 state: up mac: <filter>
Drives:    HDD Total Size: 1000.2GB (42.5% used) ID-1: /dev/sda model: ST1000LM035 size: 1000.2GB
Partition: ID-1: / size: 50G used: 24G (50%) fs: ext4 dev: /dev/sda2
           ID-2: /home size: 30G used: 3.7G (13%) fs: ext4 dev: /dev/sda3
           ID-3: swap-1 size: 9.66GB used: 0.00GB (0%) fs: swap dev: /dev/sda4
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 45.0C mobo: N/A gpu: 0.0:43C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 247 Uptime: 22 min Memory: 1985.1/7858.9MB Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35

Всё бы ничего. Но при загрузке и выключении много таких строк

Помогло в /etc/default/grub

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX_DEFAULT="pci=nomsi"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

После изменений не забываем про

Есть еще вариант
GRUB_CMDLINE_LINUX_DEFAULT=»quiet splash pci=noaer»
но не пробовал, поскольку помог первый. С ждуном еще не баловался. Если что отпишусь позже.

Нагуглить помог di_mok

Решение Unborn » 22 авг 2018, 22:15

Dja писал(а): ↑

22 авг 2018, 22:00

И это только маленький кусочек

Понятно, что маленький. Ошибки давай. Что у тебя там на 1с.5? Вывод — lspci -tv

Перейти к ответу ➙

Unborn: Сообщения: 1920; Зарегистрирован: 03 сен 2016, 13:36; Решено: 24; Благодарил (а): 5 раз; Поблагодарили: 264 раза; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

21 авг 2018, 19:21

Dja, pci=nomsi, pci=noaer зачем тогда новое железо покупал? У тебя инфа о скорректированных ошибках. Мог бы вообще её не увидеть. Обычно отключают вывод таких сообщений для уже готового, собранного ядра. В каких-нибудь альфа, бета версиях дистров такое увидишь.
А ты взял и на хер отключил возможность использования многоядерности, многопоточности для работы с прерываниями.
В принципе можно вообще на одно ядро ЦП обработку прерываний повесить. Так когда-то на серверах делали, когда ЦП одноядерные были.
Хотя бы загуглил —

Message Signaled Interrupts

А то залез назад на пальму, всё, решил вопрос с жильем. И про ядро 4.13 уже забыли. Попробуй крайнюю версию 4.4
По железу бы 4.9 LTS или 4.14 LTS использовать. ОС в УЕФИ. Кстати у АСУС УЕФИ от АМИ и самые путные. Это не Н20+свои велосипеды у остальных вендоров.

Dja: Сообщения: 6633; Зарегистрирован: 27 авг 2016, 20:03; Решено: 28; Откуда: Voskresensk; Благодарил (а): 1188 раз; Поблагодарили: 698 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

21 авг 2018, 20:16

Unborn, система то в уефи. А про обнову ядра как-то и не подумал. Да и железо то не вот тебе новое. Попробую конечно ядра поудалять и поставить поновее.
Кстати именно 4.9 и 4.14 отсутствуют

rogoznik: Сообщения: 9443; Зарегистрирован: 27 июн 2017, 13:36; Решено: 119; Откуда: Нижний Тагил; Благодарил (а): 716 раз; Поблагодарили: 1816 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

21 авг 2018, 20:27

Dja, убунтовцы прошли их стороной…поставь ukuu и из нее накати ядрышки

Dja: Сообщения: 6633; Зарегистрирован: 27 авг 2016, 20:03; Решено: 28; Откуда: Voskresensk; Благодарил (а): 1188 раз; Поблагодарили: 698 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

21 авг 2018, 20:47

довольно странно иметь на борту утилиту, которую и запускаю только для ядра, но при этом качать стороннюю

Dja: Сообщения: 6633; Зарегистрирован: 27 авг 2016, 20:03; Решено: 28; Откуда: Voskresensk; Благодарил (а): 1188 раз; Поблагодарили: 698 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

21 авг 2018, 21:37

В итоге 4.4 как и 4.15 — можно вечно смотреть на бегущие строки. 4.14 — хотя бы грузится как 4.13 после выплеска нескольких десятков строк.
Счас гляну 4.9
Их и так уже солить можно

-rw-------  1 root root  7407392 окт 10  2017 vmlinuz-4.10.0-38-generic
-rw-------  1 root root  7407392 ноя  9  2017 vmlinuz-4.10.0-40-generic
-rw-------  1 root root  7406720 дек  4  2017 vmlinuz-4.10.0-42-generic
-rw-------  1 root root  7669648 янв 10  2018 vmlinuz-4.13.0-26-generic
-rw-------  1 root root  7671376 янв 25  2018 vmlinuz-4.13.0-32-generic
-rw-------  1 root root  7711632 мар  7 21:23 vmlinuz-4.13.0-37-generic
-rw-------  1 root root  7712208 мар 14 22:49 vmlinuz-4.13.0-38-generic
-rw-------  1 root root  7711664 май  3 16:07 vmlinuz-4.13.0-41-generic
-rw-------  1 root root  7713296 май 17 18:33 vmlinuz-4.13.0-43-generic
-rw-------  1 root root  7923472 ноя 12  2017 vmlinuz-4.14.0-041400-generic
-rw-------  1 root root  8101272 авг  6 20:23 vmlinuz-4.15.0-30-generic
-rw-------  1 root root  7159744 авг 10 14:20 vmlinuz-4.4.0-133-generic
-rw-r--r--  1 root root  7065648 янв 25  2017 vmlinuz-4.4.0-53-generic
-rw-------  1 root root  7310848 июн 27  2017 vmlinuz-4.8.0-58-generic

4.14 4.9 ошибочки

dpkg: зависимости пакетов не позволяют настроить пакет linux-headers-4.9.122-0409122-generic:
 linux-headers-4.9.122-0409122-generic зависит от libssl1.1 (>= 1.1.0), однако:
  Пакет libssl1.1 не установлен.

Пошел искать пакет
UPD нашел пакет. Качнул. Поставил. Ядро 4.9 встало, но на загрузку влияет негативно. Можно вечно ждать окончания загрузки с бегущими тысячами строк. 4.14.65 тоже встало, хоть и агрилось с ошибками. Тоже грузит вечно.
Самое противное что эти строки мешают юзать ждуна

AlexZ: Сообщения: 1395; Зарегистрирован: 06 янв 2018, 21:06; Решено: 3; Откуда: Горно-Алтайск; Благодарил (а): 212 раз; Поблагодарили: 177 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

21 авг 2018, 23:19

Dja писал(а): ↑

21 авг 2018, 20:47

Кстати именно 4.9 и 4.14 отсутствуют
довольно странно иметь на борту утилиту, которую и запускаю только для ядра, но при этом качать стороннюю

Политка убунты такая. Мне вот тоже до сих пор странно, на ядре 4.15 почему-то только убунтовые дистры
А для того чтоб ядрами поиграть ukuu удобный вариант (для новой железяки последние ядра попробуй)

StarMAUGLI: Сообщения: 1609; Зарегистрирован: 10 сен 2016, 10:16; Решено: 18; Откуда: Москва; Благодарил (а): 686 раз; Поблагодарили: 187 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

22 авг 2018, 00:15

Dja, А что показывает lspci
что это вообще за зверь такой 0000:00:1c.5 ?

rogoznik: Сообщения: 9443; Зарегистрирован: 27 июн 2017, 13:36; Решено: 119; Откуда: Нижний Тагил; Благодарил (а): 716 раз; Поблагодарили: 1816 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

#10

22 авг 2018, 09:18

Dja, попробуй свеженькие ядра 4.17, 4.18

IaroslavB: Сообщения: 121; Зарегистрирован: 15 апр 2018, 15:57; Решено: 1; Откуда: Прага; Благодарил (а): 199 раз; Поблагодарили: 6 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

#11

22 авг 2018, 10:24

StarMAUGLI, lspci = команда List(Ls) + то, что будем выводить : некий вывод(зависит от дефолтных атрибутов команды) с Pci(Peripheral Components Interconnect) шины — подсистема, соединяющая множество периферийных устройств(мышь,клавиатура и т.д.) для передачи по единому каналу информацию дальше, если я правильно понимаю, как правило, до материнской платы.
А цифры те — это порт шины pci, да поправят меня знающие, если это не так.

Acer Aspire E5-575G-55J7
□ LM 18.3 KDE Plasma 5.8.9 based on Kernel[ 4.15.0-15 ]×86_64.
■ Intel Core i5=7200u
■ NVIDIA GeForce GTX 950M
Audio card: ●Intel device 9d71
Network cards:● Qualcomm Atheros dev. 0042 + ●Realtek RTL8111/8168/8411

Dja: Сообщения: 6633; Зарегистрирован: 27 авг 2016, 20:03; Решено: 28; Откуда: Voskresensk; Благодарил (а): 1188 раз; Поблагодарили: 698 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

#12

22 авг 2018, 12:31

darkfenix, да всякие пробовал. Эти «свежие ядра» вообще одни простыни выдают без возможности попасть в графику либо ждать минут по 10. Сейчас вообще графика из inxi пропала чую меня эти ядра не полечат, а покалечат. Надо наверно вернуться к решению и попробовать ждуна ) Если работать будет — пофиг на эти выхлопы. Меньше видишь крепче спишь

Dja: Сообщения: 6633; Зарегистрирован: 27 авг 2016, 20:03; Решено: 28; Откуда: Voskresensk; Благодарил (а): 1188 раз; Поблагодарили: 698 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

#13

22 авг 2018, 12:42

Еще и хромиум перестал запускаться

dja-laptop ~ $ chromium-browser
Using PPAPI flash.
--disable-new-tab-first-run --enable-user-scripts --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version=
[7706:7706:0822/124012.722612:ERROR:process_singleton_posix.cc(1035)] Failed to create socket directory.
[7706:7706:0822/124012.722769:ERROR:chrome_browser_main.cc(1713)] Failed to create a ProcessSingleton for your profile directory. This means that running multiple instances would start multiple browser processes rather than opening a new window in the existing process. Aborting now to avoid profile corruption.
dja-laptop ~ $

Весело

rogoznik: Сообщения: 9443; Зарегистрирован: 27 июн 2017, 13:36; Решено: 119; Откуда: Нижний Тагил; Благодарил (а): 716 раз; Поблагодарили: 1816 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

#14

22 авг 2018, 12:50

Dja, Что-то с профилем случилось, вот он и не запускается

StarMAUGLI: Сообщения: 1609; Зарегистрирован: 10 сен 2016, 10:16; Решено: 18; Откуда: Москва; Благодарил (а): 686 раз; Поблагодарили: 187 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

#15

22 авг 2018, 13:27

IaroslavB писал(а): ↑

22 авг 2018, 10:24

А цифры те — это порт шины pci, да поправят меня знающие, если это не так.

на моем компе это выглядит так

Код: Выделить всё

┌─ mugalem ~ 
└─ $ lspci
00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port (rev 02)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 02)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation 82801IR (ICH9R) LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA Controller [IDE mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA Controller [IDE mode] (rev 02)
01:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 650 Ti] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GK106 HDMI Audio Controller (rev a1)
03:00.0 SATA controller: JMicron Technology Corp. JMB361 AHCI/IDE (rev 02)
03:00.1 IDE interface: JMicron Technology Corp. JMB361 AHCI/IDE (rev 02)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0
05:01.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx]
┌─ mugalem ~ 
└─ $

т.е. на этом номере у меня 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 02)
но у него-то на ноуте наверняка другой набор логики (чем на моем допотопном старье) не ICH9, значит там может быть и не PCI Express — поэтому и спросил — нужно же знать про что гуглить. Любопытно же.
Тем более, что это не тот PCI Express, что идет на видео-карту, а тот, что идет на всякую мелочь, типа звука или сетевух.

Dja: Сообщения: 6633; Зарегистрирован: 27 авг 2016, 20:03; Решено: 28; Откуда: Voskresensk; Благодарил (а): 1188 раз; Поблагодарили: 698 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

#16

22 авг 2018, 13:56

всё это может быть результатом клонирования системы Попробую поставить именно на него. Посмотрю что выйдет.

Unborn: Сообщения: 1920; Зарегистрирован: 03 сен 2016, 13:36; Решено: 24; Благодарил (а): 5 раз; Поблагодарили: 264 раза; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

#17

22 авг 2018, 15:09

Dja писал(а): ↑

22 авг 2018, 13:56

всё это может быть результатом клонирования системы

Так если ты с одной аппаратной конфигурации перенес на другую, то что ты ещё удивляешься? Это закономерное явление. Как говносборку-бэкап чей-нибудь на каком-нибудь десктопном железе сделанном воткнуть себе на ноут и удивляться, что это там не работает вай-фай, если у говносборщика и вафли то не было.
И если ядро будет уже с патчем против последних Мельдауна и Спектра, то и драйвер Нвидиа должен быть с 3-мя цифрами после точки. Если ядро не патченое, то лучше с 2-мя.

Dja: Сообщения: 6633; Зарегистрирован: 27 авг 2016, 20:03; Решено: 28; Откуда: Voskresensk; Благодарил (а): 1188 раз; Поблагодарили: 698 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

#18

22 авг 2018, 16:11

darkfenix писал(а): ↑

22 авг 2018, 12:50

Что-то с профилем случилось

Места на корне нет вот система и в шоке, собственно как и я с 30 гигов увеличил до 50 и тех не хватило… Куда 20 гигов ушло… по ходу на эти логи
Unborn, ну я же ставил линух на флешку и флешка прекрасно запускалась на других машинах.

Dja: Сообщения: 6633; Зарегистрирован: 27 авг 2016, 20:03; Решено: 28; Откуда: Voskresensk; Благодарил (а): 1188 раз; Поблагодарили: 698 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

#19

22 авг 2018, 17:13

Поставил с нуля LM 18.3
Всё равно эти строки ))) Стало быть клонирование не виновато.

StarMAUGLI писал(а): ↑

22 авг 2018, 00:15

показывает lspci

00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 07)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 3D controller: NVIDIA Corporation Device 134f (rev a2)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5286 PCI Express Card Reader (rev 01)
02:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 06)
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter

StarMAUGLI: Сообщения: 1609; Зарегистрирован: 10 сен 2016, 10:16; Решено: 18; Откуда: Москва; Благодарил (а): 686 раз; Поблагодарили: 187 раз; Контактная информация:

PCIe Bus error severity=Corrected много-много строк

#20

22 авг 2018, 18:11

Dja писал(а): ↑

22 авг 2018, 17:13

00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1)

Странно. На 00:1c.4 точно такой же стоит, а ошибок нет.
Ты уверен, что проблема программная, а не железная?
Может стоит разобрать ноут и посмотреть в порт на предмет загнутых лепестков, перекошенных шлейфов, подгоревших деталек или металлического/токопроводящего мусора? Контактики там флейцем промести, ластиком почистить? Или даже пылесосом пожужжать?

Источник

I have a new HP Pavilion Gaming Notebook and a new installation of Ubuntu 16.04. When I press Ctrl + Alt + F1 I go start seeing the errors shown in the following image and it doesn’t allow me to interact with the console:

I also see these errors for a while everytime I boot. I need to do Ctrl + Alt + F1 to access a non graphical terminal to install some Nvidia drivers. What’s going on?

What’s causing the problem seems to be:
00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #6 [8086:a115] (rev f1)

jpiabrantes@joao:~$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM Registers [8086:1910] (rev 07)
00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) [8086:1901] (rev 07)
00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06)
00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 07)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31)
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31)
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31)
00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA Controller [AHCI mode] [8086:a103] (rev 31)
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1)
00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #6 [8086:a115] (rev f1)
00:1c.6 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #7 [8086:a116] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a14e] (rev 31)
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31)
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31)
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31)
01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 950M] [10de:139a] (rev a2)
07:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01)
08:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723]
09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 0a)

asked May 13, 2016 at 16:15

João AbrantesJoão Abrantes

7631 gold badge6 silver badges10 bronze badges

Try this,

Use this link ( about the adding paramter to kernel here) to understand about adding kernel boot paramter temporarily and making it permanent.
Then,

Add the parameter , pci=nomsi

And reboot.

If the problem is solved then make the change permanent.
If does not work then try,

pci=noaer

same way and make it permanent if this works.

(*Reason for appearance is related to the recent Intel Skylake architecture CPUs and Realtek rtl8723be wireless adaptor.

The ubuntu team knows about it. Read more here Bug_track_ubuntu_PCIe bus error )

answered May 13, 2016 at 16:33

ankit7540ankit7540

4,1051 gold badge24 silver badges41 bronze badges

Here already answers are provided which also helped me a lot. I use text mode of ubuntu 16.04 and so

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi"

didn’t helped me. Here what I changed was — (in /etc/default/grub)

GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi"
GRUB_CMDLINE_LINUX="text pci=nomsi"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

which solved my error(NOTE — I used only pci=nomsi, and in case it don’t work other option is pci=noaer), that may help solve anyone facing the same error.

answered Jun 17, 2017 at 6:42

I always have the same issue when reinstall Ubuntu 18.04.4 with ASUS X555UQ Laptop.

Answers above helped me a lot about adding which parameter to /etc/default/grub/ but I can’t reach terminal (also tty), because after installing OS via live usb, it gives a blank screen(or mentioned issue) instead of login screen.

Then I thought that I have to get to the GRUB menu at boot-time so, according to this link how to get to the GRUB menu at boot-time, pressing esc while booting did not cause the GRUB menu to appear. It shows please select boot device section for me. Then I pressed Enter to boot again and while booting, pressed esc again. Finally it reached to the GRUB menu and I pressed e to edit the commands(this page starts with set params 'Ubuntu'). Then I added pci=nomsi to end of the line starting with linux and pressed F10 to boot.

After this operation, I was able to reach login screen and terminal. Then I followed the @Ujjal Kumar Das’s answer above and updated my /etc/default/grub/ file permanently.

Maybe this method works for the users who have the same laptop model like me. I like using Ubuntu, but this issue is so annoying every time.

answered Mar 29, 2020 at 21:50

Источник

Бодрого времени суток!

При загрузке вылетает ошибка:

pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0018(Transmitter ID) device [8086:d138] error status/mask=00001000/00002000
Ноутбук: asus G51J
Видяха Nvidia GTS360

В соответствии с тем, что удалось найти в сети — проблема именно в видеокарте, но в соответствии с описаниями, проблем на ядрах позже 2.6.33 быть не должно, в месте с тем текущая версия ядра 4.5.1-un-def-alt1.
Используемый модуль ядра — nouveau

Как можно побороть проблему?

« Последнее редактирование: 15.04.2016 12:46:37 от ApB »

Записан

8086 — это код Intel, а не NVidia. Надо посмотреть lspci -n, понять, какой bus id у устройства, потом посмотреть просто lspci. А, вообще, это всё в /usr/share/misc/pci.ids. Файл текстовый.

d138 Core Processor PCI Express Root Port 1 1028 02da OptiPlex 980 1028 040b Latitude E6510 15d9 060d C7SIM-Q Motherboard
Или именно в нём NVidia ?

« Последнее редактирование: 14.04.2016 16:25:07 от asy »

Записан

lspci -n 00:00.0 0600: 8086:d132 (rev 11) 00:03.0 0604: 8086:d138 (rev 11) 00:08.0 0880: 8086:d155 (rev 11) 00:08.1 0880: 8086:d156 (rev 11) 00:08.2 0880: 8086:d157 (rev 11) 00:08.3 0880: 8086:d158 (rev 11) 00:10.0 0880: 8086:d150 (rev 11) 00:10.1 0880: 8086:d151 (rev 11) 00:16.0 0780: 8086:3b64 (rev 06) 00:1a.0 0c03: 8086:3b3c (rev 06) 00:1b.0 0403: 8086:3b56 (rev 06) 00:1c.0 0604: 8086:3b42 (rev 06) 00:1c.1 0604: 8086:3b44 (rev 06) 00:1c.2 0604: 8086:3b46 (rev 06) 00:1c.4 0604: 8086:3b4a (rev 06) 00:1c.5 0604: 8086:3b4c (rev 06) 00:1d.0 0c03: 8086:3b34 (rev 06) 00:1e.0 0604: 8086:2448 (rev a6) 00:1f.0 0601: 8086:3b09 (rev 06) 00:1f.2 0106: 8086:3b29 (rev 06) 00:1f.3 0c05: 8086:3b30 (rev 06) 01:00.0 0300: 10de:0cb1 (rev a2) 01:00.1 0403: 10de:0be4 (rev a1) 03:00.0 0280: 8086:0887 (rev c4) 06:00.0 0805: 1180:e822 (rev 01) 06:00.1 0880: 1180:e230 (rev 01) 06:00.3 0c00: 1180:e832 (rev 01) 07:00.0 0200: 1969:1063 (rev c0) 3f:00.0 0600: 8086:2c52 (rev 04) 3f:00.1 0600: 8086:2c81 (rev 04) 3f:02.0 0600: 8086:2c90 (rev 04) 3f:02.1 0600: 8086:2c91 (rev 04) 3f:03.0 0600: 8086:2c98 (rev 04) 3f:03.1 0600: 8086:2c99 (rev 04) 3f:03.4 0600: 8086:2c9c (rev 04) 3f:04.0 0600: 8086:2ca0 (rev 04) 3f:04.1 0600: 8086:2ca1 (rev 04) 3f:04.2 0600: 8086:2ca2 (rev 04) 3f:04.3 0600: 8086:2ca3 (rev 04) 3f:05.0 0600: 8086:2ca8 (rev 04) 3f:05.1 0600: 8086:2ca9 (rev 04) 3f:05.2 0600: 8086:2caa (rev 04) 3f:05.3 0600: 8086:2cab (rev 04)

Записан

01:00.0 0300: 10de:0cb1 (rev a2)
01:00.1 0403: 10de:0be4 (rev a1)

Вот ваша видеокарта

Записан

GT215 — используемый чипсет
GeForce GTS 360M — торговая марка

Записан

Судя по сайту nvidia, нужна версия nvidia:
Display Driver NVIDIA Recommended 304.131

Записан

00:03.0 0604: 8086:d138 (rev 11)

Теперь

lspci|grep "00:03.0"Но, раз это шина PCI, то видеокарта тоже, наверное, может иметь отношение к проблеме. Но может и не иметь.

« Последнее редактирование: 14.04.2016 17:32:44 от asy »

Записан

Но, раз это шина PCI, то видеокарта тоже, наверное, может иметь отношение к проблеме. Но может и не иметь.

Ну, например, если в эту шину вставлена видеокарта ….

Записан

Кстати, это можно увидеть через lspci -tv

Записан

01:00.0 0300: 10de:0cb1 (rev a2)

Да нет, тогда-бы у видеокарты в id шины мы-бы увидели 00:03

Записан

Не нашёл, где в исходниках nouveau можно найти список поддерживаемых устройств. Возможно оно у нас, и как в Ubuntu не поддерживается.

Записан

Источник

Bug 1616364
— PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

Summary:

PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

Created attachment 1476224 [details]
dmesg

Description of problem:

I assembled a new computer.
But my joy is marred by a lot of errors in the kernel log:
[  104.373852] pcieport 0000:00:03.1: AER: Corrected error received:
0000:00:00.0
[  104.373877] pcieport 0000:00:03.1: PCIe Bus Error:
severity=Corrected, type=Data Link Layer, (Transmitter ID)
[  104.373881] pcieport 0000:00:03.1:   device [1022:1453] error
status/mask=00001000/00006000
[  104.373886] pcieport 0000:00:03.1:    [12] Replay Timer Timeout
I don't know it may be false positive or can impact performance.
Anyway I hope it can be fixed because such count of errors make it
difficult to observe real problems.


$ uname -r
4.18.0-0.rc8.git2.1.fc29.x86_64

Comment 1

Mikhail

2018-08-15 19:11:01 UTC

$ lspci -nn
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex [1022:1450]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit [1022:1451]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453]
00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453]
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453]
00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454]
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge [1022:1452]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 59)
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1460]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1461]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1462]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1463]
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1464]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1465]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1466]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 [1022:1467]
01:00.0 Non-Volatile memory controller [0108]: Intel Corporation Optane SSD 900P Series [8086:2700]
02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43d0] (rev 01)
02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] Device [1022:43c8] (rev 01)
02:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43c6] (rev 01)
03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43c7] (rev 01)
03:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43c7] (rev 01)
03:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43c7] (rev 01)
03:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43c7] (rev 01)
03:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43c7] (rev 01)
04:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822]
09:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:1470] (rev c3)
0a:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:1471]
0b:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] [1002:687f] (rev c3)
0b:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:aaf8]
0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device [1022:145a]
0c:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:1456]
0c:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] USB 3.0 Host controller [1022:145f]
0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device [1022:1455]
0d:00.2 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)
0d:00.3 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller [1022:1457]

Comment 2

Jakub Jankiewicz

2018-11-08 12:26:15 UTC

I have the same issue:

[81827.838100] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
[81827.838111] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[81827.838122] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00001000/00000000
[81827.838129] pcieport 0000:00:1c.5:    [12] Replay Timer Timeout

in dmesg

$ uname -a
Linux jcubic 4.18.16-100.fc27.x86_64 #1 SMP Sun Oct 21 09:33:00 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I'm not sure if this was that error that came up in Kernel after update, There was thread in Kernel bug tracker that indicated the issue was always present but was not visible in logs.

Comment 3

Jakub Jankiewicz

2018-11-08 12:30:13 UTC

$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08)
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07)
00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21)
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
00:17.0 RAID bus controller [0104]: Intel Corporation 82801 Mobile SATA Controller [RAID mode] [8086:282a] (rev 21)
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1)
00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1)
00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 [8086:9d15] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller - 9D4E [8086:9d4e] (rev 21)
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21)
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21)
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21)
01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [1002:6900] (rev c1)
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller [10ec:8136] (rev 07)
03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31)

The machine was Laptop Dell Inspiron 15 5570.

Comment 6

Forrest Ewen

2019-03-29 14:03:43 UTC

Was there ever a resolution to the error.  The two posted links don't see to indicate what the issue was or if it had been fixed.  

I'm getting :
Mar 29 09:42:44 recovery kernel: pcieport 0000:80:03.0: AER: Multiple Corrected error received: id=8018
Mar 29 09:42:44 recovery kernel: pcieport 0000:80:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=8018(Receiver ID)
Mar 29 09:42:44 recovery kernel: pcieport 0000:80:03.0:   device [8086:6f08] error status/mask=00000040/00002000
Mar 29 09:42:44 recovery kernel: pcieport 0000:80:03.0:    [ 6] Bad TLP               

on RHEL kernel version 
3.10.0-862.14.4.el7.x86_64

Do I need to update the kernel to make it go away, has there been a fix for it?  The second link posted showed it as work around but not a fix.

Comment 7

Marcin Zajaczkowski

2019-06-30 16:35:27 UTC

I have the same error with 5.1.5-300.fc30.x86_64 and 5.2.0-0.rc4.git0.1.fc30.x86_64 (a rawhide SRPM rebuilt on Fedora 30).

> Jun 30 15:14:54 foobar kernel: pcieport 0000:00:1d.6: AER: Multiple Corrected error received: 0000:00:1d.6
> Jun 30 15:14:54 foobar kernel: pcieport 0000:00:1d.6: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
> Jun 30 15:14:54 foobar kernel: pcieport 0000:00:1d.6: AER:   device [8086:a336] error status/mask=00001000/00002000
> Jun 30 15:14:54 foobar kernel: pcieport 0000:00:1d.6: AER:    [12] Timeout  

> $ lspci -nn | grep 00:1d.6
> 00:1d.6 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #15 [8086:a336] (rev f0)

It was occuring a few times a day when I was on wireless (Intel Wireless-AC 9560), but coping GBs of files over sshfs with a 1Gbps direct ethernet connection (RTL8111/8168/8411) it started to be logged 20-30 times per second limiting effective transfer rate to ~100Mbps. With disabled advanced error reporting ("pci=noaer") errors are no longer printed and I had ~1Gbps with sshfs, but it only hides an underlying problem with hardware.
(there could be some issues with a cable placement, but in the attempt with pci=noaer the same cable was used)

My laptop is Hyperbook NH5/Clevo NH55RCQ. The other hardware:

$ lspci -nn
> 00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers [8086:3ec4] (rev 07)
> 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07)
> 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b]
> 00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Lake PCH Thermal Controller [8086:a379] (rev 10)
> 00:14.0 USB controller [0c03]: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller [8086:a36d] (rev 10)
> 00:14.2 RAM memory [0500]: Intel Corporation Cannon Lake PCH Shared SRAM [8086:a36f] (rev 10)
> 00:14.3 Network controller [0280]: Intel Corporation Wireless-AC 9560 [Jefferson Peak] [8086:a370] (rev 10)
> 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 [8086:a368] (rev 10)
> 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1 [8086:a369] (rev 10)
> 00:16.0 Communication controller [0780]: Intel Corporation Cannon Lake PCH HECI Controller [8086:a360] (rev 10)
> 00:17.0 SATA controller [0106]: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller [8086:a353] (rev 10)
> 00:1b.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 [8086:a32c] (rev f0)
> 00:1d.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 [8086:a330] (rev f0)
> 00:1d.6 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #15 [8086:a336] (rev f0)
> 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a30d] (rev 10)
> 00:1f.3 Audio device [0403]: Intel Corporation Cannon Lake PCH cAVS [8086:a348] (rev 10)
> 00:1f.4 SMBus [0c05]: Intel Corporation Cannon Lake PCH SMBus Controller [8086:a323] (rev 10)
> 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller [8086:a324] (rev 10)
> 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1)
> 01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:1aeb] (rev a1)
> 01:00.2 USB controller [0c03]: NVIDIA Corporation Device [10de:1aec] (rev a1)
> 01:00.3 Serial bus controller [0c80]: NVIDIA Corporation Device [10de:1aed] (rev a1)
> 06:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981 [144d:a808]
> 08:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader [10ec:5287] (rev 01)
> 08:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)

Comment 8

Marcin Zajaczkowski

2019-07-04 09:32:00 UTC

(In reply to Marcin Zajaczkowski from comment #7)
> It was occuring a few times a day when I was on wireless (Intel Wireless-AC
> 9560), but coping GBs of files over sshfs with a 1Gbps direct ethernet
> connection (RTL8111/8168/8411) it started to be logged 20-30 times per
> second limiting effective transfer rate to ~100Mbps. With disabled advanced
> error reporting ("pci=noaer") errors are no longer printed and I had ~1Gbps
> with sshfs, but it only hides an underlying problem with hardware.
> (there could be some issues with a cable placement, but in the attempt with
> pci=noaer the same cable was used)

To be clear, I have some doubts that the errors itself were limiting the transfer speed to 100Mbps. There could be some issues with a cable. Nevertheless, the flood in the logs could have some impact on the performance.

Comment 9

Adam

2019-08-12 07:35:39 UTC

Hello,

I'm new to Fedora, bugzilla and Linux in general. I have a similar issue so I wasn't sure to file it as another bug or mention it here.

Here is the error in the system log.

Aug 12 16:56:37 localhost.localdomain kernel: pcieport 0000:40:01.1: AER: Multiple Corrected error received: 0000:41:00.0
Aug 12 16:56:37 localhost.localdomain kernel: nvme 0000:41:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 12 16:56:37 localhost.localdomain kernel: nvme 0000:41:00.0: AER:   device [144d:a808] error status/mask=00000001/0000e000
Aug 12 16:56:37 localhost.localdomain kernel: nvme 0000:41:00.0: AER:    [ 0] RxErr 

Over 2700 lines of that message gets repeated.

Here is some additional information that might be useful.

kernal version: 5.2.7-200.fc30.x86_64 (I updated Fedora 30 just before these errors occur but these error was also in the previous versions)

CPU: Threadripper 1950x

Motherboard: ASUS Zenith Extreme

BIOS: 1601

Programs/commands running: "sudo journalctl -f", "sudo iotop -a", "sudo top", "Windows Server 2019 guest vm (in ramfs) using kvm via qemu 4 via libvert"

0000:41:00.0 is the pcie address of the Zenith Extreme's Dimm.2 slot that is not facing the CPU socket. Currently that slot is housing a Samsung 970 Pro nvme SSD.

Comment 10

Renich Bon Ciric

2019-11-01 17:16:01 UTC

I am suffering, apparently, of the same issue:

Nov 01 11:03:31 introdesk.g02.org kernel: pcieport 0000:00:01.3: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 01 11:03:31 introdesk.g02.org kernel: pcieport 0000:00:01.3: AER:   device [1022:1453] error status/mask=00000040/00006000
Nov 01 11:03:31 introdesk.g02.org kernel: pcieport 0000:00:01.3: AER:    [ 6] BadTLP                

My specs:

=== fpaste 0.4.0.1 System Information (fpaste --sysinfo) ===
* OS Release (cat /etc/*-release | uniq):
     Fedora release 31 (Thirty One)
     NAME=Fedora
     VERSION="31 (Workstation Edition)"
     ID=fedora
     VERSION_ID=31
     VERSION_CODENAME=""
     PLATFORM_ID="platform:f31"
     PRETTY_NAME="Fedora 31 (Workstation Edition)"
     ANSI_COLOR="0;34"
     LOGO=fedora-logo-icon
     CPE_NAME="cpe:/o:fedoraproject:fedora:31"
     HOME_URL="https://fedoraproject.org/"
     DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f31/system-administrators-guide/"
     SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
     BUG_REPORT_URL="https://bugzilla.redhat.com/"
     REDHAT_BUGZILLA_PRODUCT="Fedora"
     REDHAT_BUGZILLA_PRODUCT_VERSION=31
     REDHAT_SUPPORT_PRODUCT="Fedora"
     REDHAT_SUPPORT_PRODUCT_VERSION=31
     PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
     VARIANT="Workstation Edition"
     VARIANT_ID=workstation
     Fedora release 31 (Thirty One)
     
* Kernel (uname -r ; cat /proc/cmdline):
     5.3.7-301.fc31.x86_64
     BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.3.7-301.fc31.x86_64 root=UUID=b4f9a4c8-0f96-484d-915d-44ba1f92cb0e ro rootflags=subvol=root-f31 resume=UUID=ee364a6f-f2a6-44bb-a1d1-4bf8950650ac rhgb quiet
     
* Desktop(s) Running (ps -eo comm= | grep -E '(gnome-session|startkde|startactive|xfce.?-session|fluxbox|blackbox|hackedbox|ratpoison|enlightenment|icewm-session|od-session|wmaker|wmx|openbox-lxde|openbox-gnome-session|openbox-kde-session|mwm|e16|fvwm|xmonad|sugar-session|mate-session|lxqt-session|cinnamon)' ):
     gnome-session-b
     gnome-session-c
     gnome-session-b
     
* Desktop(s) Installed (ls -m /usr/share/xsessions/ | sed 's/.desktop//g' ):
     gnome-classic, gnome, gnome-xorg
     
* SELinux Status (sestatus):
     SELinux status:                 enabled
     SELinuxfs mount:                /sys/fs/selinux
     SELinux root directory:         /etc/selinux
     Loaded policy name:             targeted
     Current mode:                   enforcing
     Mode from config file:          enforcing
     Policy MLS status:              enabled
     Policy deny_unknown status:     allowed
     Memory protection checking:     actual (secure)
     Max kernel policy version:      31
     
* SELinux Errors (without results: "selinuxenabled && journalctl --since yesterday |grep avc: | grep -Eo comm="[^ ]+" | sort |uniq -c |sort -rn"):
     N/A

* CPU Model (grep 'model name' /proc/cpuinfo | awk -F: '{print $2}' | uniq -c |
         sed -re 's/^ +//' ):
     16  AMD Ryzen 7 1800X Eight-Core Processor
     
* 64-bit Support (grep -q ' lm ' /proc/cpuinfo && echo Yes || echo No):
     Yes
     
* Hardware Virtualization Support (grep -Eq '(vmx|svm)' /proc/cpuinfo && echo Yes || echo No):
     Yes
     
* Load average (uptime):
      11:15:24 up 39 min,  1 user,  load average: 0.29, 0.22, 0.31
     
* Memory usage (free -m):
                   total        used        free      shared  buff/cache   available
     Mem:          64312        3905       50782         232        9624       59467
     Swap:         32269           0       32269
     
* Top 5 CPU hogs (ps axuScnh | awk '$2!=13746' | sort -rnk3 | head -5):
            0       1 15.0  0.0 176108 17420 ?        Ss   10:35   5:58 systemd
         1000   10618 12.3  0.8 3725848 570716 ?      Sl   10:46   3:31 firefox
         1000   12453  9.9  0.4 3086372 322352 ?      Sl   10:52   2:17 Web Content
         1000    9465  3.3  0.1 2920716 111276 tty3   Sl+  10:46   0:57 Xorg
         1000   10809  2.6  0.8 3252320 544296 ?      Sl   10:46   0:45 Web Content
     
* Top 5 Memory hogs (ps axuScnh | sort -rnk4 | head -5):
         1000   10809  2.6  0.8 3252320 544296 ?      Sl   10:46   0:45 Web Content
         1000   10618 12.3  0.8 3725848 570716 ?      Sl   10:46   3:31 firefox
         1000   10839  1.0  0.6 3107708 455884 ?      Sl   10:46   0:17 Web Content
         1000   10817  1.7  0.6 3111396 458196 ?      Sl   10:46   0:29 Web Content
         1000   12453  9.9  0.4 3086372 322352 ?      Sl   10:52   2:17 Web Content
     
* Disk space usage (df -hT):
     Filesystem     Type      Size  Used Avail Use% Mounted on
     devtmpfs       devtmpfs   32G     0   32G   0% /dev
     tmpfs          tmpfs      32G  176M   32G   1% /dev/shm
     tmpfs          tmpfs      32G  2.2M   32G   1% /run
     /dev/nvme0n1p4 btrfs     445G  183G  260G  42% /
     tmpfs          tmpfs      32G   32M   32G   1% /tmp
     /dev/nvme0n1p4 btrfs     445G  183G  260G  42% /var
     /dev/nvme0n1p4 btrfs     445G  183G  260G  42% /srv
     /dev/nvme0n1p4 btrfs     445G  183G  260G  42% /home
     /dev/nvme0n1p2 ext4      976M  152M  757M  17% /boot
     /dev/nvme0n1p1 vfat      200M   20M  181M  10% /boot/efi
     tmpfs          tmpfs     6.3G   92K  6.3G   1% /run/user/1000
     
* Block devices (blkid):
     /dev/sda1: LABEL="archive" UUID="6d0104f1-d372-4031-8972-4921f5369117" UUID_SUB="c07dffa5-529e-4c7e-b210-59229c9b0c32" TYPE="btrfs" PARTUUID="9013fde2-1922-4566-a062-5782f299a47a"
     /dev/nvme0n1p1: SEC_TYPE="msdos" LABEL_FATBOOT="efi" LABEL="efi" UUID="0210-6250" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="face6c9c-6d73-48ec-aa39-a459097618b1"
     /dev/nvme0n1p2: LABEL="boot" UUID="9e686975-e9a7-40cd-9153-45cbbae12cac" TYPE="ext4" PARTUUID="baee3b8c-492b-4dba-91fa-1a9a2980f3a8"
     /dev/nvme0n1p3: LABEL="swap" UUID="ee364a6f-f2a6-44bb-a1d1-4bf8950650ac" TYPE="swap" PARTUUID="78998368-c355-4134-9438-336c3582c33b"
     /dev/nvme0n1p4: LABEL="fedora" UUID="b4f9a4c8-0f96-484d-915d-44ba1f92cb0e" UUID_SUB="359a1e6d-1efa-432a-9004-005c18acab1f" TYPE="btrfs" PARTUUID="144b1704-9fcf-4934-99da-f97be9a52860"
     
* PCI devices (lspci):
     00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex
     00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit
     00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
     00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
     00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
     00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
     00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
     00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
     00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
     00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
     00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
     00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
     00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
     00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
     00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
     00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
     00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
     00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
     00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
     00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
     00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
     00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
     00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
     01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961
     02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller (rev 02)
     02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset SATA Controller (rev 02)
     02:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset PCIe Upstream Port (rev 02)
     03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
     03:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
     03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
     03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
     03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
     03:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
     03:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
     04:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
     05:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
     06:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
     0a:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)
     0b:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 14a0 (rev c1)
     0c:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 14a1
     0d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] (rev c1)
     0d:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII]
     0e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
     0e:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor
     0e:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller
     0f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function
     0f:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
     0f:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller
     
* USB devices (lsusb):
     Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
     Bus 005 Device 005: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012
     Bus 005 Device 004: ID 0d8c:0012 C-Media Electronics, Inc. Scarlett 18i20 USB
     Bus 005 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
     Bus 005 Device 002: ID 1235:800c Focusrite-Novation Scarlett 18i20
     Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
     Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
     Bus 003 Device 002: ID 145f:024b Trust Trust Wired Keyboard
     Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
     Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
     Bus 001 Device 004: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
     Bus 001 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
     Bus 001 Device 002: ID 0b05:1825 ASUSTek Computer, Inc. Qualcomm Bluetooth 4.1
     Bus 001 Device 007: ID 043e:9a39 LG Electronics USA, Inc. 
     Bus 001 Device 008: ID 09e8:0045 AKAI  Professional M.I. Corp. 
     Bus 001 Device 006: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
     Bus 001 Device 005: ID 093a:2532 Pixart Imaging, Inc. Gaming Mouse
     Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
     
* DRM Information (journalctl -k -b | grep -o 'kernel:.*drm.*$' | cut -d ' ' -f 2- ):
     [drm] amdgpu kernel modesetting enabled.
     fb0: switching to amdgpudrmfb from EFI VGA
     [drm] initializing kernel modesetting (VEGA20 0x1002:0x66AF 0x1002:0x081E 0xC1).
     [drm] register mmio base: 0xFCB00000
     [drm] register mmio size: 524288
     [drm] add ip block number 0 <soc15_common>
     [drm] add ip block number 1 <gmc_v9_0>
     [drm] add ip block number 2 <vega10_ih>
     [drm] add ip block number 3 <psp>
     [drm] add ip block number 4 <gfx_v9_0>
     [drm] add ip block number 5 <sdma_v4_0>
     [drm] add ip block number 6 <powerplay>
     [drm] add ip block number 7 <dm>
     [drm] add ip block number 8 <uvd_v7_0>
     [drm] add ip block number 9 <vce_v4_0>
     [drm] UVD(0) is enabled in VM mode
     [drm] UVD(1) is enabled in VM mode
     [drm] UVD(0) ENC is enabled in VM mode
     [drm] UVD(1) ENC is enabled in VM mode
     [drm] VCE enabled in VM mode
     [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
     [drm] Detected VRAM RAM=16368M, BAR=256M
     [drm] RAM width 4096bits HBM
     [drm] amdgpu: 16368M of VRAM memory ready
     [drm] amdgpu: 16368M of GTT memory ready.
     [drm] GART: num cpu pages 131072, num gpu pages 131072
     [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
     [drm] use_doorbell being set to: [true]
     [drm] use_doorbell being set to: [true]
     [drm] Found UVD firmware ENC: 1.1 DEC: .23 Family ID: 19
     [drm] PSP loading UVD firmware
     [drm] Found VCE firmware Version: 55.5 Binary ID: 4
     [drm] PSP loading VCE firmware
     [drm] reserve 0x400000 from 0x8000c00000 for PSP TMR
     [drm] Display Core initialized with v3.2.35!
     [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
     [drm] Driver supports precise vblank timestamp query.
     [drm] UVD and UVD ENC initialized successfully.
     [drm] VCE initialized successfully.
     [drm] fb mappable at 0xE1000000
     [drm] vram apper at 0xE0000000
     [drm] size 19906560
     [drm] fb depth is 24
     [drm]    pitch is 13824
     fbcon: amdgpudrmfb (fb0) is primary device
     amdgpu 0000:0d:00.0: fb0: amdgpudrmfb frame buffer device
     [drm] ECC is not present.
     [drm] SRAM ECC is not present.
     [drm] Initialized amdgpu 3.33.0 20150101 for 0000:0d:00.0 on minor 0
     [drm] Fence fallback timer expired on ring gfx
     [drm] Fence fallback timer expired on ring comp_1.0.0
     [drm] Fence fallback timer expired on ring comp_1.1.0
     
* Xorg modules (grep LoadModule /var/log/Xorg.0.log ~/.local/share/xorg/Xorg.0.log | cut -d " -f 2 | xargs):
     
     
* GL Support (glxinfo | grep -E "OpenGL version|OpenGL renderer"):
     OpenGL renderer string: AMD Radeon VII (VEGA20, DRM 3.33.0, 5.3.7-301.fc31.x86_64, LLVM 9.0.0)
     OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.2.0
     
* Xorg errors (without results: "grep '^[.*(EE)' /var/log/Xorg.0.log ~/.local/share/xorg/Xorg.0.log | cut -d ':' -f 2- "):
     N/A

* Kernel buffer tail (dmesg | tail):
     [  652.395706] broken atomic modeset userspace detected, disabling atomic
     [  654.467202] rfkill: input handler disabled
     [ 1669.318158] pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
     [ 1669.318163] pcieport 0000:00:01.3: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
     [ 1669.318166] pcieport 0000:00:01.3: AER:   device [1022:1453] error status/mask=00000040/00006000
     [ 1669.318168] pcieport 0000:00:01.3: AER:    [ 6] BadTLP                
     [ 1832.850568] pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
     [ 1832.850574] pcieport 0000:00:01.3: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
     [ 1832.850576] pcieport 0000:00:01.3: AER:   device [1022:1453] error status/mask=00001000/00006000
     [ 1832.850578] pcieport 0000:00:01.3: AER:    [12] Timeout               
     
* Last few reboots (last -x -n10 reboot runlevel):
     runlevel (to lvl 5)   5.3.7-301.fc31.x Fri Nov  1 10:36   still running
     reboot   system boot  5.3.7-301.fc31.x Fri Nov  1 10:35   still running
     runlevel (to lvl 5)   5.3.7-301.fc31.x Thu Oct 31 20:00 - 10:36  (14:35)
     reboot   system boot  5.3.7-301.fc31.x Thu Oct 31 19:59   still running
     runlevel (to lvl 5)   5.3.7-301.fc31.x Thu Oct 31 16:18 - 20:00  (03:41)
     reboot   system boot  5.3.7-301.fc31.x Thu Oct 31 16:18   still running
     runlevel (to lvl 5)   5.3.7-301.fc31.x Thu Oct 31 16:01 - 16:18  (00:17)
     reboot   system boot  5.3.7-301.fc31.x Thu Oct 31 16:01   still running
     reboot   system boot  5.3.7-301.fc31.x Thu Oct 31 15:56   still running
     runlevel (to lvl 5)   5.3.7-301.fc31.x Thu Oct 31 09:05 - 15:55  (06:50)
     
     wtmp begins Wed Oct 30 00:44:56 2019
     
* DNF Repositories (dnf repolist):
     repo id                     repo name                                     status
     *fedora                     Fedora 31 - x86_64                            56,252
     *fedora-modular             Fedora Modular 31 - x86_64                       142
     *rpmfusion-free             RPM Fusion for Fedora 31 - Free                  588
     *rpmfusion-free-updates     RPM Fusion for Fedora 31 - Free - Updates         10
     *rpmfusion-nonfree          RPM Fusion for Fedora 31 - Nonfree               218
     *rpmfusion-nonfree-updates  RPM Fusion for Fedora 31 - Nonfree - Updates       4
     *updates                    Fedora 31 - x86_64 - Updates                   2,642
     *updates-modular            Fedora Modular 31 - x86_64 - Updates             141
     
* DNF Extras (dnf -C list extras):
     Last metadata expiration check: 0:29:39 ago on Fri 01 Nov 2019 10:45:48 AM CST.
     
* Last 20 packages installed (rpm -qa --nodigest --nosignature --last | head -20):
     irqbalance-1.4.0-4.fc31.x86_64                Fri 01 Nov 2019 11:08:08 AM CST
     qt5-qtdeclarative-5.12.5-4.fc31.x86_64        Fri 01 Nov 2019 10:45:37 AM CST
     golang-bin-1.13.3-1.fc31.x86_64               Fri 01 Nov 2019 10:45:36 AM CST
     golang-1.13.3-1.fc31.x86_64                   Fri 01 Nov 2019 10:45:36 AM CST
     cups-filesystem-2.2.12-3.fc31.noarch          Fri 01 Nov 2019 10:45:36 AM CST
     cups-2.2.12-3.fc31.x86_64                     Fri 01 Nov 2019 10:45:36 AM CST
     golang-src-1.13.3-1.fc31.noarch               Fri 01 Nov 2019 10:45:34 AM CST
     cups-ipptool-2.2.12-3.fc31.x86_64             Fri 01 Nov 2019 10:45:32 AM CST
     cups-client-2.2.12-3.fc31.x86_64              Fri 01 Nov 2019 10:45:32 AM CST
     cups-libs-2.2.12-3.fc31.x86_64                Fri 01 Nov 2019 10:45:31 AM CST
     obs-studio-libs-24.0.3-2.fc31.x86_64          Thu 31 Oct 2019 06:47:44 PM CST
     obs-studio-24.0.3-2.fc31.x86_64               Thu 31 Oct 2019 06:47:44 PM CST
     x264-0.157-12.20190717git34c06d1.fc31.x86_64  Thu 31 Oct 2019 06:47:43 PM CST
     qt5-qtsvg-5.12.5-1.fc31.x86_64                Thu 31 Oct 2019 06:47:43 PM CST
     mbedtls-2.16.3-1.fc31.x86_64                  Thu 31 Oct 2019 06:47:43 PM CST
     linux-firmware-20190923-102.fc31.noarch       Thu 31 Oct 2019 04:04:54 PM CST
     libguestfs-xfs-1.40.2-8.fc31.x86_64           Thu 31 Oct 2019 09:36:05 AM CST
     libguestfs-tools-c-1.40.2-8.fc31.x86_64       Thu 31 Oct 2019 09:36:05 AM CST
     libguestfs-1.40.2-8.fc31.x86_64               Thu 31 Oct 2019 09:36:05 AM CST
     hexedit-1.2.13-16.fc31.x86_64                 Thu 31 Oct 2019 09:36:05 AM CST
     
* EFI boot manager output (efibootmgr -v):
     BootCurrent: 0000
     Timeout: 1 seconds
     BootOrder: 0000,0017,0011,0012,0013
     Boot0000* Fedora	HD(1,GPT,face6c9c-6d73-48ec-aa39-a459097618b1,0x800,0x64000)/File(EFIFEDORASHIMX64.EFI)
     Boot0011  Hard Drive	BBS(HD,,0x0)..GO..NO........u.S.T.4.0.0.0.D.M.0.0.5.-.2.D.P.1.6.6....................A.................................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .G.Z.0.Y.F.J.Z.9........BO
     Boot0012  UEFI: PXE IP4 Intel(R) I211 Gigabit  Network Connection	PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(6045cba163b1,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
     Boot0013  UEFI: PXE IP6 Intel(R) I211 Gigabit  Network Connection	PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x2)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(6045cba163b1,1)/IPv6([::]:<->[::]:,0,0)..BO
     Boot0017* Fedora	HD(1,GPT,face6c9c-6d73-48ec-aa39-a459097618b1,0x800,0x64000)/File(EFIFEDORASHIM.EFI)..BO

This stopped occuring after adding "pcie_aspm=off iommu=1 amd_iommu=on" on vanilla kernel  head 5.5.rc4 commit 7ca4ad5ba886557b67d42242a80f303c3a99ded1 (iommu enabled on bios)

Comment 12

Marcin Zajaczkowski

2020-01-23 11:47:00 UTC

(In reply to burak from comment #11)
> This stopped occuring after adding "pcie_aspm=off iommu=1 amd_iommu=on" on
> vanilla kernel  head 5.5.rc4 commit 7ca4ad5ba886557b67d42242a80f303c3a99ded1

The same also worked for me with kernel-core-5.5.0-0.rc5.git0.1.fc32.x86_64.

Comment 13

Dariusz Wojewódzki

2020-02-19 21:47:09 UTC

Issue occurs also on RHEL8.1 (Ootpa)

[d@dwlab Desktop]$ uname -r
4.18.0-147.5.1.el8_1.x86_64

[d@dwlab Desktop]$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
00:16.3 Serial controller: Intel Corporation 100 Series/C230 Series Chipset Family KT Redirection (rev 31)
00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
00:1b.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 (rev f1)
00:1f.0 ISA bridge: Intel Corporation C236 Chipset LPC/eSPI Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro K2200] (rev a2)
01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 (rev 01)

[d@dwlab Desktop]$ dmesg|grep "pcieport 0000:00:1b.0"|tail -n 4
[   16.134734] pcieport 0000:00:1b.0: AER: Corrected error received: 0000:00:1b.0
[   16.134751] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   16.134759] pcieport 0000:00:1b.0:   device [8086:a167] error status/mask=00000001/00002000
[   16.134763] pcieport 0000:00:1b.0:    [ 0] RxErr

Comment 14

Chris Moeller

2020-03-29 01:08:57 UTC

Issue also occurred on Arch Linux, so it's not distribution specific, or specific to the LTS kernel.

[chris@mrgency]$ uname -r
5.5.13-28-tkg-cfs

[chris@mrgency]$ journalctl -b -1 | tail -n 8
Mar 28 17:19:56 mrgency kernel: pcieport 0000:00:03.1: AER: Multiple Corrected error received: 0000:00:00.0
Mar 28 17:19:56 mrgency kernel: pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Mar 28 17:19:56 mrgency kernel: pcieport 0000:00:03.1: AER:   device [1022:1453] error status/mask=00001100/00006000
Mar 28 17:19:56 mrgency kernel: pcieport 0000:00:03.1: AER:    [ 8] Rollover              
Mar 28 17:19:56 mrgency kernel: pcieport 0000:00:03.1: AER:    [12] Timeout               
Mar 28 17:19:56 mrgency kernel: pcieport 0000:00:03.1: AER: Multiple Corrected error received: 0000:00:00.0
Mar 28 17:19:56 mrgency kernel: pcieport 0000:00:03.1: AER: can't find device of ID0000

I don't have a lspci because I'm not booted into that operating system right now, as it's not really desired to continue crashing my way through the day.

Comment 15

Chris Moeller

2020-03-29 01:10:27 UTC

Crud, sorry, remembered some details that would be relevant.

00:03.1 would be the GPP that's attached to my GPU, an Asus ROG Strix RX 480 O8G.

Comment 17

lcividin

2022-07-17 00:41:51 UTC

I've started seeing an error on fedora 36 fairly recent install and only seeing this symptom after a recent update to the kernel. 


lcividin@fedora:$ uname -a 
Linux fedora 5.18.11-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Jul 12 22:52:35 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

lcividin@fedora:$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers [8086:3ec4] (rev 07)
00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07)
00:02.0 VGA compatible controller [0300]: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b]
00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Lake PCH Thermal Controller [8086:a379] (rev 10)
00:14.0 USB controller [0c03]: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller [8086:a36d] (rev 10)
00:14.2 RAM memory [0500]: Intel Corporation Cannon Lake PCH Shared SRAM [8086:a36f] (rev 10)
00:17.0 SATA controller [0106]: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller [8086:a353] (rev 10)
00:1d.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 [8086:a330] (rev f0)
00:1d.5 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #14 [8086:a335] (rev f0)
00:1d.6 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #15 [8086:a336] (rev f0)
00:1d.7 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #16 [8086:a337] (rev f0)
00:1f.0 ISA bridge [0601]: Intel Corporation HM470 Chipset LPC/eSPI Controller [8086:a30d] (rev 10)
00:1f.3 Audio device [0403]: Intel Corporation Cannon Lake PCH cAVS [8086:a348] (rev 10)
00:1f.4 SMBus [0c05]: Intel Corporation Cannon Lake PCH SMBus Controller [8086:a323] (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller [8086:a324] (rev 10)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1ba1] (rev a1)
01:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio Controller [10de:10f0] (rev a1)
02:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808]
03:00.0 Network controller [0280]: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
05:00.0 SD Host controller [0805]: Realtek Semiconductor Co., Ltd. RTS5250 PCI Express Card Reader [10ec:5250] (rev 01)

lcividin@fedora:$ cat /proc/cpuinfo | grep "model name" 
model name	: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz

lcividin@fedora:$ dmesg|grep "pcieport 0000:00:1d.6"|tail -n 4
[ 5005.427251] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: 0000:00:1d.6
[ 5005.427282] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 5005.427289] pcieport 0000:00:1d.6:   device [8086:a336] error status/mask=00000001/00002000
[ 5005.427298] pcieport 0000:00:1d.6:    [ 0] RxErr 

systemd-journald is using around 97% of the cpu and just spewing out the following error

lcividin@fedora:~$ journalctl -f 
Jul 17 10:30:29 fedora kernel: pcieport 0000:00:1d.6:   device [8086:a336] error status/mask=00000001/00002000
Jul 17 10:30:29 fedora kernel: pcieport 0000:00:1d.6:    [ 0] RxErr                 
Jul 17 10:30:29 fedora kernel: pcieport 0000:00:1d.6: AER: Multiple Corrected error received: 0000:00:1d.6
Jul 17 10:30:29 fedora kernel: pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jul 17 10:30:29 fedora kernel: pcieport 0000:00:1d.6:   device [8086:a336] error status/mask=00000001/00002000
Jul 17 10:30:29 fedora kernel: pcieport 0000:00:1d.6:    [ 0] RxErr                 
Jul 17 10:30:29 fedora kernel: pcieport 0000:00:1d.6: AER: Multiple Corrected error received: 0000:00:1d.6

last two upgrades with kernel updates 
Transaction ID : 47
Begin time     : Sat 16 Jul 2022 08:41:07
Begin rpmdb    : f235b9c526304ead2f4866c083c360904f469875 **
End time       : Sat 16 Jul 2022 08:43:12 (125 seconds)
End rpmdb      : 091e4a117eb47bb3fe52adb98ebe647d934cbf40
User           : lcividin <lcividin>
Return-Code    : Success
Releasever     : 36
Command Line   : upgrade -y
Comment        : 
Packages Altered:
    Install       kernel-5.18.11-200.fc36.x86_64                          @updates
    Install       kernel-core-5.18.11-200.fc36.x86_64                     @updates
    Install       kernel-devel-5.18.11-200.fc36.x86_64                    @updates
    Install       kernel-modules-5.18.11-200.fc36.x86_64                  @updates
    Install       kernel-modules-extra-5.18.11-200.fc36.x86_64            @updates
    Upgrade       SDL2-2.0.22-3.fc36.i686                                 @updates
    Upgraded      SDL2-2.0.22-2.fc36.i686                                 @@System
    Upgrade       SDL2-2.0.22-3.fc36.x86_64                               @updates
    Upgraded      SDL2-2.0.22-2.fc36.x86_64                               @@System
    Upgrade       autocorr-en-1:7.3.4.2-4.fc36.noarch                     @updates
    Upgraded      autocorr-en-1:7.3.4.2-1.fc36.noarch                     @@System
    Upgrade       brlapi-0.8.4-4.fc36.x86_64                              @updates
    Upgraded      brlapi-0.8.3-6.fc36.x86_64                              @@System
    Upgrade       brltty-6.5-4.fc36.x86_64                                @updates
    Upgraded      brltty-6.4-6.fc36.x86_64                                @@System
    Upgrade       freetype-2.12.1-2.fc36.i686                             @updates
    Upgraded      freetype-2.12.1-1.fc36.i686                             @@System
    Upgrade       freetype-2.12.1-2.fc36.x86_64                           @updates
    Upgraded      freetype-2.12.1-1.fc36.x86_64                           @@System
    Upgrade       fwupd-1.8.2-1.fc36.x86_64                               @updates
    Upgraded      fwupd-1.8.1-1.fc36.x86_64                               @@System
    Upgrade       fwupd-plugin-flashrom-1.8.2-1.fc36.x86_64               @updates
    Upgraded      fwupd-plugin-flashrom-1.8.1-1.fc36.x86_64               @@System
    Upgrade       fwupd-plugin-modem-manager-1.8.2-1.fc36.x86_64          @updates
    Upgraded      fwupd-plugin-modem-manager-1.8.1-1.fc36.x86_64          @@System
    Upgrade       fwupd-plugin-uefi-capsule-data-1.8.2-1.fc36.x86_64      @updates
    Upgraded      fwupd-plugin-uefi-capsule-data-1.8.1-1.fc36.x86_64      @@System
    Upgrade       gnome-bluetooth-1:42.2-1.fc36.x86_64                    @updates
    Upgraded      gnome-bluetooth-1:42.1-1.fc36.x86_64                    @@System
    Upgrade       gnome-bluetooth-libs-1:42.2-1.fc36.x86_64               @updates
    Upgraded      gnome-bluetooth-libs-1:42.1-1.fc36.x86_64               @@System
    Upgrade       gnome-boxes-42.3-1.fc36.x86_64                          @updates
    Upgraded      gnome-boxes-42.1-1.fc36.x86_64                          @@System
    Upgrade       gnome-maps-42.3-1.fc36.x86_64                           @updates
    Upgraded      gnome-maps-42.2-1.fc36.x86_64                           @@System
    Upgrade       gnome-remote-desktop-42.3-1.fc36.x86_64                 @updates
    Upgraded      gnome-remote-desktop-42.2-2.fc36.x86_64                 @@System
    Upgrade       gnupg2-2.3.7-1.fc36.x86_64                              @updates
    Upgraded      gnupg2-2.3.6-2.fc36.x86_64                              @@System
    Upgrade       gnupg2-smime-2.3.7-1.fc36.x86_64                        @updates
    Upgraded      gnupg2-smime-2.3.6-2.fc36.x86_64                        @@System
    Upgrade       ibus-typing-booster-2.17.0-1.fc36.noarch                @updates
    Upgraded      ibus-typing-booster-2.16.7-1.fc36.noarch                @@System
    Upgrade       libgphoto2-2.5.30-2.fc36.i686                           @updates
    Upgraded      libgphoto2-2.5.29-1.fc36.i686                           @@System
    Upgrade       libgphoto2-2.5.30-2.fc36.x86_64                         @updates
    Upgraded      libgphoto2-2.5.29-1.fc36.x86_64                         @@System
    Upgrade       libnl3-3.7.0-1.fc36.i686                                @updates
    Upgraded      libnl3-3.6.0-3.fc36.i686                                @@System
    Upgrade       libnl3-3.7.0-1.fc36.x86_64                              @updates
    Upgraded      libnl3-3.6.0-3.fc36.x86_64                              @@System
    Upgrade       libnl3-cli-3.7.0-1.fc36.x86_64                          @updates
    Upgraded      libnl3-cli-3.6.0-3.fc36.x86_64                          @@System
    Upgrade       libreoffice-calc-1:7.3.4.2-4.fc36.x86_64                @updates
    Upgraded      libreoffice-calc-1:7.3.4.2-1.fc36.x86_64                @@System
    Upgrade       libreoffice-core-1:7.3.4.2-4.fc36.x86_64                @updates
    Upgraded      libreoffice-core-1:7.3.4.2-1.fc36.x86_64                @@System
    Upgrade       libreoffice-data-1:7.3.4.2-4.fc36.noarch                @updates
    Upgraded      libreoffice-data-1:7.3.4.2-1.fc36.noarch                @@System
    Upgrade       libreoffice-emailmerge-1:7.3.4.2-4.fc36.x86_64          @updates
    Upgraded      libreoffice-emailmerge-1:7.3.4.2-1.fc36.x86_64          @@System
    Upgrade       libreoffice-filters-1:7.3.4.2-4.fc36.x86_64             @updates
    Upgraded      libreoffice-filters-1:7.3.4.2-1.fc36.x86_64             @@System
    Upgrade       libreoffice-graphicfilter-1:7.3.4.2-4.fc36.x86_64       @updates
    Upgraded      libreoffice-graphicfilter-1:7.3.4.2-1.fc36.x86_64       @@System
    Upgrade       libreoffice-gtk3-1:7.3.4.2-4.fc36.x86_64                @updates
    Upgraded      libreoffice-gtk3-1:7.3.4.2-1.fc36.x86_64                @@System
    Upgrade       libreoffice-help-en-1:7.3.4.2-4.fc36.x86_64             @updates
    Upgraded      libreoffice-help-en-1:7.3.4.2-1.fc36.x86_64             @@System
    Upgrade       libreoffice-impress-1:7.3.4.2-4.fc36.x86_64             @updates
    Upgraded      libreoffice-impress-1:7.3.4.2-1.fc36.x86_64             @@System
    Upgrade       libreoffice-langpack-en-1:7.3.4.2-4.fc36.x86_64         @updates
    Upgraded      libreoffice-langpack-en-1:7.3.4.2-1.fc36.x86_64         @@System
    Upgrade       libreoffice-ogltrans-1:7.3.4.2-4.fc36.x86_64            @updates
    Upgraded      libreoffice-ogltrans-1:7.3.4.2-1.fc36.x86_64            @@System
    Upgrade       libreoffice-opensymbol-fonts-1:7.3.4.2-4.fc36.noarch    @updates
    Upgraded      libreoffice-opensymbol-fonts-1:7.3.4.2-1.fc36.noarch    @@System
    Upgrade       libreoffice-pdfimport-1:7.3.4.2-4.fc36.x86_64           @updates
    Upgraded      libreoffice-pdfimport-1:7.3.4.2-1.fc36.x86_64           @@System
    Upgrade       libreoffice-pyuno-1:7.3.4.2-4.fc36.x86_64               @updates
    Upgraded      libreoffice-pyuno-1:7.3.4.2-1.fc36.x86_64               @@System
    Upgrade       libreoffice-ure-1:7.3.4.2-4.fc36.x86_64                 @updates
    Upgraded      libreoffice-ure-1:7.3.4.2-1.fc36.x86_64                 @@System
    Upgrade       libreoffice-ure-common-1:7.3.4.2-4.fc36.noarch          @updates
    Upgraded      libreoffice-ure-common-1:7.3.4.2-1.fc36.noarch          @@System
    Upgrade       libreoffice-writer-1:7.3.4.2-4.fc36.x86_64              @updates
    Upgraded      libreoffice-writer-1:7.3.4.2-1.fc36.x86_64              @@System
    Upgrade       libreoffice-x11-1:7.3.4.2-4.fc36.x86_64                 @updates
    Upgraded      libreoffice-x11-1:7.3.4.2-1.fc36.x86_64                 @@System
    Upgrade       libreoffice-xsltfilter-1:7.3.4.2-4.fc36.x86_64          @updates
    Upgraded      libreoffice-xsltfilter-1:7.3.4.2-1.fc36.x86_64          @@System
    Upgrade       libsoup3-3.0.7-1.fc36.x86_64                            @updates
    Upgraded      libsoup3-3.0.6-1.fc36.x86_64                            @@System
    Upgrade       libtiff-4.4.0-2.fc36.i686                               @updates
    Upgraded      libtiff-4.4.0-1.fc36.i686                               @@System
    Upgrade       libtiff-4.4.0-2.fc36.x86_64                             @updates
    Upgraded      libtiff-4.4.0-1.fc36.x86_64                             @@System
    Upgrade       libtracker-sparql-3.3.2-1.fc36.i686                     @updates
    Upgraded      libtracker-sparql-3.3.1-1.fc36.i686                     @@System
    Upgrade       libtracker-sparql-3.3.2-1.fc36.x86_64                   @updates
    Upgraded      libtracker-sparql-3.3.1-1.fc36.x86_64                   @@System
    Upgrade       mpg123-libs-1.30.1-1.fc36.x86_64                        @updates
    Upgraded      mpg123-libs-1.30.0-1.fc36.x86_64                        @@System
    Upgrade       openssl1.1-1:1.1.1q-1.fc36.x86_64                       @updates
    Upgraded      openssl1.1-1:1.1.1p-1.fc36.x86_64                       @@System
    Upgrade       perl-Socket-4:2.035-1.fc36.x86_64                       @updates
    Upgraded      perl-Socket-4:2.034-1.fc36.x86_64                       @@System
    Upgrade       pipewire-0.3.55-2.fc36.i686                             @updates
    Upgraded      pipewire-0.3.54-1.fc36.i686                             @@System
    Upgrade       pipewire-0.3.55-2.fc36.x86_64                           @updates
    Upgraded      pipewire-0.3.54-1.fc36.x86_64                           @@System
    Upgrade       pipewire-alsa-0.3.55-2.fc36.i686                        @updates
    Upgraded      pipewire-alsa-0.3.54-1.fc36.i686                        @@System
    Upgrade       pipewire-alsa-0.3.55-2.fc36.x86_64                      @updates
    Upgraded      pipewire-alsa-0.3.54-1.fc36.x86_64                      @@System
    Upgrade       pipewire-gstreamer-0.3.55-2.fc36.x86_64                 @updates
    Upgraded      pipewire-gstreamer-0.3.54-1.fc36.x86_64                 @@System
    Upgrade       pipewire-jack-audio-connection-kit-0.3.55-2.fc36.x86_64 @updates
    Upgraded      pipewire-jack-audio-connection-kit-0.3.54-1.fc36.x86_64 @@System
    Upgrade       pipewire-libs-0.3.55-2.fc36.i686                        @updates
    Upgraded      pipewire-libs-0.3.54-1.fc36.i686                        @@System
    Upgrade       pipewire-libs-0.3.55-2.fc36.x86_64                      @updates
    Upgraded      pipewire-libs-0.3.54-1.fc36.x86_64                      @@System
    Upgrade       pipewire-pulseaudio-0.3.55-2.fc36.x86_64                @updates
    Upgraded      pipewire-pulseaudio-0.3.54-1.fc36.x86_64                @@System
    Upgrade       pipewire-utils-0.3.55-2.fc36.x86_64                     @updates
    Upgraded      pipewire-utils-0.3.54-1.fc36.x86_64                     @@System
    Upgrade       podman-3:4.1.1-2.fc36.x86_64                            @updates
    Upgraded      podman-3:4.1.1-1.fc36.x86_64                            @@System
    Upgrade       podman-docker-3:4.1.1-2.fc36.noarch                     @updates
    Upgraded      podman-docker-3:4.1.1-1.fc36.noarch                     @@System
    Upgrade       python3-brlapi-0.8.4-4.fc36.x86_64                      @updates
    Upgraded      python3-brlapi-0.8.3-6.fc36.x86_64                      @@System
    Upgrade       subversion-1.14.2-5.fc36.x86_64                         @updates
    Upgraded      subversion-1.14.1-11.fc36.x86_64                        @@System
    Upgrade       subversion-libs-1.14.2-5.fc36.x86_64                    @updates
    Upgraded      subversion-libs-1.14.1-11.fc36.x86_64                   @@System
    Upgrade       sushi-42.0-1.fc36.x86_64                                @updates
    Upgraded      sushi-41.2-2.fc36.x86_64                                @@System
    Upgrade       switcheroo-control-2.6-1.fc36.x86_64                    @updates
    Upgraded      switcheroo-control-2.5-1.fc36.x86_64                    @@System
    Upgrade       tracker-3.3.2-1.fc36.x86_64                             @updates
    Upgraded      tracker-3.3.1-1.fc36.x86_64                             @@System
    Upgrade       vim-data-2:9.0.049-1.fc36.noarch                        @updates
    Upgraded      vim-data-2:8.2.5172-1.fc36.noarch                       @@System
    Upgrade       vim-minimal-2:9.0.049-1.fc36.x86_64                     @updates
    Upgraded      vim-minimal-2:8.2.5172-1.fc36.x86_64                    @@System
    Upgrade       wine-alsa-7.12-1.fc36.i686                              @updates
    Upgraded      wine-alsa-7.10-2.fc36.i686                              @@System
    Upgrade       wine-alsa-7.12-1.fc36.x86_64                            @updates
    Upgraded      wine-alsa-7.10-2.fc36.x86_64                            @@System
    Upgrade       wine-core-7.12-1.fc36.i686                              @updates
    Upgraded      wine-core-7.10-2.fc36.i686                              @@System
    Upgrade       wine-core-7.12-1.fc36.x86_64                            @updates
    Upgraded      wine-core-7.10-2.fc36.x86_64                            @@System
    Upgrade       wine-filesystem-7.12-1.fc36.noarch                      @updates
    Upgraded      wine-filesystem-7.10-2.fc36.noarch                      @@System
    Upgrade       wine-pulseaudio-7.12-1.fc36.i686                        @updates
    Upgraded      wine-pulseaudio-7.10-2.fc36.i686                        @@System
    Upgrade       wine-pulseaudio-7.12-1.fc36.x86_64                      @updates
    Upgraded      wine-pulseaudio-7.10-2.fc36.x86_64                      @@System
    Upgrade       wireplumber-0.4.11-2.fc36.x86_64                        @updates
    Upgraded      wireplumber-0.4.11-1.fc36.x86_64                        @@System
    Upgrade       wireplumber-libs-0.4.11-2.fc36.x86_64                   @updates
    Upgraded      wireplumber-libs-0.4.11-1.fc36.x86_64                   @@System
    Upgrade       xen-libs-4.16.1-5.fc36.x86_64                           @updates
    Upgraded      xen-libs-4.16.1-4.fc36.x86_64                           @@System
    Upgrade       xen-licenses-4.16.1-5.fc36.x86_64                       @updates
    Upgraded      xen-licenses-4.16.1-4.fc36.x86_64                       @@System
    Upgrade       xorg-x11-server-Xephyr-1.20.14-7.fc36.x86_64            @updates
    Upgraded      xorg-x11-server-Xephyr-1.20.14-6.fc36.x86_64            @@System
    Upgrade       xorg-x11-server-Xorg-1.20.14-7.fc36.x86_64              @updates
    Upgraded      xorg-x11-server-Xorg-1.20.14-6.fc36.x86_64              @@System
    Upgrade       xorg-x11-server-Xwayland-22.1.3-1.fc36.x86_64           @updates
    Upgraded      xorg-x11-server-Xwayland-22.1.2-1.fc36.x86_64           @@System
    Upgrade       xorg-x11-server-common-1.20.14-7.fc36.x86_64            @updates
    Upgraded      xorg-x11-server-common-1.20.14-6.fc36.x86_64            @@System
    Reason Change Box2D-2.4.1-7.fc36.x86_64                               @anaconda
    Removed       kernel-5.18.7-200.fc36.x86_64                           @@System
    Removed       kernel-core-5.18.7-200.fc36.x86_64                      @@System
    Removed       kernel-modules-5.18.7-200.fc36.x86_64                   @@System
    Removed       kernel-modules-extra-5.18.7-200.fc36.x86_64             @@System
Scriptlet output:
   1 Failed to start transient service unit: Connection reset by peer
   2 Failed to set unit properties on gnome-remote-desktop.service: Transport endpoint is not connected
   3 warning: file /lib/modules/5.18.7-200.fc36.x86_64/updates: remove failed: No such file or directory
   4 Failed to start transient service unit: Connection reset by peer
   5 Failed to set unit properties on tracker-xdg-portal-3.service: Transport endpoint is not connected
   6 dkms: running auto installation service for kernel 5.18.11-200.fc36.x86_64
   7  Done. 
   8 dkms: running auto installation service for kernel 5.18.11-200.fc36.x86_64
   9  Done. 
-------------------------------------------------------------------------------
Transaction ID : 45
Begin time     : Tue 12 Jul 2022 08:36:26
Begin rpmdb    : 11de6ae3065f0851f6d5f9596e6c3c762a327f1f
End time       : Tue 12 Jul 2022 08:38:21 (115 seconds)
End rpmdb      : 1c450e29d823e7ec05829a7c524e7b27a8aafbdc **
User           : lcividin <lcividin>
Return-Code    : Success
Releasever     : 36
Command Line   : upgrade -y
Comment        : 
Packages Altered:
    Install       fluid-soundfont-common-3.1-26.fc36.noarch                    @fedora
    Install       fluid-soundfont-gm-3.1-26.fc36.noarch                        @fedora
    Install       fluid-soundfont-gs-3.1-26.fc36.noarch                        @fedora
    Install       kernel-5.18.10-200.fc36.x86_64                               @updates
    Install       kernel-core-5.18.10-200.fc36.x86_64                          @updates
    Install       kernel-devel-5.18.10-200.fc36.x86_64                         @updates
    Install       kernel-modules-5.18.10-200.fc36.x86_64                       @updates
    Install       kernel-modules-extra-5.18.10-200.fc36.x86_64                 @updates
    Upgrade       NetworkManager-openconnect-1.2.8-2.fc36.x86_64               @updates
    Upgraded      NetworkManager-openconnect-1.2.8-1.fc36.x86_64               @@System
    Upgrade       NetworkManager-openconnect-gnome-1.2.8-2.fc36.x86_64         @updates
    Upgraded      NetworkManager-openconnect-gnome-1.2.8-1.fc36.x86_64         @@System
    Upgrade       dkms-3.0.5-1.fc36.noarch                                     @updates
    Upgraded      dkms-3.0.4-1.fc36.noarch                                     @@System
    Upgrade       firewalld-1.0.5-2.fc36.noarch                                @updates
    Upgraded      firewalld-1.0.4-1.fc36.noarch                                @@System
    Upgrade       firewalld-filesystem-1.0.5-2.fc36.noarch                     @updates
    Upgraded      firewalld-filesystem-1.0.4-1.fc36.noarch                     @@System
    Upgrade       flatpak-1.12.7-4.fc36.x86_64                                 @updates
    Upgraded      flatpak-1.12.7-3.fc36.x86_64                                 @@System
    Upgrade       flatpak-libs-1.12.7-4.fc36.x86_64                            @updates
    Upgraded      flatpak-libs-1.12.7-3.fc36.x86_64                            @@System
    Upgrade       flatpak-selinux-1.12.7-4.fc36.noarch                         @updates
    Upgraded      flatpak-selinux-1.12.7-3.fc36.noarch                         @@System
    Upgrade       flatpak-session-helper-1.12.7-4.fc36.x86_64                  @updates
    Upgraded      flatpak-session-helper-1.12.7-3.fc36.x86_64                  @@System
    Upgrade       gjs-1.72.1-1.fc36.x86_64                                     @updates
    Upgraded      gjs-1.72.0-5.fc36.x86_64                                     @@System
    Upgrade       glib2-2.72.3-1.fc36.i686                                     @updates
    Upgraded      glib2-2.72.2-1.fc36.i686                                     @@System
    Upgrade       glib2-2.72.3-1.fc36.x86_64                                   @updates
    Upgraded      glib2-2.72.2-1.fc36.x86_64                                   @@System
    Upgrade       glibc-2.35-14.fc36.i686                                      @updates
    Upgraded      glibc-2.35-12.fc36.i686                                      @@System
    Upgrade       glibc-2.35-14.fc36.x86_64                                    @updates
    Upgraded      glibc-2.35-12.fc36.x86_64                                    @@System
    Upgrade       glibc-all-langpacks-2.35-14.fc36.x86_64                      @updates
    Upgraded      glibc-all-langpacks-2.35-12.fc36.x86_64                      @@System
    Upgrade       glibc-common-2.35-14.fc36.x86_64                             @updates
    Upgraded      glibc-common-2.35-12.fc36.x86_64                             @@System
    Upgrade       glibc-devel-2.35-14.fc36.x86_64                              @updates
    Upgraded      glibc-devel-2.35-12.fc36.x86_64                              @@System
    Upgrade       glibc-gconv-extra-2.35-14.fc36.i686                          @updates
    Upgraded      glibc-gconv-extra-2.35-12.fc36.i686                          @@System
    Upgrade       glibc-gconv-extra-2.35-14.fc36.x86_64                        @updates
    Upgraded      glibc-gconv-extra-2.35-12.fc36.x86_64                        @@System
    Upgrade       glibc-headers-x86-2.35-14.fc36.noarch                        @updates
    Upgraded      glibc-headers-x86-2.35-12.fc36.noarch                        @@System
    Upgrade       glibc-langpack-en-2.35-14.fc36.x86_64                        @updates
    Upgraded      glibc-langpack-en-2.35-12.fc36.x86_64                        @@System
    Upgrade       gnome-calculator-42.2-1.fc36.x86_64                          @updates
    Upgraded      gnome-calculator-42.1-1.fc36.x86_64                          @@System
    Upgrade       gnome-classic-session-42.3-1.fc36.noarch                     @updates
    Upgraded      gnome-classic-session-42.2-1.fc36.noarch                     @@System
    Upgrade       gnome-shell-42.3.1-1.fc36.x86_64                             @updates
    Upgraded      gnome-shell-42.2-1.fc36.x86_64                               @@System
    Upgrade       gnome-shell-extension-apps-menu-42.3-1.fc36.noarch           @updates
    Upgraded      gnome-shell-extension-apps-menu-42.2-1.fc36.noarch           @@System
    Upgrade       gnome-shell-extension-common-42.3-1.fc36.noarch              @updates
    Upgraded      gnome-shell-extension-common-42.2-1.fc36.noarch              @@System
    Upgrade       gnome-shell-extension-launch-new-instance-42.3-1.fc36.noarch @updates
    Upgraded      gnome-shell-extension-launch-new-instance-42.2-1.fc36.noarch @@System
    Upgrade       gnome-shell-extension-places-menu-42.3-1.fc36.noarch         @updates
    Upgraded      gnome-shell-extension-places-menu-42.2-1.fc36.noarch         @@System
    Upgrade       gnome-shell-extension-window-list-42.3-1.fc36.noarch         @updates
    Upgraded      gnome-shell-extension-window-list-42.2-1.fc36.noarch         @@System
    Upgrade       gnupg2-2.3.6-2.fc36.x86_64                                   @updates
    Upgraded      gnupg2-2.3.6-1.fc36.x86_64                                   @@System
    Upgrade       gnupg2-smime-2.3.6-2.fc36.x86_64                             @updates
    Upgraded      gnupg2-smime-2.3.6-1.fc36.x86_64                             @@System
    Upgrade       gtk4-4.6.6-1.fc36.x86_64                                     @updates
    Upgraded      gtk4-4.6.5-1.fc36.x86_64                                     @@System
    Upgrade       hwdata-0.361-1.fc36.noarch                                   @updates
    Upgraded      hwdata-0.360-1.fc36.noarch                                   @@System
    Upgrade       libipa_hbac-2.7.3-1.fc36.x86_64                              @updates
    Upgraded      libipa_hbac-2.7.1-2.fc36.x86_64                              @@System
    Upgrade       libnsl-2.35-14.fc36.i686                                     @updates
    Upgraded      libnsl-2.35-12.fc36.i686                                     @@System
    Upgrade       libnsl-2.35-14.fc36.x86_64                                   @updates
    Upgraded      libnsl-2.35-12.fc36.x86_64                                   @@System
    Upgrade       libsss_certmap-2.7.3-1.fc36.x86_64                           @updates
    Upgraded      libsss_certmap-2.7.1-2.fc36.x86_64                           @@System
    Upgrade       libsss_idmap-2.7.3-1.fc36.x86_64                             @updates
    Upgraded      libsss_idmap-2.7.1-2.fc36.x86_64                             @@System
    Upgrade       libsss_nss_idmap-2.7.3-1.fc36.x86_64                         @updates
    Upgraded      libsss_nss_idmap-2.7.1-2.fc36.x86_64                         @@System
    Upgrade       libsss_sudo-2.7.3-1.fc36.x86_64                              @updates
    Upgraded      libsss_sudo-2.7.1-2.fc36.x86_64                              @@System
    Upgrade       lutris-0.5.10.1-5.fc36.x86_64                                @updates
    Upgraded      lutris-0.5.10.1-2.fc36.x86_64                                @@System
    Upgrade       mesa-dri-drivers-22.1.3-1.fc36.i686                          @updates
    Upgraded      mesa-dri-drivers-22.1.2-1.fc36.i686                          @@System
    Upgrade       mesa-dri-drivers-22.1.3-1.fc36.x86_64                        @updates
    Upgraded      mesa-dri-drivers-22.1.2-1.fc36.x86_64                        @@System
    Upgrade       mesa-filesystem-22.1.3-1.fc36.i686                           @updates
    Upgraded      mesa-filesystem-22.1.2-1.fc36.i686                           @@System
    Upgrade       mesa-filesystem-22.1.3-1.fc36.x86_64                         @updates
    Upgraded      mesa-filesystem-22.1.2-1.fc36.x86_64                         @@System
    Upgrade       mesa-libEGL-22.1.3-1.fc36.i686                               @updates
    Upgraded      mesa-libEGL-22.1.2-1.fc36.i686                               @@System
    Upgrade       mesa-libEGL-22.1.3-1.fc36.x86_64                             @updates
    Upgraded      mesa-libEGL-22.1.2-1.fc36.x86_64                             @@System
    Upgrade       mesa-libGL-22.1.3-1.fc36.i686                                @updates
    Upgraded      mesa-libGL-22.1.2-1.fc36.i686                                @@System
    Upgrade       mesa-libGL-22.1.3-1.fc36.x86_64                              @updates
    Upgraded      mesa-libGL-22.1.2-1.fc36.x86_64                              @@System
    Upgrade       mesa-libOSMesa-22.1.3-1.fc36.i686                            @updates
    Upgraded      mesa-libOSMesa-22.1.2-1.fc36.i686                            @@System
    Upgrade       mesa-libOSMesa-22.1.3-1.fc36.x86_64                          @updates
    Upgraded      mesa-libOSMesa-22.1.2-1.fc36.x86_64                          @@System
    Upgrade       mesa-libgbm-22.1.3-1.fc36.i686                               @updates
    Upgraded      mesa-libgbm-22.1.2-1.fc36.i686                               @@System
    Upgrade       mesa-libgbm-22.1.3-1.fc36.x86_64                             @updates
    Upgraded      mesa-libgbm-22.1.2-1.fc36.x86_64                             @@System
    Upgrade       mesa-libglapi-22.1.3-1.fc36.i686                             @updates
    Upgraded      mesa-libglapi-22.1.2-1.fc36.i686                             @@System
    Upgrade       mesa-libglapi-22.1.3-1.fc36.x86_64                           @updates
    Upgraded      mesa-libglapi-22.1.2-1.fc36.x86_64                           @@System
    Upgrade       mesa-libxatracker-22.1.3-1.fc36.x86_64                       @updates
    Upgraded      mesa-libxatracker-22.1.2-1.fc36.x86_64                       @@System
    Upgrade       mesa-vulkan-drivers-22.1.3-1.fc36.i686                       @updates
    Upgraded      mesa-vulkan-drivers-22.1.2-1.fc36.i686                       @@System
    Upgrade       mesa-vulkan-drivers-22.1.3-1.fc36.x86_64                     @updates
    Upgraded      mesa-vulkan-drivers-22.1.2-1.fc36.x86_64                     @@System
    Upgrade       mutter-42.3-1.fc36.x86_64                                    @updates
    Upgraded      mutter-42.2-1.fc36.x86_64                                    @@System
    Upgrade       openconnect-9.01-2.fc36.x86_64                               @updates
    Upgraded      openconnect-8.20-1.fc36.x86_64                               @@System
    Upgrade       openssl-1:3.0.5-1.fc36.x86_64                                @updates
    Upgraded      openssl-1:3.0.3-1.fc36.x86_64                                @@System
    Upgrade       openssl-devel-1:3.0.5-1.fc36.x86_64                          @updates
    Upgraded      openssl-devel-1:3.0.3-1.fc36.x86_64                          @@System
    Upgrade       openssl-libs-1:3.0.5-1.fc36.i686                             @updates
    Upgraded      openssl-libs-1:3.0.3-1.fc36.i686                             @@System
    Upgrade       openssl-libs-1:3.0.5-1.fc36.x86_64                           @updates
    Upgraded      openssl-libs-1:3.0.3-1.fc36.x86_64                           @@System
    Upgrade       pango-1.50.8-1.fc36.i686                                     @updates
    Upgraded      pango-1.50.7-1.fc36.i686                                     @@System
    Upgrade       pango-1.50.8-1.fc36.x86_64                                   @updates
    Upgraded      pango-1.50.7-1.fc36.x86_64                                   @@System
    Upgrade       pipewire-0.3.54-1.fc36.i686                                  @updates
    Upgraded      pipewire-0.3.53-2.fc36.i686                                  @@System
    Upgrade       pipewire-0.3.54-1.fc36.x86_64                                @updates
    Upgraded      pipewire-0.3.53-2.fc36.x86_64                                @@System
    Upgrade       pipewire-alsa-0.3.54-1.fc36.i686                             @updates
    Upgraded      pipewire-alsa-0.3.53-2.fc36.i686                             @@System
    Upgrade       pipewire-alsa-0.3.54-1.fc36.x86_64                           @updates
    Upgraded      pipewire-alsa-0.3.53-2.fc36.x86_64                           @@System
    Upgrade       pipewire-gstreamer-0.3.54-1.fc36.x86_64                      @updates
    Upgraded      pipewire-gstreamer-0.3.53-2.fc36.x86_64                      @@System
    Upgrade       pipewire-jack-audio-connection-kit-0.3.54-1.fc36.x86_64      @updates
    Upgraded      pipewire-jack-audio-connection-kit-0.3.53-2.fc36.x86_64      @@System
    Upgrade       pipewire-libs-0.3.54-1.fc36.i686                             @updates
    Upgraded      pipewire-libs-0.3.53-2.fc36.i686                             @@System
    Upgrade       pipewire-libs-0.3.54-1.fc36.x86_64                           @updates
    Upgraded      pipewire-libs-0.3.53-2.fc36.x86_64                           @@System
    Upgrade       pipewire-pulseaudio-0.3.54-1.fc36.x86_64                     @updates
    Upgraded      pipewire-pulseaudio-0.3.53-2.fc36.x86_64                     @@System
    Upgrade       pipewire-utils-0.3.54-1.fc36.x86_64                          @updates
    Upgraded      pipewire-utils-0.3.53-2.fc36.x86_64                          @@System
    Upgrade       python3-firewall-1.0.5-2.fc36.noarch                         @updates
    Upgraded      python3-firewall-1.0.4-1.fc36.noarch                         @@System
    Upgrade       sssd-2.7.3-1.fc36.x86_64                                     @updates
    Upgraded      sssd-2.7.1-2.fc36.x86_64                                     @@System
    Upgrade       sssd-ad-2.7.3-1.fc36.x86_64                                  @updates
    Upgraded      sssd-ad-2.7.1-2.fc36.x86_64                                  @@System
    Upgrade       sssd-client-2.7.3-1.fc36.x86_64                              @updates
    Upgraded      sssd-client-2.7.1-2.fc36.x86_64                              @@System
    Upgrade       sssd-common-2.7.3-1.fc36.x86_64                              @updates
    Upgraded      sssd-common-2.7.1-2.fc36.x86_64                              @@System
    Upgrade       sssd-common-pac-2.7.3-1.fc36.x86_64                          @updates
    Upgraded      sssd-common-pac-2.7.1-2.fc36.x86_64                          @@System
    Upgrade       sssd-idp-2.7.3-1.fc36.x86_64                                 @updates
    Upgraded      sssd-idp-2.7.1-2.fc36.x86_64                                 @@System
    Upgrade       sssd-ipa-2.7.3-1.fc36.x86_64                                 @updates
    Upgraded      sssd-ipa-2.7.1-2.fc36.x86_64                                 @@System
    Upgrade       sssd-kcm-2.7.3-1.fc36.x86_64                                 @updates
    Upgraded      sssd-kcm-2.7.1-2.fc36.x86_64                                 @@System
    Upgrade       sssd-krb5-2.7.3-1.fc36.x86_64                                @updates
    Upgraded      sssd-krb5-2.7.1-2.fc36.x86_64                                @@System
    Upgrade       sssd-krb5-common-2.7.3-1.fc36.x86_64                         @updates
    Upgraded      sssd-krb5-common-2.7.1-2.fc36.x86_64                         @@System
    Upgrade       sssd-ldap-2.7.3-1.fc36.x86_64                                @updates
    Upgraded      sssd-ldap-2.7.1-2.fc36.x86_64                                @@System
    Upgrade       sssd-nfs-idmap-2.7.3-1.fc36.x86_64                           @updates
    Upgraded      sssd-nfs-idmap-2.7.1-2.fc36.x86_64                           @@System
    Upgrade       sssd-proxy-2.7.3-1.fc36.x86_64                               @updates
    Upgraded      sssd-proxy-2.7.1-2.fc36.x86_64                               @@System
    Upgrade       webkit2gtk3-2.36.4-1.fc36.x86_64                             @updates
    Upgraded      webkit2gtk3-2.36.3-1.fc36.x86_64                             @@System
    Upgrade       webkit2gtk3-jsc-2.36.4-1.fc36.x86_64                         @updates
    Upgraded      webkit2gtk3-jsc-2.36.3-1.fc36.x86_64                         @@System
    Upgrade       wireplumber-0.4.11-1.fc36.x86_64                             @updates
    Upgraded      wireplumber-0.4.10-1.fc36.x86_64                             @@System
    Upgrade       wireplumber-libs-0.4.11-1.fc36.x86_64                        @updates
    Upgraded      wireplumber-libs-0.4.10-1.fc36.x86_64                        @@System
    Upgrade       xdg-desktop-portal-gnome-42.3-1.fc36.x86_64                  @updates
    Upgraded      xdg-desktop-portal-gnome-42.1-1.fc36.x86_64                  @@System
    Upgrade       unrar-6.1.7-1.fc36.x86_64                                    @rpmfusion-nonfree-updates
    Upgraded      unrar-6.1.6-1.fc36.x86_64                                    @@System
    Reason Change Box2D-2.4.1-7.fc36.x86_64                                    @anaconda
    Removed       kernel-5.18.6-200.fc36.x86_64                                @@System
    Removed       kernel-core-5.18.6-200.fc36.x86_64                           @@System
    Removed       kernel-modules-5.18.6-200.fc36.x86_64                        @@System
    Removed       kernel-modules-extra-5.18.6-200.fc36.x86_64                  @@System
Scriptlet output:
   1 warning: file /lib/modules/5.18.6-200.fc36.x86_64/updates: remove failed: No such file or directory
   2 dkms: running auto installation service for kernel 5.18.10-200.fc36.x86_64
   3  Done. 
   4 dkms: running auto installation service for kernel 5.18.10-200.fc36.x86_64
   5  Done. 

laptop is a 2018 system76 oryx pro (so a clevo P955ER ) 

Please let me know if you need any further info

Источник

Observations about PCIe Bus Error severity Corrected

Handling PCIe Bus Error messages if you can boot in to your Linux system

Further troubleshooting: Disable MSI

Even further troubleshooting: Disable mmconf

Can’t boot! How to edit grub config now?

Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Re: PCIe Bus Error: severity=Corrected, type=Data Link Layer on new Desktop install

Bookmarks

Bookmarks

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://ubuntuforums.org/images/ubuntu-VB4/buttons/collapse_40b.png" alt /> Posting Permissions

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

PCIe Bus error severity=Corrected много-много строк

Posting Permissions