Pci bus error linux

PCIe Bus Error

Поставил на ноут ArchLinux.

При включении wifi в лог сыпет сообщения в огромном количестве

как это исправить? Wifi лагает просто безбожно. Спасибо.

Разбирал? На других версиях ядра как?

ноут новый, на других ядрах не пробовал

в dmesg валится вот это

Добавить в параметр загрузки ядра

Но ведь это не решение.

Хех, знать бы ещё производителя и наименования моделей микросхем. На что ты надеялся? Применённый тобой хак может на время скрыть проблему, но высокой ценой. Хотя это всё не важно, в любом случае наиболее адекватным (и эффективным) решением тут будет купить нормальный лаптоп.

чем мой то ненормальный? Под окнами проблем нет

исходя из логов, драйвер hotplug пытается найти какой то девайс и собсна не может, какой я так и не понял

nomsi для всех pci устройств — это глупо

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

noaer это тоже глупо, aer — advanced error reporting, отключать его, всё равно, что разбивать градусник при болезни.

попробуй например pci=pcie_bus_safe
или там pcie_pme=nomsi или pcie_hp=nomsi

тут много всякого

исходя из логов, драйвер hotplug пытается найти какой то девайс и собсна не может, какой я так и не понял

приведи весь dmesg.
почему хотплаг? можно включать во время работы?

Источник

Ошибки PCIe Bus Error: severity=Corrected при выключении в Linux

После обновления 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:

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

Читайте также:  Python ctrl break exception

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

Источник

Troubleshooting PCIe Bus Error severity Corrected on Ubuntu and Linux Mint

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:

Now open the file with Gedit for editing:

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:

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

Читайте также:  System service exception windows 10 причина igdkmd64 system

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:

Update grub and reboot the system:

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:

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.

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:

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

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.

Источник

PCIe Bus error severity=Corrected

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)

Читайте также:  What is api call error

3 Answers 3

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

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

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 )

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

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

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.

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.

Источник

Ubuntu 20.04 PCIe Bus error severity=corrected

I have a problem with new ubuntu, after suspend i always crash and i need to reboot system

my kernel parameters «quiet splash pci=noaer pci=noamsi»

1 Answer 1

Incomplete answer. edits forthcoming.

nomsi

In your GRUB edits, pci=noamsi should be pci=nomsi . but we’ll temporarily remove both pci= statements for now.

BIOS

You have BIOS version F.53.

To determine if there’s a newer BIOS, I need the exact make/model # of your computer.

vm.swappiness

With only 8G RAM and 4G swap, vm.swappiness=10 is totally wrong.

Set vm.swappiness=60 (based on 8G RAM and 4G SWAP), this way.

sudo -H gedit /etc/sysctl.conf # edit this file

Search for an existing vm.swappiness= entry.

CTRL + f vm.swappiness

If found, edit it to say vm.swappiness=60

If not found, add vm.swappiness=60 at the end of the file

Save your edits and quit gedit

AER errors

AER errors are Advanced Error Reporting correctable errors on the PCIe bus.

From the initial information available, it appears that it might be this device:

Do you recognize this device? Is it your NVMe SSD? Is this a laptop or desktop computer?

We MAY end up putting pci=noaer in your GRUB to circumvent these errors, but more information is required.

Источник

Smartadm.ru
Adblock
detector