PCIe Bus Error

KeyHoi · 2017-04-29 11:42:22

Hello,

I bought a new Laptop and installed Arch Linux with the i3 Window Manager. Everytime I shutdown my PC while my wireless interface is up, this message

keyhoi kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, device [8086:9d15] error status/mask=00000001/00002000 [ 0] Receiver Error		(First)
keyhoi kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
keyhoi kernel: pcieport 0000:00:1c.5: can't find device pf ID00e5

is printed till I shutdown my PC manually.

device at 0000:00:1c.5:

00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08)
	Subsystem: ASUSTeK Computer Inc. Device 1ccd
	Flags: bus master, fast devsel, latency 0
	Capabilities: <access denied>
	Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. Device 1ccd
	Flags: bus master, fast devsel, latency 0, IRQ 127
	Memory at dd000000 (64-bit, non-prefetchable) [size=16M]
	Memory at b0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=64]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915

00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08)
	Subsystem: ASUSTeK Computer Inc. Device 1d6d
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at df320000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: <access denied>
	Kernel driver in use: proc_thermal
	Kernel modules: processor_thermal_device

00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) (prog-if 30 [XHCI])
	Subsystem: ASUSTeK Computer Inc. Device 201f
	Flags: bus master, medium devsel, latency 0, IRQ 125
	Memory at df310000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
	Subsystem: ASUSTeK Computer Inc. Device 1ccd
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Memory at df338000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel_pch_thermal
	Kernel modules: intel_pch_thermal

00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
	Subsystem: ASUSTeK Computer Inc. Device 1d6d
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at df337000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
	Subsystem: ASUSTeK Computer Inc. Device 1d6d
	Flags: bus master, fast devsel, latency 0, IRQ 17
	Memory at df336000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
	Subsystem: ASUSTeK Computer Inc. Device 1ccd
	Flags: bus master, fast devsel, latency 0, IRQ 128
	Memory at df335000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: mei_me
	Kernel modules: mei_me

00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) (prog-if 01 [AHCI 1.0])
	Subsystem: ASUSTeK Computer Inc. Device 1ccd
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 126
	Memory at df330000 (32-bit, non-prefetchable) [size=8K]
	Memory at df334000 (32-bit, non-prefetchable) [size=256]
	I/O ports at f090 [size=8]
	I/O ports at f080 [size=4]
	I/O ports at f060 [size=32]
	Memory at df333000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: <access denied>
	Kernel driver in use: ahci
	Kernel modules: ahci

00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 122
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000e000-0000efff [size=4K]
	Memory behind bridge: de000000-df0fffff [size=17M]
	Prefetchable memory behind bridge: 00000000c0000000-00000000d1ffffff [size=288M]
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 123
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff [size=4K]
	Memory behind bridge: df200000-df2fffff [size=1M]
	Prefetchable memory behind bridge: None
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 124
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 0000c000-0000cfff [size=4K]
	Memory behind bridge: df100000-df1fffff [size=1M]
	Prefetchable memory behind bridge: None
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
	Subsystem: ASUSTeK Computer Inc. Device 1ccd
	Flags: bus master, medium devsel, latency 0

00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
	Subsystem: ASUSTeK Computer Inc. Device 1d6d
	Flags: bus master, fast devsel, latency 0
	Memory at df32c000 (32-bit, non-prefetchable) [size=16K]
	Kernel driver in use: intel_pmc_core

00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
	Subsystem: ASUSTeK Computer Inc. Device 1ccd
	Flags: bus master, fast devsel, latency 32, IRQ 131
	Memory at df328000 (64-bit, non-prefetchable) [size=16K]
	Memory at df300000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel, snd_soc_skl

00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
	Subsystem: ASUSTeK Computer Inc. Device 1ccd
	Flags: medium devsel, IRQ 16
	Memory at df332000 (64-bit, non-prefetchable) [size=256]
	I/O ports at f040 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940M] (rev a2)
	Subsystem: ASUSTeK Computer Inc. Device 246a
	Flags: bus master, fast devsel, latency 0, IRQ 132
	Memory at de000000 (32-bit, non-prefetchable) [size=16M]
	Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Memory at d0000000 (64-bit, prefetchable) [size=32M]
	I/O ports at e000 [size=128]
	Expansion ROM at df000000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: nouveau
	Kernel modules: nouveau

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
	Subsystem: ASUSTeK Computer Inc. Device 200f
	Flags: bus master, fast devsel, latency 0, IRQ 129
	I/O ports at d000 [size=256]
	Memory at df204000 (64-bit, non-prefetchable) [size=4K]
	Memory at df200000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: r8169
	Kernel modules: r8169

03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter
	Subsystem: XAVi Technologies Corp. Device 2482
	Flags: bus master, fast devsel, latency 0, IRQ 130
	I/O ports at c000 [size=256]
	Memory at df100000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: rtl8821ae
	Kernel modules: rtl8821ae

Any suggestions to fix this?

Last edited by KeyHoi (2017-05-01 12:20:35)

x33a · 2017-04-29 18:33:32

Do not post pictures of output, post the actual text.

https://wiki.archlinux.org/index.php/Co … s_and_code

Also, can you elaborate more on this line:

Everytime I shutdown my PC while my wireless interface is up, this message(the red one) is printed till I shutdown my PC manually.

How do you initiate the shutdown and what do you mean by manual shutdown?

ewaller · 2017-04-29 19:18:41

What is the output lspci ? In particular what device is at 0000:00:1c.5 ?

mich41 · 2017-04-29 20:42:22

Dunno what it is, except that it's some error reported by hardware and possibly caused by things being powered down.

Just write some scripts which rmmods the WiFi driver at shutdown if you say it helps

KeyHoi · 2017-04-29 23:15:21

x33a wrote:

Do not post pictures of output, post the actual text.
https://wiki.archlinux.org/index.php/Co … s_and_code
Also, can you elaborate more on this line:
Everytime I shutdown my PC while my wireless interface is up, this message(the red one) is printed till I shutdown my PC manually.
How do you initiate the shutdown and what do you mean by manual shutdown?

I hold down the poweroff button.

KeyHoi · 2017-04-29 23:16:54

mich41 wrote:

Dunno what it is, except that it's some error reported by hardware and possibly caused by things being powered down.
Just write some scripts which rmmods the WiFi driver at shutdown if you say it helps

The problem is I can't enable NetworkManager, because if i do so, the message is printed at boot up till i shutdown the Laptop.

mich41 · 2017-04-30 05:41:07

So it's not just every time you shutdown with the interface up but all the time the interface is up?

OK, since it says the errors are already corrected anyway, maybe just disable error reporting Try adding pci=noaer to the kernel boot parameters.

ewaller · 2017-04-30 16:25:14

Well, what we learned from your truncated lspci output was that the device that was throwing the error was the root port. Had you posted that for which I had asked, we would know what devices were on that bus and, perhaps, gained some insight into the root cause.

KeyHoi · 2017-05-01 12:21:18

ewaller wrote:

Well, what we learned from your truncated lspci output was that the device that was throwing the error was the root port. Had you posted that for which I had asked, we would know what devices were on that bus and, perhaps, gained some insight into the root cause.

I edited it

mrunion · 2017-05-01 12:30:42

KeyHoi wrote:

I hold down the poweroff button.

Personally, I would not be shutting down that way. If I'm not mistaken, that is a "forced shutdown". Try "poweroff" from a prompt or something. (This is probably not the cause of the issue, but just general advice.)

KeyHoi · 2017-05-01 12:51:08

mrunion wrote:

KeyHoi wrote:
I hold down the poweroff button.
Personally, I would not be shutting down that way. If I'm not mistaken, that is a "forced shutdown". Try "poweroff" from a prompt or something. (This is probably not the cause of the issue, but just general advice.)

I know, but I have to. The message is printed every 0.1s till I do a forced shutdown.

ewaller · 2017-05-01 13:56:54

KeyHoi wrote:

...
I edited it

And we remain information starved.

KeyHoi · 2017-05-01 14:10:49

ewaller wrote:

...
And we remain information starved.

What do you mean? I added the output of lspci -v

blahhumbug · 2017-05-01 15:02:59

The requested info does appear to be in the lspci output.

00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 124
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0

So attached to the affected root-port is bus 3 (secondary=03). Which is the wireless network device.

03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter

This is an interesting problem, and I would wager it is a kernel root-port driver issue or a realtek driver issue (since the root-port is the device flagging the receiver errors, this likely means it is getting PCIe framing errors from the attached realtek device, or the attached PCIe device is going to electrical idle, and the root-port is not properly detecting it.

But something during the reset process may be causing the realtek device to go haywire with an unclean shutdown flow. Normally Intel hardware reset flows have a watchdog timer that will eventually force a global-reset even if a device is not responding, but you mentioned that reset never occurs and you are forced to issue a cold-reset (holding down power button). This might indicate that the OS is not even reaching the point of asking for a reset because it is stuck waiting on something else (hence why it could be a kernel root-port related issue with reset under the presence of errors which trigger interrupts).

I would suggest trying the LTS kernel, and seeing if it useable and if there is any reset behavior difference. I do know that skylake took a long time to be useable in linux, and so I am unsure if the LTS kernel will work for that hardware, but it will provide some extra data points that may help.

EDIT: Also check your BIOS settings and see if you have PCIe ASPM enabled. If so, try disabling it. If there are separate bios settings for L0s and L1, disable both.

Edit2:: Additionally, make sure you have intel-ucode installed and enabled in your boot loader. The reset flows are controlled in SunrisePoint by firmware that lives in the PMC (power-management controller). This gets loaded by BIOS, so also check your laptop vendor for BIOS updates, as there could be fixes available.

Last edited by blahhumbug (2017-05-01 15:49:58)

teffysam · 2018-07-20 08:51:45

Hi, I'm brand new to Arch but not Linux, so please excuse my ignorance if I've said anything wrong. I'm trying to install Arch and I've run into the same PCIE bus error on the same port (00:1c.5), but in my case I can't even do anything about it . I've been using KDE Neon till now and used to have the same problem on boot, but I managed to add pci=nomsi to my grub and this made the error not show up on boot.

But I can't seem to do the same from my live USB install of Arch and the error just keeps printing on screen wherever I am so I can't edit files too (not sure if those printed errors will end up saving in the grub file too, besides I am not even sure if the grub file on the Live USB is writable and whether changes will even be saved on the next boot...) . I also dual boot Windows 10. Any help would be great, I really want to try out Arch. I heard the community is great too. I posted the same problem on Kde forums and no one gives a damn there.

I've also read the replies above, PCIe ASPM doesn't show up on my BIOS. Is it possible to install intel-ucode in the storm of errors being printed on my console? Or is is a fundamental problem with my laptop? I can't remove Windows as I use that for my games and have a ton of stuff there too.

seth · 2018-07-20 11:06:09

Please do not necrobump.
Ensure windows fastboot is off, https://www.tenforums.com/tutorials/418 … -10-a.html
If that's settled, please open a new thread, post the actual message and an lspci output.

The "error" is none, there're problems to communicate w/ the PCI device but the call is repeated and the error corrected. (Ie. a "loose contact", works, works not, works…)

WorMzy · 2018-07-20 11:19:26

As Seth notes, please do not necrobump.

https://wiki.archlinux.org/index.php/Co … bumping.22

Closing.

Arch Linux

#1 2017-04-29 11:42:22

PCIe Bus Error

#2 2017-04-29 18:33:32

Re: PCIe Bus Error

#3 2017-04-29 19:18:41

Re: PCIe Bus Error

#4 2017-04-29 20:42:22

Re: PCIe Bus Error

#5 2017-04-29 23:15:21

Re: PCIe Bus Error

#6 2017-04-29 23:16:54

Re: PCIe Bus Error

#7 2017-04-30 05:41:07

Re: PCIe Bus Error

#8 2017-04-30 16:25:14

Re: PCIe Bus Error

#9 2017-05-01 12:21:18

Re: PCIe Bus Error

#10 2017-05-01 12:30:42

Re: PCIe Bus Error

#11 2017-05-01 12:51:08

Re: PCIe Bus Error

#12 2017-05-01 13:56:54

Re: PCIe Bus Error

#13 2017-05-01 14:10:49

Re: PCIe Bus Error

#14 2017-05-01 15:02:59

Re: PCIe Bus Error

#15 2018-07-20 08:51:45

Re: PCIe Bus Error

#16 2018-07-20 11:06:09

Re: PCIe Bus Error

#17 2018-07-20 11:19:26

Re: PCIe Bus Error

Board footer