Thank you! "pci=noaer" definitely sweeps this dust under the carpet,
and it would be much better to avoid that.
Narcis (comment #157) reported that "pcie_aspm=off" is a workaround and
is much more specific than "pci=noaer".
If we can collect complete dmesg and "sudo lspci -vv" output when
Hi there !
Same errors are spamming my logs, and my console...
(Nearly) Fresh install on a Ubuntu server 22.04.4 LTS, motherboard Asus Pro
Q670M-C-CSM. Kernel is 5.15.0-97-generic
The "pci=noaer" grub patch does the job, but I’d rather not put the dust under
the carpet ;-)
Output of dmesg and
** Attachment added: "outputs_AER_errors"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+attachment/5751174/+files/outputs_AER_errors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
One more case:
- Hardware: Mainboard "Asus Prime B-560M-A"
- Software: Debian GNU/Linux 11 (bullseye); Kernel Linux 5.10.0-10-amd64
- systemd-journald messages:
Jan 12 09:57:53 system systemd-journald[79944]: Missed 12 kernel messages
░░ Subject: Journal messages have been missed
░░ Defined-By:
** Changed in: linux
Status: Confirmed => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications about this bug
This is the correct patch for the AER message spew.
** Patch removed:
"0001-PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+attachment/5530246/+files/0001-PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch
**
This is the correct patch for the AER message spew.
** Patch added: "0001-PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+attachment/5530246/+files/0001-PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch
--
You
** Patch removed:
"0001-PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+attachment/5529657/+files/0001-PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch
--
You received this bug notification because you are a
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications about this bug go to:
Hello Folks,
As mentioned by Bjorn in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/comments/2
I have been working on a patch for the AER message spew. I have a
potential patch ready for the problem, but unfortunately, I do not have
a system that outputs the same AER errors so I am
I just created the new bug report as suggested, here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error
Launchpad has imported 9 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=109691.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Please create a separate bug report, as the error type is different from
the original report here. Also, in the new report (best upstream), give
more information (firmware version, extension cards, …), and also
*attach* (not paste) the output of `lspci -tvnn` and `sudo lspci
-vvxxx`.
--
You
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
For every one affected, at least attach the output of `lspci -nn`,
`dmesg`, and give details for your system.
As this bug has gotten long, and causes go from firmware, firmware
configuration to hardware issues, it’s better if you opened a separate
report directly upstream, after testing the
Since upgrading from Ubuntu 20.10 to 21.04 I get this message like every
second in journalctl:
Apr 09 13:00:28 tobias-MS-7C37 kernel: pcieport :00:03.1: AER: Multiple
Corrected error received: :00:00.0
Apr 09 13:00:28 tobias-MS-7C37 kernel: pcieport :00:03.1: PCIe Bus Error:
** Changed in: linux
Status: Unknown => Confirmed
** Changed in: linux
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error
Hello to all. I have the same problem, and this has affected me for a
long time now. I described it in detail here, with output, videos,
photos etc:
https://ubuntuforums.org/showthread.php?t=2460318
I hope this adds useful information to draw attention to the bug in
question.
--
You received
Seen this as well -- although I don't believe it's causing any
problems that we know of -- sure does look right now like it's
only noise in the logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also tried all LTS Ubuntus back to 16.04. They all get this log
message a lot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage
I have this same problem on a Dell XPS 13 9360 that shipped with Ubuntu
16.04 preloaded. My dmesg logs look identical to what I am seeing above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
And FWIW, I have fully upgraded all firmware and also tried both Ubuntu
20.10 and Fedora 33. All of these systems show the same behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
Still an issue for me on Ubuntu 20.10 "Groovy".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications about this bug go to:
"me too" - Dell Latitude w/ a Dell WD16 USB-C dock. After recent
firmware updates it got significantly worse and nearly never properly
re-attaches after suspend/resume.
Dell 5400 Latitude:
(0.1.9.1=same, 0.1.7.4=older, 0.1.6.5=older, 0.1.5.1=older, 0.1.4.2=older)
dock:
```
No upgrades for
This bug still affect the install process today, with ubuntu 20.04 LTS
and same with kubuntu installer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received:
@piscvau, the original report is not about a crash, so your issue is
unrelated. Please create a separate report for the crash Ubuntu 20.04.
(Also mention there, if it is a system crash/hang? Does the numlock key
still work? Can you switch to a virtual console with Ctrl + Alt + F4?
Can you still
on PC MSI GE73, installation of Xubuntu 18.04 fails,as well as XUBUNTU 19.10.
PC was returned to MSI under warranty. Hardware is correct and no problem with
windows.
WIth the latest BIOS it is now impossible to boot the PC with an ISO USB key
for version 18.04 and 19.10.
WIth XUBUNTU 20.04 the
my investigation came to same conclusion as #109 (but I'm on 20.04 and
latest kernel, so this is still relevant)
My configuration is as follows.
It there is a need to get more information/logs, please let me know.
--
Dell Latitude 7389
miki@DL-7389:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
@magean, I believe you are having a different issue here, so please
create a separate bug report, and, as you reproduced this with Linux 5.4
(also try https://kernel.ubuntu.com/~kernel-ppa/), contact linux-
p...@vger.kernel.org and the PCI subsystem maintainers directly, and
attach `dmesg` to your
So, although `pci=nommconf` gets rid of the error flood, it does
apparently make some collateral damage. After a few days under this
kernel parameter, the person who uses the laptop on a daily basis
reported a decrease in responsiveness and stability, with occasional
stutters if I understood
I've been getting a similar problem on a Leopard GP73-8RE laptop from
MSI, on Ubuntu 20.04 as well as 19.10 and 18.04.
This is the message that spammed in my system journal, causing it to
inflate very rapidly to ludicrous proportions:
22:36:51 kernel: alx :03:00.0: AER:[ 7] BadDLLP
Hi, Dell G3 3579 (086F)
Ubuntu 20.04
LOG:
[72720.138307] pcieport :00:1d.6: AER: PCIe Bus Error: severity=Corrected,
type=Data Link Layer, (Transmitter ID)
[72720.138314] pcieport :00:1d.6: AER: device [8086:a336] error
status/mask=1000/2000
[72720.138320] pcieport
Dell Inspiron P74G, Kubuntu 19.04 Disco, kernel 5.0.0-13-generic.
I'm affected as well by this bug, with ~50 lines per minute of errors in
the syslog.
I noticed only recently the issue on my Kubuntu 18.04 LTS setup (say,
this October 2019). Since then I upgraded to 19.04, but with no
I have similar problem, but I got "Timeout"
ACER Nitro 5 - Ubuntu 19.04 fresh install.
Intel(R) Core(TM) i7-8750H
Spamming in few minutes the following (on example):
Sep 25 03:09:06 mark-Nitro-AN515-52 kernel: [ 4326.007230] pcieport
:00:1d.5: AER: Corrected error received: :00:1d.5
Sep
I am getting the same issue with Ubuntu 19.04.
I am using HP Probook 440G3 having i7-6500U processor and RTL8723BE network
card.
Any ideas on when this issue is planned to be patched?
Getting this info from Windows counterpart, as I am still getting issues
after applying nomsi
Name
Seeing this on Linux LAPTOP 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu
Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux, running xubuntu
18.04.3.
description: Notebook
product: Aspire A315-53 ()
vendor: Acer
*-pci
description: Host bridge
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications about this bug go to:
I've got the same using archlinux latest kernel with a dell computer, i7
and an pcie network card as well. I've found this thread on redhat
bugzilla very helpful:
https://bugzilla.redhat.com/show_bug.cgi?id=681017
I was able to solve my problem by explicitly disabling aspm in my bios.
>From
I have experienced the same bug on my laptop HP - Pavilion and I think the
problem is in compatibility between Wireless Card RTL8723BE PCIe and the
linux kernal
causing it to infinitely log a PCIe Error on every boot/reboot of the system
which cause a huge log files size on the disk!
I 'm
I get the pcie errors on all X,L,K Ubuntu's disco 19.04
[ 3056.549121] pcieport :00:1c.0: AER: Corrected error received:
:00:1c.0
[ 3056.549136] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected,
type=Data Link Layer, (Transmitter ID)
[ 3056.549147] pcieport :00:1c.0:
I am seeing this on an updated Cosmic with a Dell Inspiron 5570. Kernel
version is presently 4.18.0-15.16.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error
I'm also experiencing this bug with the latest debian testing release:
Linux lemon 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 (2018-12-22) x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm still having this issue with my Dell Inspiron 5570 and a Ubuntu 18.04 fully
updated install.
I had this issue since i bought it (6 months ago), but now its even worse.
Right now my wifi keeps disconnecting and a hard reboot is required to make it
work again.
Also, the wifi icon on the top
This is also present in later distro versions, right up to Cosmic.
In my case it manifests on Supermicro and Intel 7500/5500/5520/X58 -
based servers when Qlogic QLE2562 fibre optic cards are used - and
_ONLY_ with Qlogic cards, nothing else seems to trigger it
As with the wifi cards on laptops,
The mainline kernel is now at v4.19-rc6. It might be worth testing this
kernel to see if the bug has been fixed upstream. It can be downloaded
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Reverting to Triaged on the Ubuntu task, Also making clear there is a
workaround (pci=noaer) for it.
** Changed in: linux (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Note: Current workaround is to add pci=noaer to your kernel command
- line:
+ WORKAROUND: 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:
+ 1)
*First linux bug report*
I am also affected by this issue Bionic: 4.15.0-33 on a Dell Aurora R6
Processor is i7-7700K Kabylake getting the issue with the PCI bus
connected to Intel Corporation Wireless 3165 card.
I see someone said a fix is in place, but cannot find where the fix has
been
I'm also having this issue on my Dell Inspiron 14 7472.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename: bionic
$ uname -a
Linux bionic 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018
I have the same issue in mey dell inspiron 5378 i7.
lspci -vt
-[:00]-+-00.0 Intel Corporation Device 5904
+-02.0 Intel Corporation Device 5916
+-04.0 Intel Corporation Skylake Processor Thermal Subsystem
+-13.0 Intel Corporation Device 9d35
I'm in Xenial : Linux 4.15.0-29-generic #31~16.04.1-Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications about this
I have a Dell Inspiron 5570 with Intel i7-8550U CPU. I face the same
problem with the Ubuntu 16.04 OEM install and a fresh Kubuntu 18.04
install.
22/7/18 3:01 Μ.Μ. kernel pcieport :00:1c.5: AER: Corrected error
received: id=00e5
22/7/18 3:01 Μ.Μ. kernel pcieport :00:1c.5:
the initial error report is(several log messages dmesg):
[ 13.078695] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected,
type=Data Link Layer, id=00e4(Transmitter ID)
[ 13.078697] pcieport :00:1c.4: device [8086:9d14] error
status/mask=1000/2000
[ 13.078698] pcieport
Let me tell my history:
I bought a dell inspiron 7000 series with windows 10.
Replaced by ubuntu 18.04
I make some bios upgrades. my actual bios is the newer.
One day i opened my notebook and do a ssd upgrade.
My error was to unplug the battery because one pin twisted.
I noticed in ubuntu
Just an update with this. I tried with fedora rawhide with 4.18 kernel
and Ubuntu daily cosmic cuttlefish and the issue is present there too.
I am unable to change the status of this bug back to confirmed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is not fixed for me. Asus x541u
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications about this bug go to:
Where is this fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications
I have the same problem in my computer since I upgrade the last linux
kernel 4.4.0-128-generic, and my sound card can not work as usual.
Jun 18 01:48:00 home kernel: [ 353.142183] pcieport :00:1c.0: AER:
Corrected error received: id=00e0
Jun 18 01:48:00 home kernel: [ 353.142194] pcieport
What is the current status of this issue?
I am facing it on my MSI laptop and I'm not sure if disabling interrupts or
turning off active-state power management is the right solution?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications
I have this error on my Asus X541U, with Ubuntu 18.04, please solve it.
It generates an endless list with this error:
PCIe Bus Error: severity=Corrected, type=Physical Layer,
id=00e5(Receiver ID) device [8086:9d15] error status/mask=0001/2000
And I can't log in.
And it is related to
I can confirm similar issues on AMD Threadripper.
The issues went away on Ubuntu 17.10 by adding "pci_aspm=off" to grub,
but are re-introduced by upgrading to 18.04. Strangely, the error now
occurs in both 4.13 and 4.15 kernels.
One solution I found is to set PCIe to 2.0 instead of the default
I too like Thorsten have a Ryzen workstation, and incidentally the same
network chipset but a different motherboard (asrock ab350m pro4)
1f:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
I think this error message is generic
I had the same problem and fix #9 worked for me (adding "pci=noaer").
I'm on Ubuntu 17.10 on a HP Pavilion laptop 14-008nf and all hardware seems to
be working.
I was flooded with this(took lots of disk space cause logging constantly):
akem@akem-HP-Pavilion-Notebook:~$ tail /var/log/syslog
Mar
I had same messages, to get hide it I use Fastboot and pcie_aspm=off. I
think this only hide the messages, WiFi works correctly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER:
Still present in (X)ubuntu 17.10 with kernel 4.13.0-32-generic.
The trigger is the onboard Realtek network chip on my Gigabyte GA-AB350
Gaming 3 (AMD Ryzen) mainboard:
+-01.3-[01-05]--+-00.0 Advanced Micro Devices, Inc. [AMD] USB 3.1 XHCI
Controller
| +-00.1 Advanced
I noticed weird network problems on this system aswell, when plugging in
a USB3 external harddisk and on Friday even when I just plugged in my
mobile phone just to load the battery.
Don't know if this is connected in some way. Yesterday I updated the
UEFI/BIOS and will watch if this is still
I'm not seeing this spammed in dmesg. Only maybe once per boot, but I'm
seeing the following on my 9360 running Ubuntu 17.10:
[ 4649.396767] pcieport :00:1c.4: AER: Corrected error received: id=00e4
[ 4649.396784] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected,
type=Data Link
Setting "Fastboot" to "Through" in the BIOS (v2.4.2) of my XPS 13 9360
fixed this error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To
@Bougron did you register new bug? Failed to find new one... If
registered, could you pls share new number?
Got new laptop, seems that I'm having the same issue.
Nov 22 10:05:50 tower9-xps15 kernel: [ 110.580978] pcieport :00:1d.0: AER:
Corrected error received: id=00e8
Nov 22 10:05:50
Sorry not enough coffee in a morning. ps output was meant for frozen
kernel update...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage
Bougron, please file a new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications about this bug go to:
Sorry
I saw this
** Attachment added: "trace.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+attachment/5012138/+files/trace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
hello
Today, I have seem this 4 lines repeadedmany many times in a syslog trace
of ubuntu 17.10
Nov 20 00:07:53 sat-XPS-15-9560 kernel: [ 590.905484] pcieport :00:1c.0:
AER: Corrected error received: id=00e0
Nov 20 00:07:53 sat-XPS-15-9560 kernel: [ 590.905513] pcieport :00:1c.0:
Marcos,
#68
Regardless of fastboot on/off I get the same behavior without
pcie_aspm=off
➜ ~ uname -r
4.13.0-16-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER:
Hi Marcos, I was getting this error on a Precision 5520 when I plugged a
TB16 docking station. I am running Xubuntu 16.04 fully updated. No
peripheral was functional.
After setting the fast boot option to Auto, it worked!
Cheers...
--
You received this bug notification because you are a member
I entered on BIOS and set the option "Fastboot" to "through". I would
like people check what value is selected for this option and change to
check if error persists. Some people could help me on that?
On Fri, Nov 10, 2017 at 10:37 AM, Sasha Stadnik
<1521...@bugs.launchpad.net> wrote:
> I had the
I had the same problem on Linux Lubuntu 17.10 (4.13.0-16-generic)
Asus X550VXK Intel i7, Nvidia Geforce GTX 950M
First at all i had black screen, temporary added "nomodeset" to grub
menu solved it.
pci=noaer helped me to get rid of "PCIe Bus Error: severity=Corrected,
type=Physical Layer"
After
> On 7 Nov 2017, at 1:07 AM, Jinyu LIU <1521...@bugs.launchpad.net> wrote:
>
> I got same issue with DELL XPS
Jinyu LIU,
Can you file a new bug? Thanks.
Kai-Heng
>
> * Ubuntu 17.10
> * Linux SimonUbuntu 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC
> 2017 x86_64 x86_64 x86_64
I got same issue with DELL XPS
* Ubuntu 17.10
* Linux SimonUbuntu 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
* syslog
Nov 7 00:59:08 SimonUbuntu kernel: [ 1701.635733] pcieport :00:1c.2: AER:
Corrected error received: id=00e2
Nov 7
This message just occurs to me when I set the "Fastboot" option on BIOS
to "Minimal" instead of "Through". I think the Linux isn't ready yet for
Fastboot feature.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm using Ubuntu 17.10 on a i7 Skylake and using the "pci=noaer"tip the
message goes away. Now I need to find out what this option means to see
if I'm losing something.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same issue on Linux Ubuntu Server 16.04
Intel Skylake i5-6400
Asus Motherboard Z270 Prime
GPU on PCIe MSI RX 580
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error
Still same here. Updated from 17.04 to 17.10:
pcieport :00:1c.5: AER: Corrected error received: id=00e5
pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Data Link
Layer, id=00e5(Transmitter ID)
pcieport :00:1c.5: device [8086:9d15] error status/mask=1000/2000
[ 6283.204650] pcieport :00:1c.4: AER: Corrected error received: id=00e4
[ 6283.204661] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected,
type=Data Link Layer, id=00e4(Transmitter ID)
[ 6283.204671] pcieport :00:1c.4: device [8086:9d14] error
status/mask=1000/2000
[
Just now experiencing this on Ubuntu 17.10. Never saw this before.
Dell XPS 13 DE 9360 w/ Kabylake CPU.
** Tags added: artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER:
I just wanted to report that I am on Asus X550V (Skylake i7-7700HQ Cpu
with Nividia GeForce GTX 950M) and your workaround in first paragraph
worked:
"Note: 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
Hit by this today after updating packages on ubuntu 17.10 running on dell 9360.
This upgraded the kernel to '4.13.0-11-generic #12-Ubuntu SMP'
The same pcieport messages as dan-mulholland was seeing.
[ 1423.748011] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected,
type=Data Link Layer,
Still happening with Ubuntu 17.10 kernel Linux P01A30136
4.12.0-12-generic #13-Ubuntu SMP Thu Aug 17 16:13:25 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux and updated BIOS.
Aug 28 10:55:08 LAPTOPNAME kernel: [ 5632.967441] pcieport :00:1c.5: AER:
Corrected error received: id=00e5
Aug 28 10:55:08
Also affecting me on Ubuntu 14.04 Asus UX305CA.
Could this be the reason my computer could not resume from suspend
anymore?
After a very recent system update my computer never resumed fully from
suspend and after a hard restart I got an apportcheckresume error. Only
thing I could notice was the
I have the same issue on Asus x550vx laptop {with Nividia GTX950M}
i7-7700HQ quad-core on Ubuntu 16.04.3 linux kernel 4.10.0-32-generic:
Aug 21 07:45:05 kernel: [170968.303385] pcieport :00:1c.2: AER: Multiple
Corrected error received: id=00e2
Aug 21 07:45:05 kernel: [170968.304027]
I have experienced the same issue.
Linux kernel 4.12 (easily installed using Ukuu
http://www.omgubuntu.co.uk/2017/02/ukuu-easy-way-to-install-mainline-kernel-ubuntu)
completely resolved this issue with the PCIe bus for me.
On Fri, Jul 21, 2017 at 8:26 PM, Stephan Ruegamer <
Just saw this message the first time:
Ubuntu Artful (Devel) latest packages.
Jul 21 10:15:18 sruegamer-xps13 kernel: [ 3949.594315] pcieport :00:1c.4:
PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter
ID)
Jul 21 10:15:18 sruegamer-xps13 kernel: [ 3949.594323]
Follow-up: Errors disappeared only for a few reboots. First only a
subset of errors, today all of the previously observed error messages
appeared again during boot up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have an ASUS N552VW laptop for which updating BIOS to 300 had helped
to solve this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To
FWIW, running Kubuntu 17.04 with kernel 4.12.0-041200rc4-generic on a
Dell XPS 9360 (late 2016) model, I get this error:
9825.550655] pcieport :00:1c.4: AER: Corrected error received: id=00e4
[ 9825.550661] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected,
type=Data Link Layer,
Note: before doing the workaround, my Realtek 8821AE wifi module did
work and would connect to the network, despite the high rate of errors
going to the log. After implementing the workaround, no more errors but
the wifi doesn't work (it can see the network but won't connect to it).
--
You
Same problem here. Both Ubuntu Desktop 16.04, and 17.04 with kernel
4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
This is on i7-6700TE @ 2.4GHz, 32 GB RAM, 500 GB SSD with Nvidia GeForce GT710
video card and Realtek 8821AE PCI-E wireless adaptor.
The
1 - 100 of 151 matches
Mail list logo
