PCIe Bus Error Ubuntu 16.04
I bought recently a computer and installed ubuntu but get this error when ubuntu is booting
[ 91.167119] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[ 91.167122] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 91.167130] pcieport 0000:00:1c.0: [ 0] Receiver Error (First)
What is it?
is It bad?
How to fix it?
boot 16.04
edited May 3 '17 at 4:40
Ravexina
32.6k1487113
asked May 3 '17 at 3:33
Beto TeBeto Te
1112
add a comment |
I bought recently a computer and installed ubuntu but get this error when ubuntu is booting
[ 91.167119] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[ 91.167122] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 91.167130] pcieport 0000:00:1c.0: [ 0] Receiver Error (First)
What is it?
is It bad?
How to fix it?
boot 16.04
edited May 3 '17 at 4:40
Ravexina
32.6k1487113
asked May 3 '17 at 3:33
Beto TeBeto Te
1112
You might try alspcicommand interminalto see if you can identify what device is throwing the error. Look for device00:1c.0.
– heynnema
May 3 '17 at 14:10
add a comment |
I bought recently a computer and installed ubuntu but get this error when ubuntu is booting
[ 91.167119] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[ 91.167122] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 91.167130] pcieport 0000:00:1c.0: [ 0] Receiver Error (First)
What is it?
is It bad?
How to fix it?
boot 16.04
edited May 3 '17 at 4:40
Ravexina
32.6k1487113
asked May 3 '17 at 3:33
Beto TeBeto Te
1112
I bought recently a computer and installed ubuntu but get this error when ubuntu is booting
[ 91.167119] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[ 91.167122] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 91.167130] pcieport 0000:00:1c.0: [ 0] Receiver Error (First)
What is it?
is It bad?
How to fix it?
boot 16.04
boot 16.04
edited May 3 '17 at 4:40
Ravexina
32.6k1487113
asked May 3 '17 at 3:33
Beto TeBeto Te
1112
edited May 3 '17 at 4:40
Ravexina
32.6k1487113
asked May 3 '17 at 3:33
Beto TeBeto Te
1112
edited May 3 '17 at 4:40
Ravexina
32.6k1487113
edited May 3 '17 at 4:40
Ravexina
32.6k1487113
edited May 3 '17 at 4:40
Ravexina
32.6k1487113
32.6k1487113
asked May 3 '17 at 3:33
Beto TeBeto Te
1112
asked May 3 '17 at 3:33
Beto TeBeto Te
1112
asked May 3 '17 at 3:33
Beto TeBeto Te
1112
1112
You might try alspcicommand interminalto see if you can identify what device is throwing the error. Look for device00:1c.0.
– heynnema
May 3 '17 at 14:10
add a comment |
You might try alspcicommand interminalto see if you can identify what device is throwing the error. Look for device00:1c.0.
– heynnema
May 3 '17 at 14:10
You might try a
lspci command in terminal to see if you can identify what device is throwing the error. Look for device 00:1c.0.– heynnema
May 3 '17 at 14:10
You might try a
lspci command in terminal to see if you can identify what device is throwing the error. Look for device 00:1c.0.– heynnema
May 3 '17 at 14:10
add a comment |
2 Answers
2
active
oldest
votes
I had the same PCIe BusError messages in boot and spamming my logs on Asus x550v (Skylake cpu).
Try this:
Current workaround is to add pci=noaer to your kernel command line:
1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
2) run sudo update-grub
3) reboot
from Workaround here
note: If pci=noaer doesnt work try use pci-nomsi instead.
answered Sep 29 '17 at 11:38
jon anotter88998889jon anotter88998889
344
add a comment |
Try this steps:
cp /etc/default/grub ~/Desktop
Edit grub. Add
pci=noaerat the end ofGRUB_CMDLINE_LINUX_DEFAULT.
Line will be like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
sudo cp ~/Desktop/grub /etc/default/sudo update-grubReboot now
:) Enjoy.
answered May 28 '18 at 2:29
EhteshamEhtesham
414
1
This is a duplicate of the other answer
– stumblebee
May 28 '18 at 3:14
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f911296%2fpcie-bus-error-ubuntu-16-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had the same PCIe BusError messages in boot and spamming my logs on Asus x550v (Skylake cpu).
Try this:
Current workaround is to add pci=noaer to your kernel command line:
1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
2) run sudo update-grub
3) reboot
from Workaround here
note: If pci=noaer doesnt work try use pci-nomsi instead.
answered Sep 29 '17 at 11:38
jon anotter88998889jon anotter88998889
344
add a comment |
I had the same PCIe BusError messages in boot and spamming my logs on Asus x550v (Skylake cpu).
Try this:
Current workaround is to add pci=noaer to your kernel command line:
1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
2) run sudo update-grub
3) reboot
from Workaround here
note: If pci=noaer doesnt work try use pci-nomsi instead.
answered Sep 29 '17 at 11:38
jon anotter88998889jon anotter88998889
344
add a comment |
I had the same PCIe BusError messages in boot and spamming my logs on Asus x550v (Skylake cpu).
Try this:
Current workaround is to add pci=noaer to your kernel command line:
1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
2) run sudo update-grub
3) reboot
from Workaround here
note: If pci=noaer doesnt work try use pci-nomsi instead.
answered Sep 29 '17 at 11:38
jon anotter88998889jon anotter88998889
344
I had the same PCIe BusError messages in boot and spamming my logs on Asus x550v (Skylake cpu).
Try this:
Current workaround is to add pci=noaer to your kernel command line:
1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
2) run sudo update-grub
3) reboot
from Workaround here
note: If pci=noaer doesnt work try use pci-nomsi instead.
answered Sep 29 '17 at 11:38
jon anotter88998889jon anotter88998889
344
answered Sep 29 '17 at 11:38
jon anotter88998889jon anotter88998889
344
answered Sep 29 '17 at 11:38
jon anotter88998889jon anotter88998889
344
answered Sep 29 '17 at 11:38
jon anotter88998889jon anotter88998889
344
344
add a comment |
add a comment |
Try this steps:
cp /etc/default/grub ~/Desktop
Edit grub. Add
pci=noaerat the end ofGRUB_CMDLINE_LINUX_DEFAULT.
Line will be like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
sudo cp ~/Desktop/grub /etc/default/sudo update-grubReboot now
:) Enjoy.
answered May 28 '18 at 2:29
EhteshamEhtesham
414
1
This is a duplicate of the other answer
– stumblebee
May 28 '18 at 3:14
add a comment |
Try this steps:
cp /etc/default/grub ~/Desktop
Edit grub. Add
pci=noaerat the end ofGRUB_CMDLINE_LINUX_DEFAULT.
Line will be like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
sudo cp ~/Desktop/grub /etc/default/sudo update-grubReboot now
:) Enjoy.
answered May 28 '18 at 2:29
EhteshamEhtesham
414
1
This is a duplicate of the other answer
– stumblebee
May 28 '18 at 3:14
add a comment |
Try this steps:
cp /etc/default/grub ~/Desktop
Edit grub. Add
pci=noaerat the end ofGRUB_CMDLINE_LINUX_DEFAULT.
Line will be like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
sudo cp ~/Desktop/grub /etc/default/sudo update-grubReboot now
:) Enjoy.
answered May 28 '18 at 2:29
EhteshamEhtesham
414
Try this steps:
cp /etc/default/grub ~/Desktop
Edit grub. Add
pci=noaerat the end ofGRUB_CMDLINE_LINUX_DEFAULT.
Line will be like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
sudo cp ~/Desktop/grub /etc/default/sudo update-grubReboot now
:) Enjoy.
answered May 28 '18 at 2:29
EhteshamEhtesham
414
edited May 30 '18 at 6:17
answered May 28 '18 at 2:29
EhteshamEhtesham
414
answered May 28 '18 at 2:29
EhteshamEhtesham
414
answered May 28 '18 at 2:29
EhteshamEhtesham
414
414
1
This is a duplicate of the other answer
– stumblebee
May 28 '18 at 3:14
add a comment |
1
This is a duplicate of the other answer
– stumblebee
May 28 '18 at 3:14
1
1
This is a duplicate of the other answer
– stumblebee
May 28 '18 at 3:14
This is a duplicate of the other answer
– stumblebee
May 28 '18 at 3:14
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f911296%2fpcie-bus-error-ubuntu-16-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You might try a
lspcicommand interminalto see if you can identify what device is throwing the error. Look for device00:1c.0.– heynnema
May 3 '17 at 14:10