mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Mario.Limonciello@dell.com>
To: <pmenzel@molgen.mpg.de>, <rjw@rjwysocki.net>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] ACPI: PM: Revert "ACPI / PM: Blacklist Low Power S0 Idle _DSM for Dell XPS13 9360"
Date: Tue, 8 Oct 2019 01:44:17 +0000	[thread overview]
Message-ID: <541d9bfa3ccf45b5b07e35e3eebb72ed@AUSX13MPC105.AMER.DELL.COM> (raw)
In-Reply-To: <97e66464-8407-fd58-21a6-aeb7736dec7b@molgen.mpg.de>

> On 26.09.19 18:08, Mario Limonciello wrote:
> > This reverts part of
> > commit 71630b7a832f ("ACPI / PM: Blacklist Low Power S0 Idle _DSM for
> > Dell XPS13 9360") to remove the S0ix blacklist for the XPS 9360.
> >
> > The problems with this system occurred in one possible NVME SSD when
> > putting system into s0ix.  As the NVME sleep behavior has been
> > adjusted in d916b1be this is expected to be now resolved.
> 
> 1.  Please add, that it was the Hynix(?) SSD.
> 2.  Please add the commit message summary of d916b1be.
> 
>      nvme-pci: use host managed power state for suspend
> 

Rafael, let me know if you want me to adjust the commit message and resubmit
or if you would just handle this task.

> > Cc: 'Paul Menzel <pmenzel@molgen.mpg.de>'
> > BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=196907
> > Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
> 
> Tag it for the stable series? d916b1be (first tag v5.3-rc1) is not tagged for stable.
> 

Although Dell arranged a lot of testing with partners I don't feel d916b1be is a stable
candidate.  Rafael found a corner case with regards to ASPM configuration last minute
in 5.3rcX, I found a another corner case related to order of events and timing around
PC10 entry that's getting fixed in 5.4.

> > ---
> > The particular failing configuration was reported by only ever failed
> > for Paul Menzel, so hopefully he can test on his failing system.
> 
> I successfully tested Linux 5.4-rc1+ with this commit last Friday on the Dell XPS
> 13 9360.
> 
> Tested-by: Paul Menzel <pmenzel@molgen.mpg.de>
> 

Well that's great, appreciate your testing and confirmation.


  reply	other threads:[~2019-10-08  1:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 16:08 Mario Limonciello
2019-10-07 22:44 ` Paul Menzel
2019-10-08  1:44   ` Mario.Limonciello [this message]
2019-10-10  8:51     ` Rafael J. Wysocki

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=541d9bfa3ccf45b5b07e35e3eebb72ed@AUSX13MPC105.AMER.DELL.COM \
    --to=mario.limonciello@dell.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=rjw@rjwysocki.net \
    /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

all inboxes | Powered by JetHome®