linux-kernel - [REGRESSION] PCI v5.5-rc1 breaks google kevin

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-next>] [day] [month] [year] [list]

Message-ID: <58ce5534-64bd-4b4b-bd60-ed4e0c71b20f@gmail.com>
Date:   Thu, 12 Dec 2019 00:38:35 +0100
From:   Vicente Bergas <vicencb@...il.com>
To:     Bjorn Helgaas <bhelgaas@...gle.com>,
        Shawn Lin <shawn.lin@...k-chips.com>,
        Heiko Stuebner <heiko@...ech.de>,
        Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>,
        Heiner Kallweit <hkallweit1@...il.com>,
        "\"Rafael J. Wysocki\"" <rafael.j.wysocki@...el.com>
Cc:     Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        Andrew Murray <andrew.murray@....com>,
        Philipp Zabel <p.zabel@...gutronix.de>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        "Stefan Mätje" <stefan.maetje@....eu>,
        Frederick Lawler <fred@...dlawl.com>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>,
        <linux-pci@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-rockchip@...ts.infradead.org>,
        <linux-arm-kernel@...ts.infradead.org>
Subject: [REGRESSION] PCI v5.5-rc1 breaks google kevin

Hi,
since v5.5-rc1 the google kevin chromebook does not boot.
Git bisect reports 
5e0c21c75e8c PCI/ASPM: Remove pcie_aspm_enabled() unnecessary locking
as the first bad commit.

In order to revert it from v5.5-rc1 i had to also revert some dependencies:
5e0c21c75e8c08375a69710527e4a921b897cb7e
aff5d0552da4055da3faa27ee4252e48bb1f5821
35efea32b26f9aacc99bf07e0d2cdfba2028b099
687aaf386aeb551130f31705ce40d1341047a936
72ea91afbfb08619696ccde610ee4d0d29cf4a1d
87e90283c94c76ee11d379ab5a0973382bbd0baf
After reverting all of this, still no luck.
So, either the results of git bisect are not to be trusted, or
there are more bad commits.

By "does not boot" i mean that the display fails to start and
the display is the only output device, so debugging is quite difficult.

v5.5-rc1 as is (reverting no commits at all) works fine when disabling PCI:
# CONFIG_PCI is not set

Regards,
  Vicente.