linux-kernel - Re: [Bug 216877] New: Regression in PCI powermanagement breaks resume after suspend

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: <20230102171516.GA783946@bhelgaas>
Date:   Mon, 2 Jan 2023 11:15:16 -0600
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Vidya Sagar <vidyas@...dia.com>
Cc:     Thomas Witt <kernel@...t.link>, linux-kernel@...r.kernel.org,
        linux-pci@...r.kernel.org
Subject: Re: [Bug 216877] New: Regression in PCI powermanagement breaks
 resume after suspend

Thank you very much for your report and all the work of bisecting,
Thomas!  If you have a chance, can you collect the "sudo lspci -vv"
output (the one attached doesn't include the ASPM info, probably
because lspci wasn't run as root), and also a complete dmesg log from
before the suspend?

On Mon, Jan 02, 2023 at 02:02:51PM +0000, bugzilla-daemon@...nel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=216877
> 
>             Bug ID: 216877
>            Summary: Regression in PCI powermanagement breaks resume after
>                     suspend
>     Kernel Version: 6.0.0-rc1
> 
> Created attachment 303512
>   --> https://bugzilla.kernel.org/attachment.cgi?id=303512&action=edit
> output of git bisect log
> 
> After commit 5e85eba6f50dc288c22083a7e213152bcc4b8208 "PCI/ASPM:
> Refactor L1 PM Substates Control Register programming" my Laptop
> does not resume PCI devices back from suspend.
> 
> My Laptop is a Tuxedo Infinitybook S 14 v5, as far as I can tell
> they use a Clevo L140CU Mainboard.
> 
> The main symptom is:
> iwlwifi 0000:02:00.0: Unable to change power state from D3hot to D0, device inaccessible
> nvme 0000:03:00.0: Unable to change power state from D3hot to D0, device inaccessible
> 
> after that, the level of interaction I still have with the laptop
> varies, but It cannot run dmesg and it cannot do a clean reboot. The
> issue occurs on every suspend/resume cycle.