From: keith.busch@intel.com (Keith Busch)
Subject: Fwd: [Bug 196907] [Regression] New default s2idle does not work on Dell XPS 13 9360 with Ubuntu 16.04.3 LTS (Xenial Xerus)
Date: Mon, 9 Oct 2017 16:22:15 -0600 [thread overview]
Message-ID: <20171009222215.GF19329@localhost.localdomain> (raw)
In-Reply-To: <5479293.9hsiVanX3S@aspire.rjw.lan>
On Tue, Oct 10, 2017@12:01:33AM +0200, Rafael J. Wysocki wrote:
> On Tuesday, October 10, 2017 12:14:14 AM CEST Keith Busch wrote:
> > On Mon, Oct 09, 2017@11:52:26PM +0200, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > We are seeing a resume issue with a Hynix SSD (PC300 NVMe SK hynix 512GB)
> > > with respect to suspend-to-idle (S3 resume works for the reporter,
> > > interestingly enough). It appears to be limited to Hynix and to that
> > > specific SSD ATM.
> > >
> > > Also it is reported to work in 4.11-rc1 and it already is failing in 4.13,
> > > so it looks like something between the two broke it.
> > >
> > > Any ideas of what that might be?
> > >
> > > Or anything we should try/test to narrow it down?
> > >
> > > Any help will be appreciated.
> >
> > I'd start with the APST feature and see if disabling that helps.
> > That can be done with the nvme_core module param:
> >
> > default_ps_max_latency_us=0
> >
>
> We've tried that and it doesn't help.
But it wasn't done correctly according to the notes on the
bugzilla. May be just a typo, but want make sure: it says they used
"nvme.default_ps_max_latency_us=0" on the kernel's command line, which
doesn't mean anything. It's "nvme_core" that provides that module
parameter.
next prev parent reply other threads:[~2017-10-09 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 21:52 Fwd: [Bug 196907] [Regression] New default s2idle does not work on Dell XPS 13 9360 with Ubuntu 16.04.3 LTS (Xenial Xerus) Rafael J. Wysocki
2017-10-09 22:14 ` Keith Busch
2017-10-09 22:01 ` Rafael J. Wysocki
2017-10-09 22:22 ` Keith Busch [this message]
2017-10-09 22:13 ` 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=20171009222215.GF19329@localhost.localdomain \
--to=keith.busch@intel.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.