ASPM Errors Related to USB 3.1 root port [Solved]

renordw · 2018-10-26 06:28:18

I have a dual boot with Windows and Arch with BTRFS and systemd-boot.

Somewhere in the past 2 weeks, when I am starting up, I consistently get these errors:

$ journalctl -p 3 -xb 
Oct 25 18:50:37 archlinux kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Oct 25 18:50:37 archlinux kernel: pcieport 0000:00:1c.4:   device [8086:a294] error status/mask=00000001/00002000
Oct 25 18:50:37 archlinux kernel: pcieport 0000:00:1c.4:    [ 0] Receiver Error         (First)
Oct 25 18:50:37 archlinux kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Oct 25 18:50:37 archlinux kernel: pcieport 0000:00:1c.6:   device [8086:a296] error status/mask=00000001/00002000
Oct 25 18:50:37 archlinux kernel: pcieport 0000:00:1c.6:    [ 0] Receiver Error         (First)

I am finding it difficult to diagnose because everything seems to be working fine. For the sake of completeness, the device in question is:

# lspci -v

00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 125
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: None
	Memory behind bridge: f7100000-f71fffff [size=1M]
	Prefetchable memory behind bridge: None
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: ASUSTeK Computer Inc. 200 Series PCH PCI Express Root Port
	Capabilities: [a0] Power Management version 3
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Access Control Services
	Capabilities: [220] Secondary PCI Express <?>
	Kernel driver in use: pcieport

00:1c.6 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #7 (rev f0) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 126
	Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
	I/O behind bridge: None
	Memory behind bridge: f7000000-f70fffff [size=1M]
	Prefetchable memory behind bridge: None
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: ASUSTeK Computer Inc. 200 Series PCH PCI Express Root Port
	Capabilities: [a0] Power Management version 3
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Access Control Services
	Capabilities: [220] Secondary PCI Express <?>
	Kernel driver in use: pcieport

Last edited by renordw (2018-10-31 06:44:26)

anuj62176 · 2018-10-26 07:22:09

Try adding "pci=noaer" without quotes in the kernel parameters.
This turns off advanced error reporting for pci devices.

renordw · 2018-10-26 07:34:16

Thanks. That definitely worked. I guess it's concerning that it's giving off these errors, I forgot to mention -- I currently don't even have anything plugged into PCI slots.

seth · 2018-10-26 07:46:03

noaer simply suppresses the message. These are physical communication issues, detected and corrected.

lspci -tv

renordw · 2018-10-26 07:53:13

So then everything is working fine?

lspci -tv                                                                                                                                            ✔  5458  01:51:14

-[0000:00]-+-00.0  Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers
           +-02.0  Intel Corporation Device 3e92
           +-14.0  Intel Corporation 200 Series PCH USB 3.0 xHCI Controller
           +-16.0  Intel Corporation 200 Series PCH CSME HECI #1
           +-17.0  Intel Corporation 200 Series PCH SATA controller [AHCI mode]
           +-1b.0-[01]--
           +-1c.0-[02]--
           +-1c.2-[03]----00.0  Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter
           +-1c.4-[04]----00.0  ASMedia Technology Inc. Device 2142
           +-1c.6-[05]----00.0  ASMedia Technology Inc. Device 2142
           +-1d.0-[06]--
           +-1f.0  Intel Corporation Device a2c9
           +-1f.2  Intel Corporation 200 Series PCH PMC
           +-1f.3  Intel Corporation 200 Series PCH HD Audio
           \-1f.4  Intel Corporation 200 Series PCH SMBus Controller

seth · 2018-10-26 08:21:48

Not "fine", but working.
Seems to be some USB controller behind those ports, "lsusb"?

renordw · 2018-10-26 08:56:22

Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05dc:a838 Lexar Media, Inc. JumpDrive Tough
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0b05:1872 ASUSTek Computer, Inc. 
Bus 001 Device 004: ID 0b05:185c ASUSTek Computer, Inc. 
Bus 001 Device 003: ID 2516:0004 Cooler Master Co., Ltd. Storm QuickFire Rapid Mechanical Keyboard
Bus 001 Device 002: ID 04d9:fc15 Holtek Semiconductor, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

seth · 2018-10-26 12:45:14

I assume one of these devices generate the traffic

Bus 001 Device 005: ID 0b05:1872 ASUSTek Computer, Inc. 
Bus 001 Device 004: ID 0b05:185c ASUSTek Computer, Inc. 
Bus 001 Device 003: ID 2516:0004 Cooler Master Co., Ltd. Storm QuickFire Rapid Mechanical Keyboard
Bus 001 Device 002: ID 04d9:fc15 Holtek Semiconductor, Inc.

For a quick start, you could remove all external devices (keyboard and jumpdrive?)

You should also provide some context, ie. the complete journal of the boot (the surrounding messages might provide further insight when this happens, thus what likely contenders are - and also whether there're other issues that might cause massive traffic on the bus or similar)

renordw · 2018-10-28 20:23:40

Alright, sorry it's taken a few days, but I've narrowed it down.

No matter what I unplug I still get the same errors, so I went into the BIOS. When I disable the USB's 3.1 hub "ASMEDIA FRONT", which is the one that is controlled by an extension cord, the error goes away.

The weirdest part is that I still get the error, even if the extension cord is unplugged!!!

For what it's worth this is the motherboard I have:

https://dlcdnets.asus.com/pub/ASUS/mb/L … 082417.pdf

--Correction, the error dates back to when I built the computer in April--

Last edited by renordw (2018-10-28 20:28:06)

renordw · 2018-10-29 06:24:11

I can confirm that these errors only exist when USB3.1 is enabled via BIOS. There are 3 or so different ways I can enable or disable USB3.1, and no matter which way they are disabled the errors (in the middle code segment) go away. When USB3.1 is enabled, then these errors pop back up.

arch linux kernel and date removed for brevity

# journalctl -xbehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

ehci-pci: EHCI PCI platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
uhci_hcd: USB Universal Host Controller Interface driver
xhci_hcd 0000:00:14.0: xHCI Host Controller
xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000000009810
xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.18
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: xHCI Host Controller
usb usb1: Manufacturer: Linux 4.18.16-arch1-1-ARCH xhci-hcd
usb usb1: SerialNumber: 0000:00:14.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 16 ports detected
xhci_hcd 0000:00:14.0: xHCI Host Controller
xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
xhci_hcd 0000:00:14.0: Host supports USB 3.0  SuperSpeed
usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.18
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: xHCI Host Controller
usb usb2: Manufacturer: Linux 4.18.16-arch1-1-ARCH xhci-hcd
usb usb2: SerialNumber: 0000:00:14.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 10 ports detected
xhci_hcd 0000:04:00.0: xHCI Host Controller
xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1c.4:   device [8086:a294] error status/mask=00000001/00002000
pcieport 0000:00:1c.4:    [ 0] Receiver Error         (First)
xhci_hcd 0000:04:00.0: hcc params 0x0200ef81 hci version 0x110 quirks 0x0000000000000010
usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.18
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: xHCI Host Controller
usb usb3: Manufacturer: Linux 4.18.16-arch1-1-ARCH xhci-hcd
usb usb3: SerialNumber: 0000:04:00.0
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
xhci_hcd 0000:04:00.0: xHCI Host Controller
xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 4
xhci_hcd 0000:04:00.0: Host supports USB 3.1 Enhanced SuperSpeed
usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.18
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: xHCI Host Controller
usb usb4: Manufacturer: Linux 4.18.16-arch1-1-ARCH xhci-hcd
usb usb4: SerialNumber: 0000:04:00.0
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
xhci_hcd 0000:05:00.0: xHCI Host Controller
xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 5
pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6
pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
pcieport 0000:00:1c.6:   device [8086:a296] error status/mask=00000001/00002000
pcieport 0000:00:1c.6:    [ 0] Receiver Error         (First)
xhci_hcd 0000:05:00.0: hcc params 0x0200ef81 hci version 0x110 quirks 0x0000000000000010
usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.18
usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb5: Product: xHCI Host Controller
usb usb5: Manufacturer: Linux 4.18.16-arch1-1-ARCH xhci-hcd
usb usb5: SerialNumber: 0000:05:00.0
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
xhci_hcd 0000:05:00.0: xHCI Host Controller
xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 6
xhci_hcd 0000:05:00.0: Host supports USB 3.1 Enhanced SuperSpeed
usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.18
usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb6: Product: xHCI Host Controller
usb usb6: Manufacturer: Linux 4.18.16-arch1-1-ARCH xhci-hcd
usb usb6: SerialNumber: 0000:05:00.0
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
usb: port power management may be unreliable
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic

Last edited by renordw (2018-10-30 22:10:51)

Lone_Wolf · 2018-10-29 12:53:34

https://www.asus.com/Motherboards/ROG-S … Desk_BIOS/

Latest firmware version is 1412 , released on september 29 .
What version are you running ?

renordw · 2018-10-30 00:18:22

Lone_Wolf wrote:

https://www.asus.com/Motherboards/ROG-S … Desk_BIOS/
Latest firmware version is 1412 , released on september 29 .
What version are you running ?

That's the one I'm using.

renordw · 2018-10-30 07:13:49

deleted

Last edited by renordw (2018-10-31 06:11:36)

renordw · 2018-10-31 06:09:18

Well. I have fixed it by mucking with the lspci and setpci.

# setpci -s 1c.6 0x50.B=0x43 #rootport
# setpci -s 4:00.0 0x90.B=0x43 #endpoint
# setpci -s 1.c4 0x50.B=0x43 #rootport
# setpci -s 5:00.0 0x90.B=0x43 #endpoint

They were all set to 40, which is L0S, and need to be L0SL1, which is 43.

Now, I just need to figure out how to set these values at boot.

renordw · 2018-10-31 06:41:36

Alright. It's fixed. If anybody else has this problem this is how you fix it. Instead of outright changing the hex codes, I downloaded a script from http://drvbp1.linux-foundation.org/~mcg … nable-aspm that searches for the defective bits, and changes them based on your defective rootports and endpoints.

The script has a line that says

sleep 3

Make sure to comment it out, or you're going to have to wait 3 seconds for each USB port that is fixed.

Make two (or however many defective USB ports you have) files and renamed them fix-aspm-usb1 and fix-aspm-usb2 (arbitrary but meaningful names), placed them into /usr/bin, and chmodded them both to 755.

Create a systemd service called aspm-fix.service (again arbitrary but meaningful) with the following

[Unit]
Description=Fix ASPM for USB

[Service]
Type=oneshot
ExecStart=fix-aspm-usb1
ExecStart=fix-aspm-usb2

[Install]
WantedBy=multi-user.target

Then enable it

  # systemctl enable aspm-fix

.

Now all my PCIe ports are L0s L1 enabled on boot:

# lspci -vvv | grep 'ASPM.*abled;'                                                                                                          
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+

This is really a frustrating fix since it's a bug in my BIOS. The only caveat is that you have to make sure your BIOS actually enables L0s L1 at the points, or else something bad might happen.

Actually, another caveat is that the actual errors are still getting thrown, since the problems are fixed after systemd starts, which is after BIOS negotiation.

Last edited by renordw (2018-10-31 06:48:01)

Arch Linux

#1 2018-10-26 06:28:18

ASPM Errors Related to USB 3.1 root port [Solved]

#2 2018-10-26 07:22:09

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#3 2018-10-26 07:34:16

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#4 2018-10-26 07:46:03

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#5 2018-10-26 07:53:13

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#6 2018-10-26 08:21:48

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#7 2018-10-26 08:56:22

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#8 2018-10-26 12:45:14

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#9 2018-10-28 20:23:40

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#10 2018-10-29 06:24:11

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#11 2018-10-29 12:53:34

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#12 2018-10-30 00:18:22

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#13 2018-10-30 07:13:49

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#14 2018-10-31 06:09:18

Re: ASPM Errors Related to USB 3.1 root port [Solved]

#15 2018-10-31 06:41:36

Re: ASPM Errors Related to USB 3.1 root port [Solved]

Board footer