Bug 1839209 - ACPI issue causing device AER error on PCIe bus at boot time.
Summary: ACPI issue causing device AER error on PCIe bus at boot time.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 32
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-22 18:24 UTC by social_bot
Modified: 2021-05-25 17:41 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:41:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Console after starting boot (111.88 KB, image/jpeg)
2020-05-22 18:24 UTC, social_bot
no flags Details

Description social_bot 2020-05-22 18:24:52 UTC
Created attachment 1691152 [details]
Console after starting boot

This seems to be a problem with the RTL8821AE 802.11ac PCIe Wireless Network Adapter and or the ACPI.

If the ACPI is not turned off via Grub using acpi=off, then it is impossible to boot up, and the console is flooded with messages,(see file attached).

Setting pnpacpi=off means it is possible to boot up and view messages from dmesg.

With ACPI turned off it is not possible to power off the system.

How reproducible:
Always happens.

Steps to Reproduce:
Boot up system (Fedora 32) with default Grub settings.
ACPI is therefore on.

Actual results: See attached image.
Booting with pnpacpi=off means system boots up, and one can run dmesg.

dmesg output:

21 21:05:09 popcorn kernel: pcieport 0000:00:1b.3: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May 21 21:05:09 popcorn systemd-journald[653]: Missed 22 kernel messages
May 21 21:05:09 popcorn kernel: pcieport 0000:00:1b.3: AER: Corrected error received: 0000:00:1b.3
May 21 21:05:09 popcorn systemd-journald[653]: Missed 19 kernel messages
May 21 21:05:09 popcorn kernel: pcieport 0000:00:1b.3: AER: Corrected error received: 0000:00:1b.3

Additional info:
lspci -tv
-[0000:00]-+-00.0  Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers
           +-01.0-[01]--
           +-02.0  Intel Corporation HD Graphics 530
           +-14.0  Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
           +-14.2  Intel Corporation 200 Series PCH Thermal Subsystem
           +-16.0  Intel Corporation 200 Series PCH CSME HECI #1
           +-17.0  Intel Corporation SATA Controller [RAID mode]
           +-1b.0-[02]--
           +-1b.3-[03]----00.0  Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter 
           +-1c.0-[04]--
           +-1c.2-[05]----00.0  Intel Corporation I211 Gigabit Network Connection
           +-1c.3-[06]----00.0  Intel Corporation I211 Gigabit Network Connection
           +-1f.0  Intel Corporation 200 Series PCH LPC Controller (Z270)
           +-1f.2  Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller
           +-1f.3  Intel Corporation 200 Series PCH HD Audio
           \-1f.4  Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller

Comment 1 social_bot 2020-05-23 14:29:48 UTC
Booting up with the setting noapic, and inspecting dmesg, I find it is after the Network Manager is started the AER PCIe Bus errors start:

May 23 13:39:19 popcorn systemd[1]: Starting Network Manager Script Dispatcher Service...
May 23 13:39:19 popcorn NetworkManager[1045]: <info>  [1590237559.0341] device (wlp3s0): driver supports Access Point (AP) mode
May 23 13:39:19 popcorn NetworkManager[1045]: <info>  [1590237559.0346] manager: (wlp3s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/4)
May 23 13:39:19 popcorn NetworkManager[1045]: <info>  [1590237559.0365] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external
')
May 23 13:39:19 popcorn kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected error received: 0000:00:1b.3
May 23 13:39:19 popcorn kernel: pcieport 0000:00:1b.3: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May 23 13:39:19 popcorn kernel: pcieport 0000:00:1b.3: AER:   device [8086:a2ea] error status/mask=00000001/00002000
May 23 13:39:19 popcorn kernel: pcieport 0000:00:1b.3: AER:    [ 0] RxErr                 
May 23 13:39:19 popcorn kernel: pcieport 0000:00:1b.3: AER: Multiple Corrected err

Comment 2 social_bot 2020-05-23 15:53:52 UTC
uname -r
5.6.13-300.fc32.x86_64

Comment 3 Fedora Program Management 2021-04-29 17:03:11 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2021-05-25 17:41:48 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.