From: Bjorn Helgaas <firstname.lastname@example.org>
To: Vidya Sagar <email@example.com>
Cc: Thomas Witt <firstname.lastname@example.org>,
Subject: Re: [Bug 216877] New: Regression in PCI powermanagement breaks resume after suspend
Date: Mon, 2 Jan 2023 11:15:16 -0600 [thread overview]
Message-ID: <20230102171516.GA783946@bhelgaas> (raw)
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, email@example.com wrote:
> Bug ID: 216877
> Summary: Regression in PCI powermanagement breaks resume after
> 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.
next parent reply other threads:[~2023-01-02 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org/>
2023-01-02 17:15 ` Bjorn Helgaas [this message]
2023-01-04 0:30 ` [Bug 216877] New: Regression in PCI powermanagement breaks resume after suspend Bjorn Helgaas
2023-01-04 8:44 ` Thomas Witt
2023-01-04 15:02 ` Bjorn Helgaas
2023-01-04 15:37 ` Thomas Witt
2023-01-26 19:24 ` Thomas Witt
2023-02-02 20:49 ` Bjorn Helgaas
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).