AER: Corrected error received: id=00e0

Bug #1521173 reported by David Henningsson
706
This bug affects 147 people
Affects Status Importance Assigned to Milestone
Linux
Unknown
Medium
linux (Ubuntu)
Medium
Unassigned
Xenial
Medium
Unassigned

Bug Description

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:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
2) run "sudo update-grub"
3) reboot

----

My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot.

[ 5315.986588] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[ 5315.987249] pcieport 0000:00:1c.0: can't find device of ID00e0
[ 5315.995632] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[ 5315.995664] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[ 5315.995674] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 5315.995683] pcieport 0000:00:1c.0: [ 0] Receiver Error
[ 5316.002772] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[ 5316.002811] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[ 5316.002826] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 5316.002838] pcieport 0000:00:1c.0: [ 0] Receiver Error
[ 5316.009926] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[ 5316.009964] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[ 5316.009979] pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00000001/00002000
[ 5316.009991] pcieport 0000:00:1c.0: [ 0] Receiver Error

ProblemType: BugDistroRelease: Ubuntu 16.04
Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic]
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio
 /dev/snd/controlC0: david 1502 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Nov 30 13:19:00 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
InstallationDate: Installed on 2015-11-28 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
MachineType: Dell Inc. Inspiron 13-7359
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-19-generic N/A
 linux-backports-modules-4.2.0-19-generic N/A
 linux-firmware 1.153SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.00.00
dmi.board.name: 0NT3WX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 13-7359
dmi.sys.vendor: Dell Inc.

Revision history for this message
David Henningsson (diwic) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc3-wily

tags: added: kernel-da-key
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
David Henningsson (diwic) wrote :

I've tried upgrading BIOS to 1.2.0 (latest version on Dell website) and also with the v4.4-rc3-wily kernel. The dmesg is still spammed with the same error.

tags: added: kernel-bug-exists-upstream
tags: added: bios-outdated-1.2.0
tags: added: latest-bios-1.2.0
removed: bios-outdated-1.2.0
Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

David Henningsson, pending you've already tested and reproduced in 4.4-rc4, the issue you are reporting is an upstream one. Could you please report this upstream (TO Bjorn Helgaas CC linux-pci) via https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Also, could you quantify your description comment "My dmesg gets completely spammed with the following messages appearing over and over again."?

For example, it increases the log file size by 1MB per hour in comparison to when this doesn't happen?

Thank you for your understanding.

tags: added: kernel-bug-exists-upstream-4.4-rc3
Changed in linux (Ubuntu Xenial):
status: Confirmed → Triaged
Revision history for this message
David Henningsson (diwic) wrote :

The spam rate is 150 lines per second. With ~80 characters per line, that's about 50 MB per hour. As a very rough measure.

122 comments hidden view all 156 comments
Revision history for this message
In , cspadijer (cspadijer-linux-kernel-bugs) wrote :

Created attachment 197891
Collection of outputs from X555U laptop

Good day.
I have updated this laptop to the latest vendor supplied BIOS 204 10/18/2015.

Attempted distribution: Ubuntu mate 15.10.
Had to use acpi=off boot parameter to install linux
Eventually found more hardware worked with the pci=nommconf boot parameter

With pci=nommconf the following still does not work:
- Realtec rtl8821ae 802.11ac wireless NIC PCIe will only run in 2.4GHz mode. 5GHz mode will not work.
- Laptop will not resume after suspend

Many boot errors show in dmesg:
ACPI: AE_NOT_FOUND errors
systemd: failed to insert module 'kdbus' function not implemented

If pci=nommconf not used as boot parameter there is a looping pci-e error message that I cant break out of. From what I can read it says:
printk messages dropped pcieport 0000:00:... id=00E5(Receiver ID)

In the attached file is the following when pci=nommconf boot parameter used:
sudo output of:
dmesg
uname -a
lspci -vvnn
dmidecode
Tarball of /proc/acpi directory

Note: I am unable to resume from hibernate everything is frozen. So I am not able to attach a copy of /var/log/kern.log.0

121 comments hidden view all 156 comments
Revision history for this message
Beanow (beanow) wrote :

Confirming same error messages on 4.2.0 kernel from jessie-backports with skylake i7-6700HQ. On pci port 0:1c:0, device ID [8086:a110].

According to lspci -tv this is connected to my Intel 3165 wireless card. Using a manually added ucode from https://wireless.kernel.org/en/users/Drivers/iwlwifi

Can you check with lspci -tv what device is connected to this pci slot?

Revision history for this message
Beanow (beanow) wrote :

Found in your udev file that your slot that triggers the messages is also a wifi card. Realtek, RLT8723BE PCIe Wireless Network Adapter.

So the common ground seems to be. 4.x kernel versions. PCIe wireless cards. Intel PCIe bus. Skylake CPU series laptop.

121 comments hidden view all 156 comments
Revision history for this message
In , rui.zhang (rui.zhang-linux-kernel-bugs) wrote :

There are a couple of problems here
1. "pci=nommconf" is needed to boot
2. tpm_crb driver calltrace in dmesg
3. ieee80211_tx calltrace in dmesg
4. hibernate failure

IMO, any of the first three problems may break hibernation, thus we should try to fix the first three issues separately and then check how hibernation goes on this laptop.

Move to PCI category to get Problem 1 fixed first.

Revision history for this message
In , bjorn (bjorn-linux-kernel-bugs) wrote :

Thank you very much for this report. It's a pretty serious problem when we can't boot at all.

"pcieport 0000:00:... id=00E5(Receiver ID)" looks like an AER message. Please try turning off AER with "pci=noaer". If you can boot with "pci=noaer" and without "pci=nommconf", please attach the dmesg log.

Here's a report of another similar AER problem:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173

Revision history for this message
In , cspadijer (cspadijer-linux-kernel-bugs) wrote :

Created attachment 198481
Updated dmesg with pci=noaer

It booted no problem after replacing pci=nommconf with pci=noaer as suggested. See updated dmesg.txt as requested.

Thanks!

122 comments hidden view all 156 comments
Revision history for this message
David Henningsson (diwic) wrote : Re: Dmesg filled with "AER: Corrected error received"

Hi,

Indeed booting with pci=noaer (as suggested in the other bug) works
around this issue as well. I'll use that for the time being.

Thanks for working on it!

// David

On 2015-12-29 16:58, Bjorn Helgaas wrote:
> On Fri, Dec 18, 2015 at 11:30:33AM +0100, David Henningsson wrote:
>> Hi Linux PCI maintainers,
>>
>> My dmesg gets filled with a few lines repeated over and over again:
>>
>> pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
>> pcieport 0000:00:1c.0: can't find device of ID00e0
>> pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
>> pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected,
>> type=Physical Layer, id=00e0(Receiver ID)
>> pcieport 0000:00:1c.0: device [8086:9d14] error
>> status/mask=00000001/00002000
>> pcieport 0000:00:1c.0: [ 0] Receiver Error
>>
>> This happens 10-30 times per second (!), so dmesg fills up quickly.
>> The bug is present in both vanilla and Ubuntu kernels.
>
> This is a pretty obvious bug in our AER code. We normally clear
> correctable errors by writing the PCI_ERR_COR_STATUS register in
> handle_error_source(). The execution path looks like this:
>
> aer_isr_one_error
> aer_print_port_info
> if (find_source_device())
> aer_process_err_devices
> handle_error_source
> pci_write_config_dword(dev, PCI_ERR_COR_STATUS, ...)
>
> In this case, find_source_device() printed "can't find device of
> ID00e0" [sic] and returned false, so we don't call
> aer_process_err_devices(). The error is never cleared, so
> we discover it again and again.
>
> I'll work on fixing this. Incidentally, there's another report
> with similar symptoms here:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=109691
>
> Bjorn
>

--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

123 comments hidden view all 156 comments
Revision history for this message
In , bjorn (bjorn-linux-kernel-bugs) wrote :

Great, thank you! I understand the AER bug (see http://lkml.kernel.org/r/20151229155822.GA17321@localhost); now we just need to figure out a fix.

Revision history for this message
In , cspadijer (cspadijer-linux-kernel-bugs) wrote :

Excellent.
Thanks Bjorn.
Great to see you have isolated the problem.

All the best in 2016!

Any other details you require from me let me know I will update this post.

Cheers!

123 comments hidden view all 156 comments
Revision history for this message
SqUe (sque) wrote :

Same error on Ubuntu Gnome 15.10 running 4.2 or 4.3 or 4.4-rc8 as also on Debian testing with 4.3. I get randomly this kind of error:
[ 851.659186] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[ 851.659208] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
[ 851.659219] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
[ 851.659227] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)

Revision history for this message
SqUe (sque) wrote :

..continuing (pressed post by mistake)

I am on intel i5-6200u and the pci port is the one that wireless card is connected too.

lspci -vt
-[0000:00]-+-00.0 Intel Corporation Sky Lake Host Bridge/DRAM Registers
           +-02.0 Intel Corporation Sky Lake Integrated Graphics
           +-14.0 Intel Corporation Device 9d2f
           +-14.2 Intel Corporation Device 9d31
           +-16.0 Intel Corporation Device 9d3a
           +-17.0 Intel Corporation Device 9d03
           +-1c.0-[01]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           +-1c.5-[02]----00.0 Intel Corporation Wireless 3165
           +-1d.0-[03]----00.0 Realtek Semiconductor Co., Ltd. Device 522a
           +-1f.0 Intel Corporation Device 9d48
           +-1f.2 Intel Corporation Device 9d21
           +-1f.3 Intel Corporation Device 9d70
           \-1f.4 Intel Corporation Device 9d23

I am also having spci -vt
-[0000:00]-+-00.0 Intel Corporation Sky Lake Host Bridge/DRAM Registers
           +-02.0 Intel Corporation Sky Lake Integrated Graphics
           +-14.0 Intel Corporation Device 9d2f
           +-14.2 Intel Corporation Device 9d31
           +-16.0 Intel Corporation Device 9d3a
           +-17.0 Intel Corporation Device 9d03
           +-1c.0-[01]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           +-1c.5-[02]----00.0 Intel Corporation Wireless 3165
           +-1d.0-[03]----00.0 Realtek Semiconductor Co., Ltd. Device 522a
           +-1f.0 Intel Corporation Device 9d48
           +-1f.2 Intel Corporation Device 9d21
           +-1f.3 Intel Corporation Device 9d70
           \-1f.4 Intel Corporation Device 9d23

The weird thing is that at some boots this error never appears and on some others this error my show early or later and repeatedly.

Jan W (ubuntu-kiekerjan)
tags: added: kernel-bug-exists-upstream-4.4.1
removed: kernel-bug-exists-upstream-4.4-rc3
Jan W (ubuntu-kiekerjan)
tags: added: wily
Revision history for this message
Jordon Bedwell (envygeeks) wrote :

I still get this problem in Xenial as well... randomly but it happens.

122 comments hidden view all 156 comments
Revision history for this message
In , bugs (bugs-linux-kernel-bugs) wrote :

Looks like I have this same problem (with the same hardware). Adding my name to the list, using Ubuntu's Xubuntu 15.10 distro. The pci=noaer works, although pci=nomsi also works.

Strangely enough, Knoppix 7.6.1 boots just fine. Hmmm...

121 comments hidden view all 156 comments
Revision history for this message
Ehsan (azarnasab) wrote :

On 4.4.8-300.fc23.x86_64 with "Dell Inc. XPS 8900/0XJ8C4, BIOS 2.1.3 01/20/2016" and "i7-6700 CPU @ 3.40GHz (family: 0x6, model: 0x5e, stepping: 0x3)"

```text
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: can't find device of ID00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: device [8086:a110] error status/mask=00000001/00002000
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: [ 0] Receiver Error (First)
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: can't find device of ID00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: can't find device of ID00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: can't find device of ID00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: can't find device of ID00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: can't find device of ID00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: can't find device of ID00e0
May 05 14:02:57 dashesy.wavelet kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
```

That device is "PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)" and is used by "+-1c.0-[02]----00.0 Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter"
`pci=nomsi` solved the problem but so did `pci=noaer` which I will use for now.

I will gladly do debugging if there is a kernel to test.

122 comments hidden view all 156 comments
Revision history for this message
In , cspadijer (cspadijer-linux-kernel-bugs) wrote :

Just an update.
confirmed Kelly Price's discovery: Knoppix 7.6.1 with kernel 4.2.6 boots fine.
Thanks Kelly.

I flash updated the BIOS to latest vendor supplied version 206 (2016/02/24).

Latest Ubuntu 16.04 with kernel 4.4 still has the same problem.

121 comments hidden view all 156 comments
Revision history for this message
Abhishek Bhatia (abhigenie92) wrote :

I tried the suggestion of pci=nomsi but it doesn't fix it. Here are the complete details. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588428

Revision history for this message
Abhishek Bhatia (abhigenie92) wrote :

Any progress on this bug?

Revision history for this message
e633 (e633) wrote :

Hello, i am affected too. Dell Latitude 3570. Kernel 4.4.0-21-generic x86_64 and in my case the problematic device seems to be the Qualcomm Atheros AR9462 Wireless Network Adapter. Everything seems to work though.
Full PC specs: https://paste.debian.net/hidden/03da6511/

Error:
AER: Corrected error received: id=00e0
pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e0(Transmitter ID)
pcieport 0000:00:1c.0: device [8086:9d14] error status/mask=00003000/00002000
pcieport 0000:00:1c.0: [12] Replay Timer Timeout

#lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM Registers [8086:1904] (rev 08)
00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07)
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:9d2f] (rev 21)
00:14.2 Signal processing controller [1180]: Intel Corporation Device [8086:9d31] (rev 21)
00:15.0 Signal processing controller [1180]: Intel Corporation Device [8086:9d60] (rev 21)
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:9d3a] (rev 21)
00:17.0 SATA controller [0106]: Intel Corporation Device [8086:9d03] (rev 21)
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9d14] (rev f1)
00:1c.5 PCI bridge [0604]: Intel Corporation Device [8086:9d15] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d48] (rev 21)
00:1f.2 Memory controller [0580]: Intel Corporation Device [8086:9d21] (rev 21)
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:9d70] (rev 21)
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:9d23] (rev 21)
01:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01)
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)

#lspci -vt
-[0000:00]-+-00.0 Intel Corporation Sky Lake Host Bridge/DRAM Registers
           +-02.0 Intel Corporation Sky Lake Integrated Graphics
           +-14.0 Intel Corporation Device 9d2f
           +-14.2 Intel Corporation Device 9d31
           +-15.0 Intel Corporation Device 9d60
           +-16.0 Intel Corporation Device 9d3a
           +-17.0 Intel Corporation Device 9d03
           +-1c.0-[01]----00.0 Qualcomm Atheros AR9462 Wireless Network Adapter
           +-1c.5-[02]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           +-1f.0 Intel Corporation Device 9d48
           +-1f.2 Intel Corporation Device 9d21
           +-1f.3 Intel Corporation Device 9d70
           \-1f.4 Intel Corporation Device 9d23

pci=noaer helps.

Revision history for this message
Игорь (ifree92) wrote :

I have the same "spam" in my dmesg
And as said upper... I have "Intel Corporation Wireless 3165" card connected.

So strange....

Revision history for this message
erika jonell (erika-jonell) wrote :

In order to supress the error and boot at all you must add pci=noaer to your kernel boot parameters. You can do it in the install launcher's GRUB menu or during boot, then regen your grub.cfg with it included for future boots.

This is not an ubuntu unique problem, as i can confirm it exists in other distros as well (Arch for one).

my belief is it is an issue with Skylake chips and intel based mobos and the south-bridge PCI support within the kernel itself.

(i have a i7 6700 and an H110 chipset)

Revision history for this message
Makda (makdamujji) wrote :

This is my dmesg output:
[ 121.716206] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00000000
[ 121.716209] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
[ 121.716216] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[ 121.716616] pcieport 0000:00:1c.5: can't find device of ID00e5
[ 121.716619] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[ 121.717092] pcieport 0000:00:1c.5: can't find device of ID00e5
[ 121.717109] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
[ 121.717129] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)

my 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 134e (rev a2)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter

Most probably having something to do with 6th gen intel and Realtek hardware.

Doug McMahon (mc3man)
tags: added: yakketywily
removed: wily
tags: added: wily yakkety
removed: yakketywily
Revision history for this message
JujuLand (alain-aupeix) wrote :

Same bug with a Dell XPS8900.

I can install 12.04, but it fails with 15.10 or 16.04.
Having installed 12.04 and updated to 14.04, I have then updated to 16.04, but if it boots correctly, syslog and kern.log are filled with these messages and / is filled (0 bytes free ...)

I tried to boot on 16.04 DVD, but impossible ...

Is there any progress about this bug ?

Thanks
A+

Revision history for this message
Bill Michaelson (t-launchpad-bill-from-net) wrote :

I seem to have this issue too, but related to a different device. Running 16.04 with 4.4.0-31-generic. New (used) machine so very concering. It ran fine for about an hour then spontaneously started spewing this:

Jul 26 13:28:05 twin kernel: [ 8.837650] pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
Jul 26 13:28:05 twin kernel: [ 8.837665] pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver ID)
Jul 26 13:28:05 twin kernel: [ 8.837675] pcieport 0000:00:03.0: device [8086:d138] error status/mask=00000001/00002000
Jul 26 13:28:05 twin kernel: [ 8.837685] pcieport 0000:00:03.0: [ 0] Receiver Error (First)

lspci -nn gives me a match against this:

00:03.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express Root Port 1 [8086:d138] (rev 11)

and booting with pci=noaer suppresses the messages with no apparent ill effects.

But I don't know what the message is supposed to mean and I fear that I am suppressing a valid warning and gambling if I use the machine for serious work. Insights more than welcome. The machine is an ASUS G73Jh laptop Intel Core i7-720QM @ 1.60GHz / Nehalem 45nm). TIA.

Revision history for this message
David Henningsson (diwic) wrote :

Out of curiousity, do all of you have the combination of Skylake + RTL8723BE, and second, do you experience (as I do) that wifi doesn't work very well (often loses connections etc)?

...as the errors seem to indicate some kind of physical error between the Skylake/Sunrise Point host controller and the wifi card.

Revision history for this message
David Henningsson (diwic) wrote :

Btw, I reported mine upstream long ago and got response from upstream that "I've thought about this problem a bit, but realistically I don't have time to do the fix I'd like to do /.../ Anybody else who is interested should feel free to take a crack at it."

See http://permalink.gmane.org/gmane.linux.kernel.pci/48697

Also some googling finds me a few other reports with very similar symptoms, e g:

https://bugzilla.kernel.org/show_bug.cgi?id=111601

https://lkml.org/lkml/2015/9/2/573

description: updated
Revision history for this message
Fabio A. (falemagn) wrote :

Yes David, I've got your exact hw combination and indeed wifi sometimes seems to "get stuck".

A
    sudo modprobe -r rtl8723be

followed by

    sudo modprobe rtl8723be

does the trick of bringing the device to life most of the times, though.

Revision history for this message
Makda (makdamujji) wrote :

WiFi can be fixed by this:

Create a conf file for Wifi:
sudo gedit /etc/modprobe.d/rtl8723be.conf

Write in it:
options rtl8723be fwlps=N ips=N

Save and reboot. WIFi will work fine now, but the NOAER error still floods the dmesg.

Revision history for this message
JujuLand (alain-aupeix) wrote :

I have build the Dell XP 8900 with Ubuntu 14.04, and it works fine.

I forget to disable LTS update, and the owner made the update

The bug is always here, and I must redo a 14.04 install

Grrr ....

Does somebody is in charge of this bug which is very old (since 15.04) ?

Thanks
A+

Revision history for this message
Bjorn Helgaas (bjorn-helgaas) wrote :

Related problem report:
https://bugzilla.kernel.org/show_bug.cgi?id=109691

Brief analysis of AER issue:
http://lkml.kernel.org/r/20151229155822.GA17321@localhost

I did say in that analysis that I was going to work on fixing this, but I haven't had time. It would be great if somebody would jump in and help out.

Revision history for this message
JujuLand (alain-aupeix) wrote :

Hi, I had a look to the link you give, and saw there is a way to boot using pci=noaer parameter.

It's a good way while no other solution has been found, but does this method is usable when booting on a live hd to install on an HD

Thanks
A+

Revision history for this message
JujuLand (alain-aupeix) wrote :

Humm ... typo : booting on a live DvD, obviously :)

A+

Revision history for this message
John (jsalatas) wrote :

Same here. Also in a Dell XPS 8900 (Skylake + RTL8723BE) using kernel 4.4.0

Revision history for this message
Eduardo Montes de Oca Sanchez (ed-montesdeoca) wrote :
Download full text (6.4 KiB)

I have de same issue. I Have an HP Star Wars Special Edition 15-an050nr:

edrendar@outrider-HP-Pavilion-Notebook:~$ tail -f /var/log/syslog
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778017] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778028] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778032] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778035] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778041] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778151] pcieport 0000:00:1c.5: can't find device of ID00e5
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778296] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778307] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778310] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778313] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.877828] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.877853] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.877864] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.877872] pcieport 0000:00:1c.5: [ 0] Receiver Error
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.877885] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.878542] pcieport 0000:00:1c.5: can't find device of ID00e5
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.878562] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.878587] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.878594] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.878600] pcieport 0000:00:1c.5: [ 0] Receiver Error
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.878611] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Nov 8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.879259] pcieport 0000:00:1c.5: can't find device of ID00e...

Read more...

Revision history for this message
Daniel Jose (danieldsj) wrote :

I exhibited similar symptoms when installing Ubuntu 16.04.1 LTS on an Asus x541u VivoBook Max system. When performing the installation, the logs would fill up with these errors and eventually fail because of lack of disk space. I found the following thread helpful...
http://www.gossamer-threads.com/lists/linux/kernel/2250177

The workaround for me was to hold left SHIFT, edit the grub menu and add the pcie_aspm=off kernel parameter to suppress the messages during the installation and every subsequent boot. Adding these options to the grub configuration after installing was the long-term workaround.

Revision history for this message
Ped (ped) wrote :

I'm slightly affected, or maybe actually my kernel is "fixed" to correctly clear the error report even when device is not found internally (referring to the #27 brief analysis), as I do see the AER error in dmesg, periodically showing up, but only about once per couple of minutes.

It's still beyond being acceptable for me, so I used the "pci=noaer" workaround, which stops the messages appearing.

Error log:
[ 487.987496] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[ 487.987503] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[ 487.987505] pcieport 0000:00:1c.0: device [8086:a110] error status/mask=00000001/00002000
[ 487.987507] pcieport 0000:00:1c.0: [ 0] Receiver Error (First)

Further errors have the same 1c.0 address (Intel Corporation Wireless 3165) and details.

Kernel version: 4.4.0-59-generic

CPU: Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz

# lspci -vt
-[0000:00]-+-00.0 Intel Corporation Sky Lake Host Bridge/DRAM Registers
           +-01.0-[01]----00.0 NVIDIA Corporation GM107M [GeForce GTX 960M]
           +-02.0 Intel Corporation Skylake Integrated Graphics
           +-14.0 Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller
           +-14.2 Intel Corporation Sunrise Point-H Thermal subsystem
           +-16.0 Intel Corporation Sunrise Point-H CSME HECI #1
           +-17.0 Intel Corporation Sunrise Point-H SATA Controller [AHCI mode]
           +-1c.0-[02]----00.0 Intel Corporation Wireless 3165
           +-1c.3-[03]----00.0 Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller
           +-1f.0 Intel Corporation Sunrise Point-H LPC Controller
           +-1f.2 Intel Corporation Sunrise Point-H PMC
           +-1f.3 Intel Corporation Sunrise Point-H HD Audio
           \-1f.4 Intel Corporation Sunrise Point-H SMBus

MSI Notebook GP62 6QF-678XCZ

Revision history for this message
mohican (mohican) wrote :

Hello,
same bug on Asus R556UB-DM217T (live session)

I was able to install using pci=noaer

Also associated with a bug with the sound (no input sound from integrated webcam mic)
sound device : HDA Intel PCH, Realtek ALC256

Revision history for this message
pakman (phill-phillk) wrote :

not sure if this merit's as i encountered this on a Centos install with anaconda, booted with the flag specified & the errors didnt pile up. Hardware is a dell xps. i can provide more info if needed.

Revision history for this message
PanPetr (javacentrum) wrote :

The same issue: lubuntu 16.04 on HP ProBook 470 G3 writes to kernel.log and then completely freeze

Mar 24 09:02:09 localhost kernel: [ 6972.305728] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Mar 24 09:02:09 localhost kernel: [ 6972.305749] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Mar 24 09:02:09 localhost kernel: [ 6972.305760] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Mar 24 09:02:09 localhost kernel: [ 6972.305768] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Mar 24 09:03:12 localhost kernel: [ 7035.298073] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Mar 24 09:03:12 localhost kernel: [ 7035.298083] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Mar 24 09:03:12 localhost kernel: [ 7035.298087] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Mar 24 09:03:12 localhost kernel: [ 7035.298089] pcieport 0000:00:1c.5: [ 0] Receiver Error
Mar 24 09:04:15 localhost kernel: [ 7098.238955] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Mar 24 09:04:15 localhost kernel: [ 7098.238979] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Mar 24 09:04:15 localhost kernel: [ 7098.238992] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Mar 24 09:04:15 localhost kernel: [ 7098.239001] pcieport 0000:00:1c.5: [ 0] Receiver Error
\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00

Revision history for this message
Davide (davide-maraschio93) wrote :

The same issue: Ubuntu 16.04.2 on Asus N552VW-FY136T writes to kernel.log and then completely freeze

Mar 24 09:02:09 localhost kernel: [ 6972.305728] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
pcieport 0000:00:1c.5 PCIe Bus Error: severity=corrected, type=physical layer, id=00e4(Receiver 12)
pcieport 0000:00:1c.5 device[8086:a112] error status/mask=00000001/000020000

The workarounds described here don't work for me.

Revision history for this message
Davide (davide-maraschio93) wrote :

My kernel version is 4.8

Revision history for this message
Davide (davide-maraschio93) wrote :

I've reinstalled Ubuntu and now it starts. I typed dmesg and there's this message anyway:

[ 0.875431] pcieport 0000:00:1c.4: AER: Corrected error received: id=00e4
[ 0.875438] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID)
[ 0.875440] pcieport 0000:00:1c.4: device [8086:a114] error status/mask=00000100/00002000
[ 0.875442] pcieport 0000:00:1c.4: [ 8] RELAY_NUM Rollover
[ 0.879660] pcieport 0000:00:1c.4: AER: Corrected error received: id=00e4
[ 0.879667] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID)
[ 0.879669] pcieport 0000:00:1c.4: device [8086:a114] error status/mask=00000100/00002000
[ 0.879670] pcieport 0000:00:1c.4: [ 8] RELAY_NUM Rollover
[ 0.911313] pcieport 0000:00:1c.4: AER: Corrected error received: id=00e4
[ 0.911319] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID)
[ 0.911320] pcieport 0000:00:1c.4: device [8086:a114] error status/mask=00000100/00002000
[ 0.911321] pcieport 0000:00:1c.4: [ 8] RELAY_NUM Rollover
[ 0.923536] pcieport 0000:00:1c.4: AER: Corrected error received: id=00e4
[ 0.923542] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID)
[ 0.923543] pcieport 0000:00:1c.4: device [8086:a114] error status/mask=00000100/00002000
[ 0.923544] pcieport 0000:00:1c.4: [ 8] RELAY_NUM Rollover

wanghuan (fredwanghuan)
Changed in linux (Ubuntu):
status: Triaged → New
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: artful
information type: Public → Public Security
information type: Public Security → Public
information type: Public → Public Security
information type: Public Security → Public
M (manudv7)
Changed in linux (Ubuntu):
status: Confirmed → In Progress
M (manudv7)
Changed in linux (Ubuntu):
status: In Progress → Confirmed
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
C de-Avillez (hggdh2)
Changed in linux (Ubuntu):
status: Fix Released → Triaged
description: updated
Brad Figg (brad-figg)
tags: added: cscc
information type: Public → Public Security
information type: Public Security → Public
76 comments hidden view all 156 comments
Revision history for this message
Luis A (peppapig123) wrote :

This bug still affect the install process today, with ubuntu 20.04 LTS and same with kubuntu installer.

Revision history for this message
fermulator (fermulator) wrote :

"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 RTS5413 in Dell dock, current is 01.21: 01.21=same
No upgrades for RTS5487 in Dell dock, current is 01.47: 01.47=same
No upgrades for WD19, current is 01.00.00.00: 01.00.00.00=same
No upgrades for Package level of Dell dock, current is 01.00.04.01: 01.00.04.01=same
No upgrades for VMM5331 in Dell dock, current is 05.03.10: 05.03.10=same
```

spammed by
```
[Tue Sep 15 18:50:06 2020] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
[Tue Sep 15 18:50:06 2020] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[Tue Sep 15 18:50:06 2020] pcieport 0000:00:1d.0: device [8086:9db1] error status/mask=00001000/00002000
[Tue Sep 15 18:50:06 2020] pcieport 0000:00:1d.0: [12] Timeout
```

```
lspci -v | grep 9db1
00:1d.0 PCI bridge: Intel Corporation Device 9db1 (rev f0) (prog-if 00 [Normal decode])
```

Revision history for this message
Bill Duetschler (bikergeek) wrote :

Still an issue for me on Ubuntu 20.10 "Groovy".

Revision history for this message
Wren Turkal (wt-penguintechs-org) wrote :

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.

Revision history for this message
Wren Turkal (wt-penguintechs-org) wrote :

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.

Revision history for this message
Wren Turkal (wt-penguintechs-org) wrote :

I also tried all LTS Ubuntus back to 16.04. They all get this log message a lot.

Revision history for this message
Nivedita Singhvi (niveditasinghvi) wrote :

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.

13 comments hidden view all 156 comments
Revision history for this message
In , rbelli97 (rbelli97-linux-kernel-bugs) wrote :

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.

12 comments hidden view all 156 comments
Revision history for this message
Riccardo Belli (rbelli97) wrote :

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.

Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Tobias Schönberg (tobias47n9e) wrote :

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 0000:00:03.1: AER: Multiple Corrected error received: 0000:00:00.0
Apr 09 13:00:28 tobias-MS-7C37 kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Apr 09 13:00:28 tobias-MS-7C37 kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00001100/00006000
Apr 09 13:00:28 tobias-MS-7C37 kernel: pcieport 0000:00:03.1: [ 8] Rollover
Apr 09 13:00:28 tobias-MS-7C37 kernel: pcieport 0000:00:03.1: [12] Timeout
Apr 09 13:00:29 tobias-MS-7C37 kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Apr 09 13:00:29 tobias-MS-7C37 kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Apr 09 13:00:29 tobias-MS-7C37 kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00001000/00006000
Apr 09 13:00:29 tobias-MS-7C37 kernel: pcieport 0000:00:03.1: [12] Timeout

Revision history for this message
Paul Menzel (paulmenzel) wrote :

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 current Linux kernel using Ubuntu PPA repository [1].

[1]: https://kernel.ubuntu.com/~kernel-ppa/

Revision history for this message
Tobias Schönberg (tobias47n9e) wrote :
Download full text (10.0 KiB)

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-1fh) 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.2 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-1fh) PCIe Dummy Host Bridge [1022:1452]
00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) 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-1fh) PCIe Dummy Host Bridge [1022:1452]
00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) 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-1fh) 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]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808]
20:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream [1022:57ad]
21:00.0 PCI bridge [0604]: Advan...

Revision history for this message
Paul Menzel (paulmenzel) wrote :

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`.

9 comments hidden view all 156 comments
Revision history for this message
In , pmenzel+bugzilla.kernel.org (pmenzel+bugzilla.kernel.org-linux-kernel-bugs) wrote :

As the ASUS X541UVK is a different device, please create a new bug report with all the necessary information included/attached.

Revision history for this message
In , bjorn (bjorn-linux-kernel-bugs) wrote :

Riccardo, would you mind booting with just "pci=noaer" to see if that works around the problem? Your photo at https://i.imgur.com/PPZ49lL.jpg suggests that it might.

Revision history for this message
Riccardo Belli (rbelli97) wrote :

I just created the new bug report as suggested, here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752

1 comments hidden view all 156 comments
Revision history for this message
In , naveennaidu479 (naveennaidu479-linux-kernel-bugs) wrote :

Created attachment 299043
Patch for the AER message spew

Hello Folks,

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 unable to test it out.

It would really help if anyone could please test this patch and see if it solved the AER message spew.

Thanks,
Naveen Naidu

Revision history for this message
In , naveennaidu479 (naveennaidu479-linux-kernel-bugs) wrote :

(In reply to Naveen Naidu from comment #11)
> Created attachment 299043 [details]
> Patch for the AER message spew
>
> Hello Folks,
>
> 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 unable to test it out.
>
> It would really help if anyone could please test this patch and see if it
> solved the AER message spew.
>
> Thanks,
> Naveen Naidu

Forgot to mention! This patch would make the "pci=noaer" unnecessary.

tags: added: patch
2 comments hidden view all 156 comments
Revision history for this message
In , cspadijer (cspadijer-linux-kernel-bugs) wrote :

Created attachment 299047
attachment-6460-0.html

Hi Naveen.
Absolutely, I can test.
I can try it out this weekend.

Chris

⁣Get BlueMail for Android ​

On Oct 1, 2021, 2:35 AM, at 2:35 AM, <email address hidden> wrote:
>https://bugzilla.kernel.org/show_bug.cgi?id=109691
>
>Naveen Naidu (<email address hidden>) changed:
>
> What |Removed |Added
>----------------------------------------------------------------------------
> CC| |<email address hidden>
>
>--- Comment #11 from Naveen Naidu (<email address hidden>) ---
>Created attachment 299043
> --> https://bugzilla.kernel.org/attachment.cgi?id=299043&action=edit
>Patch for the AER message spew
>
>Hello Folks,
>
>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 unable to test it out.
>
>It would really help if anyone could please test this patch and see if
>it
>solved the AER message spew.
>
>Thanks,
>Naveen Naidu
>
>--
>You may reply to this email to add a comment.
>
>You are receiving this mail because:
>You reported the bug.

Revision history for this message
In , naveennaidu479 (naveennaidu479-linux-kernel-bugs) wrote :

Comment on attachment 299043
Patch for the AER message spew

I apologize, please ignore this patch. I realized there is a bug in the patch. I have fixed it now and will upload it. I apologized for the inconvenience caused. I do not know how to delete this patch, so I'll reupload a new patch. Apologies again ^^'

Revision history for this message
In , naveennaidu479 (naveennaidu479-linux-kernel-bugs) wrote :

Created attachment 299071
Patch for the AER message spew

This is the correct patch. Please use this and ignore the previous patch.

Revision history for this message
In , naveennaidu479 (naveennaidu479-linux-kernel-bugs) wrote :

Created attachment 299073
Patch for the AER message spew

3 comments hidden view all 156 comments
Revision history for this message
Naveen Naidu (theprophet26) wrote :

This is the correct patch for the AER message spew.

4 comments hidden view all 156 comments
Revision history for this message
In , cspadijer (cspadijer-linux-kernel-bugs) wrote :

Created attachment 299081
attachment-4100-0.html

Okay sounds good.
I will try it soon.

Chris

⁣Get BlueMail for Android ​

On Oct 3, 2021, 2:03 AM, at 2:03 AM, <email address hidden> wrote:
>https://bugzilla.kernel.org/show_bug.cgi?id=109691
>
>Naveen Naidu (<email address hidden>) changed:
>
> What |Removed |Added
>----------------------------------------------------------------------------
> Attachment #299043|0 |1
> is obsolete| |
>
>--- Comment #15 from Naveen Naidu (<email address hidden>) ---
>Created attachment 299071
> --> https://bugzilla.kernel.org/attachment.cgi?id=299071&action=edit
>Patch for the AER message spew
>
>This is the correct patch. Please use this and ignore the previous
>patch.
>
>--
>You may reply to this email to add a comment.
>
>You are receiving this mail because:
>You reported the bug.

Revision history for this message
In , cspadijer (cspadijer-linux-kernel-bugs) wrote :
Download full text (3.8 KiB)

Are you good with me using kernel: 5.11.0-37-generic  or would you
prefer I use a different kernel?
The X555U is currently running Linux Mint 20.2 Cinnamon.

FYI:
I tried removing pci=noaer and it does boot now (without your patch).
It has been a while since I tried removing pci=noaer and new kernels get
installed all the time so not sure what kernel first started allowing it
to boot without needing that line.
However, there are still many errors on boot.

dmesg --level=err,warn
[    0.105337] x86/cpu: VMX (outside TXT) disabled by BIOS
[    0.110761] MDS CPU bug present and SMT on, data leak possible. See
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for
more details.
[    0.110761]  #3
[    0.114598] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.135583] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PCI0.RP01.PXSX], AE_NOT_FOUND (20201113/psargs-330)
[    0.135597] ACPI Error: Skipping While/If block (20201113/psloop-427)
[    0.527786] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not
cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f
flags 0x200] vs fed40080 f80
[    0.527874] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not
cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f
flags 0x200] vs fed40080 f80
[    0.736009] i8042: PNP: PS/2 appears to have AUX port disabled, if
this is incorrect please boot with i8042.nopnp
[    0.738042] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    0.738044] platform eisa.0: Cannot allocate resource for EISA slot 1
[    0.738045] platform eisa.0: Cannot allocate resource for EISA slot 2
[    0.738046] platform eisa.0: Cannot allocate resource for EISA slot 3
[    0.738048] platform eisa.0: Cannot allocate resource for EISA slot 4
[    0.738049] platform eisa.0: Cannot allocate resource for EISA slot 5
[    0.738050] platform eisa.0: Cannot allocate resource for EISA slot 6
[    0.738051] platform eisa.0: Cannot allocate resource for EISA slot 7
[    0.738052] platform eisa.0: Cannot allocate resource for EISA slot 8
[    1.268806] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have
ASPM control
[    1.329939] i2c_hid i2c-ELAN1000:00: supply vdd not found, using
dummy regulator
[    1.329973] i2c_hid i2c-ELAN1000:00: supply vddl not found, using
dummy regulator
[    1.611704] ata1.00: supports DRM functions and may not be fully
accessible
[    1.613394] ata1.00: supports DRM functions and may not be fully
accessible
[    5.726419] elan_i2c i2c-ELAN1000:00: supply vcc not found, using
dummy regulator
[    6.376762] nvidia: loading out-of-tree module taints kernel.
[    6.376775] nvidia: module license 'NVIDIA' taints kernel.
[    6.376776] Disabling lock debugging due to kernel taint

[    6.884240] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 470.63.01
Tue Aug  3 20:44:16 UTC 2021
[    6.958699] nvidia_uvm: module uses symbols from proprietary module
nvidia, inheriting taint.
[    8.533945] ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20201113/nsarguments-61)

Chris

On 2021-10-03 2:03 a.m., bugzilla-daemo...

Read more...

Revision history for this message
In , pmenzel+bugzilla.kernel.org (pmenzel+bugzilla.kernel.org-linux-kernel-bugs) wrote :
Download full text (3.9 KiB)

(In reply to cspadijer from comment #18)
> Are you good with me using kernel: 5.11.0-37-generic  or would you
> prefer I use a different kernel?
> The X555U is currently running Linux Mint 20.2 Cinnamon.
>
> FYI:
> I tried removing pci=noaer and it does boot now (without your patch).
> It has been a while since I tried removing pci=noaer and new kernels get
> installed all the time so not sure what kernel first started allowing it
> to boot without needing that line.
> However, there are still many errors on boot.

The original bug seems to be solved now. As there are over ten comments already, could you mark it as fixed, and create new issues?

> dmesg --level=err,warn
> [    0.105337] x86/cpu: VMX (outside TXT) disabled by BIOS
> [    0.110761] MDS CPU bug present and SMT on, data leak possible. See
> https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for
> more details.

Is GNU/Linux applying the latest microcode updates?

> [    0.110761]  #3

Cosmetic error.

> [    0.114598] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
> [    0.135583] ACPI BIOS Error (bug): Could not resolve symbol
> [\_SB.PCI0.RP01.PXSX], AE_NOT_FOUND (20201113/psargs-330)
> [    0.135597] ACPI Error: Skipping While/If block (20201113/psloop-427)
> [    0.527786] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not
> cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags
> 0x200] vs fed40080 f80
> [    0.527874] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not
> cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags
> 0x200] vs fed40080 f80

Firmware issues.

> [    0.736009] i8042: PNP: PS/2 appears to have AUX port disabled, if this is
> incorrect please boot with i8042.nopnp

Can be ignored.

> [    0.738042] platform eisa.0: EISA: Cannot allocate resource for mainboard
> [    0.738044] platform eisa.0: Cannot allocate resource for EISA slot 1
> [    0.738045] platform eisa.0: Cannot allocate resource for EISA slot 2
> [    0.738046] platform eisa.0: Cannot allocate resource for EISA slot 3
> [    0.738048] platform eisa.0: Cannot allocate resource for EISA slot 4
> [    0.738049] platform eisa.0: Cannot allocate resource for EISA slot 5
> [    0.738050] platform eisa.0: Cannot allocate resource for EISA slot 6
> [    0.738051] platform eisa.0: Cannot allocate resource for EISA slot 7
> [    0.738052] platform eisa.0: Cannot allocate resource for EISA slot 8

Is there an EISA slot?

> [    1.268806] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM
> control

Can be ignored.

> [    1.329939] i2c_hid i2c-ELAN1000:00: supply vdd not found, using dummy
> regulator
> [    1.329973] i2c_hid i2c-ELAN1000:00: supply vddl not found, using dummy
> regulator

Please contact the Linux folks about this. But first try the latest Linux mainline version.

> [    1.611704] ata1.00: supports DRM functions and may not be fully
> accessible
> [    1.613394] ata1.00: supports DRM functions and may not be fully
> accessible
> [    5.726419] elan_i2c i2c-ELAN1000:00: supply vcc not found, using dummy
> regulator
> [    6.376762] nvidia: loading out-of-tree module taints kernel.
> [    6.376...

Read more...

Revision history for this message
In , cspadijer (cspadijer-linux-kernel-bugs) wrote :
Download full text (4.6 KiB)

Created attachment 299107
attachment-9243-0.html

Hi Paul.

Okay yes.  I will mark as fixed and open up new for other issues you clarified as linux.  Thanks for your help.

For the firmware issues should I be reaching out to the vendors?

Chris

⁣Get BlueMail for Android ​

On Oct 5, 2021, 7:13 AM, at 7:13 AM, <email address hidden> wrote:
>https://bugzilla.kernel.org/show_bug.cgi?id=109691
>
>--- Comment #19 from Paul Menzel
>(<email address hidden>) ---
>(In reply to cspadijer from comment #18)
>> Are you good with me using kernel: 5.11.0-37-generic  or would you
>> prefer I use a different kernel?
>> The X555U is currently running Linux Mint 20.2 Cinnamon.
>>
>> FYI:
>> I tried removing pci=noaer and it does boot now (without your patch).
>> It has been a while since I tried removing pci=noaer and new kernels
>get
>> installed all the time so not sure what kernel first started allowing
>it
>> to boot without needing that line.
>> However, there are still many errors on boot.
>
>The original bug seems to be solved now. As there are over ten comments
>already, could you mark it as fixed, and create new issues?
>
>> dmesg --level=err,warn
>> [    0.105337] x86/cpu: VMX (outside TXT) disabled by BIOS
>> [    0.110761] MDS CPU bug present and SMT on, data leak possible.
>See
>> https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html
>for
>> more details.
>
>Is GNU/Linux applying the latest microcode updates?
>
>> [    0.110761]  #3
>
>Cosmetic error.
>
>> [    0.114598] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
>> [    0.135583] ACPI BIOS Error (bug): Could not resolve symbol
>> [\_SB.PCI0.RP01.PXSX], AE_NOT_FOUND (20201113/psargs-330)
>> [    0.135597] ACPI Error: Skipping While/If block
>(20201113/psloop-427)
>> [    0.527786] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does
>not
>> cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f
>flags
>> 0x200] vs fed40080 f80
>> [    0.527874] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does
>not
>> cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f
>flags
>> 0x200] vs fed40080 f80
>
>Firmware issues.
>
>> [    0.736009] i8042: PNP: PS/2 appears to have AUX port disabled, if
>this is
>> incorrect please boot with i8042.nopnp
>
>Can be ignored.
>
>> [    0.738042] platform eisa.0: EISA: Cannot allocate resource for
>mainboard
>> [    0.738044] platform eisa.0: Cannot allocate resource for EISA
>slot 1
>> [    0.738045] platform eisa.0: Cannot allocate resource for EISA
>slot 2
>> [    0.738046] platform eisa.0: Cannot allocate resource for EISA
>slot 3
>> [    0.738048] platform eisa.0: Cannot allocate resource for EISA
>slot 4
>> [    0.738049] platform eisa.0: Cannot allocate resource for EISA
>slot 5
>> [    0.738050] platform eisa.0: Cannot allocate resource for EISA
>slot 6
>> [    0.738051] platform eisa.0: Cannot allocate resource for EISA
>slot 7
>> [    0.738052] platform eisa.0: Cannot allocate resource for EISA
>slot 8
>
>Is there an EISA slot?
>
>> [    1.268806] r8169 0000:02:00.0: can't disable ASPM; OS doesn't
>have ASPM
>> control
>
>Can be ignored.
>
>> [    1.329939] i2c_hid i2c-ELAN1000...

Read more...

Revision history for this message
In , pmenzel+bugzilla.kernel.org (pmenzel+bugzilla.kernel.org-linux-kernel-bugs) wrote :

[Please remove the quote next time from your reply. If you look at the Web interface, the comments get needlessly long because of that.]

(In reply to cspadijer from comment #20)

[…]

> Okay yes.  I will mark as fixed and open up new for other issues you
> clarified as linux.  Thanks for your help.

Thank you.

> For the firmware issues should I be reaching out to the vendors?

Yes, only the vendors can fix the firmware, unless you use FLOSS firmware like coreboot based firmware for example.

Unfortunately, my track record of getting vendors to fix their firmware is not so good, as you are only one customer using this weird operating system and not Microsoft Windows. But fingers crossed.

Additionally you might want to point them to the Firmware Test Suite (FWTS) [1].

[1]: https://wiki.ubuntu.com/FirmwareTestSuite/

Revision history for this message
In , cspadijer (cspadijer-linux-kernel-bugs) wrote :

Created attachment 299109
attachment-15734-0.html

Okay great.

Thanks for the link to FirmwareTestSuite.

Chris

⁣Get BlueMail for Android ​

On Oct 5, 2021, 9:25 AM, at 9:25 AM, <email address hidden> wrote:
>https://bugzilla.kernel.org/show_bug.cgi?id=109691
>
>--- Comment #21 from Paul Menzel
>(<email address hidden>) ---
>[Please remove the quote next time from your reply. If you look at the
>Web
>interface, the comments get needlessly long because of that.]
>
>(In reply to cspadijer from comment #20)
>
>[…]
>
>> Okay yes.  I will mark as fixed and open up new for other issues you
>> clarified as linux.  Thanks for your help.
>
>Thank you.
>
>> For the firmware issues should I be reaching out to the vendors?
>
>Yes, only the vendors can fix the firmware, unless you use FLOSS
>firmware like
>coreboot based firmware for example.
>
>Unfortunately, my track record of getting vendors to fix their firmware
>is not
>so good, as you are only one customer using this weird operating system
>and not
>Microsoft Windows. But fingers crossed.
>
>Additionally you might want to point them to the Firmware Test Suite
>(FWTS)
>[1].
>
>
>[1]: https://wiki.ubuntu.com/FirmwareTestSuite/
>
>--
>You may reply to this email to add a comment.
>
>You are receiving this mail because:
>You reported the bug.

Revision history for this message
In , cspadijer (cspadijer-linux-kernel-bugs) wrote :

An upstream kernel since 4.2.0-22-generic has resolved the issue with this make/model of laptop.
Laptop successfully boots now without the pci=nommconf boot parameter.

Changed in linux:
status: Confirmed → Unknown
Displaying first 40 and last 40 comments. View all 156 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.