Stable Archive on lore.kernel.org
 help / color / Atom feed
* Nominate "PCI/ASPM: Disable ASPM on ASMedia ASM1083/1085 PCIe-to-PCI bridge" for stable
@ 2020-07-31  1:22 Robert Hancock
  2020-08-01 10:36 ` Greg KH
  0 siblings, 1 reply; 2+ messages in thread
From: Robert Hancock @ 2020-07-31  1:22 UTC (permalink / raw)
  To: stable

I would like to nominate the following commit, now in mainline, for
stable. This fixes an issue exposed by commit 66ff14e59e8a ("PCI/ASPM:
Allow ASPM on links to PCIe-to-PCI/PCI-X Bridges") and so should go
into all stable branches which that was backported to (which appears
to be all of the currently maintained releases).

commit b361663c5a40c8bc758b7f7f2239f7a192180e7c
Author: Robert Hancock <hancockrwd@gmail.com>
Date:   Tue Jul 21 20:18:03 2020 -0600

    PCI/ASPM: Disable ASPM on ASMedia ASM1083/1085 PCIe-to-PCI bridge

    Recently ASPM handling was changed to allow ASPM on PCIe-to-PCI/PCI-X
    bridges.  Unfortunately the ASMedia ASM1083/1085 PCIe to PCI bridge device
    doesn't seem to function properly with ASPM enabled.  On an Asus PRIME
    H270-PRO motherboard, it causes errors like these:

      pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected,
type=Data Link Layer, (Transmitter ID)
      pcieport 0000:00:1c.0: AER:   device [8086:a292] error
status/mask=00003000/00002000
      pcieport 0000:00:1c.0: AER:    [12] Timeout
      pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
      pcieport 0000:00:1c.0: AER: can't find device of ID00e0

    In addition to flooding the kernel log, this also causes the machine to
    wake up immediately after suspend is initiated.

    The device advertises ASPM L0s and L1 support in the Link Capabilities
    register, but the ASMedia web page for ASM1083 [1] claims "No PCIe ASPM
    support".

    Windows 10 (build 2004) enables L0s, but it also logs correctable PCIe
    errors.

    Add a quirk to disable ASPM for this device.

    [1] https://www.asmedia.com.tw/eng/e_show_products.php?cate_index=169&item=114

    [bhelgaas: commit log]
    Fixes: 66ff14e59e8a ("PCI/ASPM: Allow ASPM on links to
PCIe-to-PCI/PCI-X Bridges")
    Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=208667
    Link: https://lore.kernel.org/r/20200722021803.17958-1-hancockrwd@gmail.com
    Signed-off-by: Robert Hancock <hancockrwd@gmail.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Nominate "PCI/ASPM: Disable ASPM on ASMedia ASM1083/1085 PCIe-to-PCI bridge" for stable
  2020-07-31  1:22 Nominate "PCI/ASPM: Disable ASPM on ASMedia ASM1083/1085 PCIe-to-PCI bridge" for stable Robert Hancock
@ 2020-08-01 10:36 ` Greg KH
  0 siblings, 0 replies; 2+ messages in thread
From: Greg KH @ 2020-08-01 10:36 UTC (permalink / raw)
  To: Robert Hancock; +Cc: stable

On Thu, Jul 30, 2020 at 07:22:22PM -0600, Robert Hancock wrote:
> I would like to nominate the following commit, now in mainline, for
> stable. This fixes an issue exposed by commit 66ff14e59e8a ("PCI/ASPM:
> Allow ASPM on links to PCIe-to-PCI/PCI-X Bridges") and so should go
> into all stable branches which that was backported to (which appears
> to be all of the currently maintained releases).
> 
> commit b361663c5a40c8bc758b7f7f2239f7a192180e7c
> Author: Robert Hancock <hancockrwd@gmail.com>
> Date:   Tue Jul 21 20:18:03 2020 -0600
> 
>     PCI/ASPM: Disable ASPM on ASMedia ASM1083/1085 PCIe-to-PCI bridge
> 
>     Recently ASPM handling was changed to allow ASPM on PCIe-to-PCI/PCI-X
>     bridges.  Unfortunately the ASMedia ASM1083/1085 PCIe to PCI bridge device
>     doesn't seem to function properly with ASPM enabled.  On an Asus PRIME
>     H270-PRO motherboard, it causes errors like these:
> 
>       pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected,
> type=Data Link Layer, (Transmitter ID)
>       pcieport 0000:00:1c.0: AER:   device [8086:a292] error
> status/mask=00003000/00002000
>       pcieport 0000:00:1c.0: AER:    [12] Timeout
>       pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
>       pcieport 0000:00:1c.0: AER: can't find device of ID00e0
> 
>     In addition to flooding the kernel log, this also causes the machine to
>     wake up immediately after suspend is initiated.
> 
>     The device advertises ASPM L0s and L1 support in the Link Capabilities
>     register, but the ASMedia web page for ASM1083 [1] claims "No PCIe ASPM
>     support".
> 
>     Windows 10 (build 2004) enables L0s, but it also logs correctable PCIe
>     errors.
> 
>     Add a quirk to disable ASPM for this device.
> 
>     [1] https://www.asmedia.com.tw/eng/e_show_products.php?cate_index=169&item=114
> 
>     [bhelgaas: commit log]
>     Fixes: 66ff14e59e8a ("PCI/ASPM: Allow ASPM on links to
> PCIe-to-PCI/PCI-X Bridges")
>     Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=208667
>     Link: https://lore.kernel.org/r/20200722021803.17958-1-hancockrwd@gmail.com
>     Signed-off-by: Robert Hancock <hancockrwd@gmail.com>
>     Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

Now queued up everywhere, thansk!

greg k-h

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-31  1:22 Nominate "PCI/ASPM: Disable ASPM on ASMedia ASM1083/1085 PCIe-to-PCI bridge" for stable Robert Hancock
2020-08-01 10:36 ` Greg KH

Stable Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ https://lore.kernel.org/stable \
		stable@vger.kernel.org
	public-inbox-index stable

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.stable


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git