linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vidya Sagar <vidyas@nvidia.com>
To: "Kenneth R. Crudup" <kenny@panix.com>,
	Bjorn Helgaas <helgaas@kernel.org>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Commit 4257f7e0 ("PCI/ASPM: Save/restore L1SS Capability for suspend/resume") causing hibernate resume failures
Date: Wed, 30 Dec 2020 12:25:01 +0530	[thread overview]
Message-ID: <73f7f072-583c-cf54-a034-55e2f1990c52@nvidia.com> (raw)
In-Reply-To: <cb32b83e-108b-47e5-812-9c26712de9a0@panix.com>

Ideally Bjorn's patch should have worked.
Could you please collect 'sudo lspci -vv' (please don't forget to give 
sudo) with Bjorn's patch before and after hibernate?
Also, is it right to say that with policy set to "performance" there is 
no issue during hibernate/resume?

- Vidya Sagar

On 12/28/2020 12:00 PM, Kenneth R. Crudup wrote:
> External email: Use caution opening links or attachments
> 
> 
> On Sun, 27 Dec 2020, Kenneth R. Crudup wrote:
> 
>> I'll try your patch after the revert and see if anything changes.
> 
> I just realized today's patch makes no sense if it's reverted, so nevermind.
> 
>          -Kenny
> 
> --
> Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Orange County CA
> 

  reply	other threads:[~2020-12-30  6:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28  4:05 Commit 4257f7e0 ("PCI/ASPM: Save/restore L1SS Capability for suspend/resume") causing hibernate resume failures Bjorn Helgaas
2020-12-28  4:41 ` Kenneth R. Crudup
2020-12-28  5:43 ` Kenneth R. Crudup
2020-12-28  6:30   ` Kenneth R. Crudup
2020-12-30  6:55     ` Vidya Sagar [this message]
2021-01-22 20:11 ` Kenneth R. Crudup
2021-01-27 15:50   ` Bjorn Helgaas
2021-01-27 16:00     ` Kenneth R. Crudup
2021-01-27 16:03     ` Kenneth R. Crudup

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=73f7f072-583c-cf54-a034-55e2f1990c52@nvidia.com \
    --to=vidyas@nvidia.com \
    --cc=helgaas@kernel.org \
    --cc=kenny@panix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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 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).