linux-kernel - Re: [GIT PULL] PCI fixes for v4.10

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 2 May 2017 03:54:05 +0200
From:   Lukas Wunner <lukas@...ner.de>
To:     "Raj, Ashok" <ashok.raj@...el.com>
Cc:     Bjorn Helgaas <helgaas@...nel.org>, linux-pci@...r.kernel.org,
        linux-kernel@...r.kernel.org, Yinghai Lu <yinghai@...nel.org>,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>,
        Keith Busch <keith.busch@...el.com>,
        Sinan Kaya <okaya@...eaurora.org>
Subject: Re: [GIT PULL] PCI fixes for v4.10

Hi Ashok,

sorry for the delay, I was swamped with work in the first quarter and am
in the process of slowly going through my backlog...


On Thu, Feb 09, 2017 at 10:46:13AM -0800, Raj, Ashok wrote:
> I did a lspci and captured after a fresh reboot on the slot before 
> attempting a power off via sysfs.
> 
> lspci-at-poweron - values after a cold reset poweron.
> lspci-aft-poweroff - values after a echo 0 > power
> lspci-aft-poweron - values after a echo 1 > power
> 
> i would expect most or all of those values to stay same between poweron
> and after the next sysfs managed poweron. Would be worth taking a look and see 
> if we have any escapes.


(a) Correctable error (Receiver Error) after powering off => harmless.

(b) ASPM L1 enabled on boot, but disabled after powering off and back on
    => I believe Sinan is working on this (+cc).

(c) Autonomous Bandwidth Status is set after powering back on, but the
    speed and width is the same as on boot => harmless.

(d) PME Status is set after powering off and stays set after powering on.
    Weird.  Could you retry with the new pciehp runtime PM series I sent
    out a few hours ago?

Thanks!

Lukas