On Thu, May 16, 2013 at 4:10 PM, Phillip Susi <psusi@xxxxxxxxxx> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 05/16/2013 12:42 PM, Bjorn Helgaas wrote:
>> Can you collect a complete dmesg log and complete "lspci -vv" output, please?
> ...
Thanks. The BIOS gave us control over ASPM via _OSC, and you have
these devices where it looks like we should be enabling ASPM, because
it's supported on both ends of the link:
00:1c.1 bridge to [bus 03] ASPM L0s L1, ASPM disabled
03:00.0 ASPM L0s L1, ASPM disabled
00:1c.3 bridge to [bus 05] ASPM L0s L1, ASPM Disabled
05:00.0 ASPM L0s L1, ASPM Disabled
00:1c.4 bridge to [bus 06] ASPM L0s L1, ASPM Disabled
06:00.0 ASPM L0s L1, ASPM Disabled
00:1c.7 bridge to [bus 09] ASPM L0s L1, ASPM Disabled
09:00.0 ASPM L0s L1, ASPM Disabled
You also have this bridge where lspci says "ASPM unknown":
00:01.0 bridge to [bus 01] ASPM unknown
Just out of curiosity, can you collect the output of "lspci -xxxs
00:01.0"? There are only two bits in the Link Capabilities ASPM
support field, and all four encodings are defined, so I'm curious
about why lspci says "unknown".
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
