From: Keith Busch <keith.busch@intel.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>, Sagi Grimberg <sagi@grimberg.me>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-nvme <linux-nvme@lists.infradead.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Mario Limonciello <mario_limonciello@dell.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] nvme: Change our APST table to be no more aggressive than Intel RSTe
Date: Fri, 19 May 2017 17:42:48 -0400 [thread overview]
Message-ID: <20170519214248.GE7850@localhost.localdomain> (raw)
In-Reply-To: <CALCETrWCLAZp4yn7gAm2WMMPgsWLzb_5g9_r66a_bKOsDcwGnA@mail.gmail.com>
On Fri, May 19, 2017 at 11:24:39AM -0700, Andy Lutomirski wrote:
> On Fri, May 19, 2017 at 7:18 AM, Keith Busch <keith.busch@intel.com> wrote:
> > On Thu, May 18, 2017 at 11:35:05PM -0700, Christoph Hellwig wrote:
> >> On Thu, May 18, 2017 at 06:13:55PM -0700, Andy Lutomirski wrote:
> >> > a) Leave the Dell quirk in place until someone from Dell or Samsung
> >> > figures out what's actually going on. Add a blanket quirk turning off
> >> > the deepest sleep state on all Intel devices [1] at least until
> >> > someone from Intel figures out what's going on -- Hi, Keith! Deal
> >> > with any other problems as they're reported.
> >>
> >> I think we should just blacklist the 60p entirely. It also seems to
> >> corrupt data 100% reliable when used with XFS.
> >
> > I assume you're talking about the 600p/p3100. That family of devices
> > prefer 4k alignment, and patch below will enforce that, fixing all
> > access issues. I wasn't planning to post it because my understanding is
> > an imminent f/w update will make it unnecessary.
> >
> > I understand there is a different issue specific to the KBL NUC platforms
> > that exposes some other errata, but I don't know much about that.
>
> We can quirk by firmware version. The report said:
>
> vid : 0x8086
> ssvid : 0x8086
> sn : BTPY63850F281P0H
> mn : INTEL SSDPEKKW010T7
> fr : PSF104C
>
> Any chance you can check what firmware versions have the issue?
All publicly available f/w's may experience the reported issues. The
update that is believed to resolve all known isues is currently in the
validation process and will be released with an update tool as soon as
that completes, but I have not been provided a specific release date.
prev parent reply other threads:[~2017-05-19 21:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 4:06 [PATCH] nvme: Change our APST table to be no more aggressive than Intel RSTe Andy Lutomirski
2017-05-12 13:58 ` Mario.Limonciello
2017-05-12 14:04 ` Andy Lutomirski
2017-05-12 14:34 ` Mario.Limonciello
2017-05-12 23:49 ` Andy Lutomirski
2017-05-15 15:51 ` Mario.Limonciello
2017-05-13 12:27 ` Andy Lutomirski
2017-05-15 16:11 ` Mario.Limonciello
2017-05-19 1:18 ` Andy Lutomirski
2017-05-19 1:13 ` Andy Lutomirski
2017-05-19 1:32 ` Mario.Limonciello
2017-05-19 1:37 ` Andy Lutomirski
2017-05-19 6:35 ` Christoph Hellwig
2017-05-19 14:18 ` Keith Busch
2017-05-19 14:15 ` Christoph Hellwig
2017-05-19 18:24 ` Andy Lutomirski
2017-05-19 21:42 ` Keith Busch [this message]
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=20170519214248.GE7850@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=luto@kernel.org \
--cc=mario_limonciello@dell.com \
--cc=sagi@grimberg.me \
/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