From: Thomas Witt <kernel@witt.link>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Vidya Sagar <vidyas@nvidia.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [Bug 216877] New: Regression in PCI powermanagement breaks resume after suspend
Date: Wed, 4 Jan 2023 16:37:46 +0100 [thread overview]
Message-ID: <fa187ea6-eaba-92cd-b2bc-a62d25501826@witt.link> (raw)
In-Reply-To: <20230104150246.GA1068896@bhelgaas>
On 04/01/2023 16:02, Bjorn Helgaas wrote:
> On Wed, Jan 04, 2023 at 09:44:25AM +0100, Thomas Witt wrote:
>> On 04/01/2023 01:30, Bjorn Helgaas wrote:
>>> On Mon, Jan 02, 2023 at 11:15:16AM -0600, Bjorn Helgaas wrote:
>>>> On Mon, Jan 02, 2023 at 02:02:51PM +0000, bugzilla-daemon@kernel.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
>
> BTW, if the bisect is correct, I think the regression actually is in
> v6.1-rc1, where 5e85eba6f50d ("PCI/ASPM: Refactor L1 PM Substates
> Control Register programming") appeared.
>
>>>>> 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.
>>>
>>> Thomas, could you try the debug patch below on top of v6.2-rc1?
>>
>> Thank you for that patch Bjorn, but as far as I can see it does not change
>> anything.
>
> Thanks for testing it. Maybe Vidya will have more ideas. The patch
> below (based on v6.2-rc1) would revert 5e85eba6f50d and 4ff116d0d5fd.
> If 5e85eba6f50d is the culprit, it should fix the regression. It
> would also potentially break L1 substates after resume, so we'd like
> to avoid reverting it if possible.
>
> But the "Unable to change power state from D3hot to D0, device
> inaccessible" symptom suggests that the device is still in D3, which
> would be more like a wakeup issue than an ASPM issue.
>
> Your bisect log said 3e347969a577 ("PCI/PM: Reduce D3hot delay with
> usleep_range()") was "good", but it would be worth double-checking,
> e.g., see if reverting it from v6.2-rc1 makes any difference.
>
> Bjorn
>
> commit 61de2691d549 ("Revert "PCI/ASPM: Refactor L1 PM Substates Control Register programming"")
> parent 1b929c02afd3
> Author: Bjorn Helgaas <bhelgaas@google.com>
> Date: Wed Jan 4 08:38:53 2023 -0600
>
> Revert "PCI/ASPM: Refactor L1 PM Substates Control Register programming"
With this patch on top of 6.2-rc1 suspend/resume works and my PCI
devices come back online.
next prev parent reply other threads:[~2023-01-04 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216877-41252@https.bugzilla.kernel.org/>
2023-01-02 17:15 ` [Bug 216877] New: Regression in PCI powermanagement breaks resume after suspend Bjorn Helgaas
2023-01-04 0:30 ` Bjorn Helgaas
2023-01-04 8:44 ` Thomas Witt
2023-01-04 15:02 ` Bjorn Helgaas
2023-01-04 15:37 ` Thomas Witt [this message]
2023-01-26 19:24 ` Thomas Witt
2023-02-02 20:49 ` Bjorn Helgaas
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa187ea6-eaba-92cd-b2bc-a62d25501826@witt.link \
--to=kernel@witt.link \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=vidyas@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.