From: Andy Lutomirski <luto@kernel.org>
To: Keith Busch <keith.busch@intel.com>
Cc: Andy Lutomirski <luto@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
linux-nvme <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 2/2] nvme: Quirk APST on Intel 600P/P3100 devices
Date: Wed, 31 May 2017 06:54:51 -0700 [thread overview]
Message-ID: <CALCETrVa4xvAKyw=-dwRpOExwFrKuVdmMDixaCjaWV0HYtuO5A@mail.gmail.com> (raw)
In-Reply-To: <20170530153516.GB2845@localhost.localdomain>
On Tue, May 30, 2017 at 8:35 AM, Keith Busch <keith.busch@intel.com> wrote:
> On Wed, May 24, 2017 at 03:06:31PM -0700, Andy Lutomirski wrote:
>> They have known firmware bugs. A fix is apparently in the works --
>> once fixed firmware is available, someone from Intel (Hi, Keith!)
>> can adjust the quirk accordingly.
>
> Here's the latest firmware with all the known fixes:
>
> https://downloadcenter.intel.com/download/26491?v=t
>
> I am not 100% sure if this fixes the issue you're quirking, but I think
> it falls under the issues the link initialization and ASPM comments in
> the release notes.
Can you or someone at Intel supply a reliable way to distinguish a
fixed firmware from an unfixed firmware? We have access to the "fr"
string, but I don't know what to do with it.
WARNING: multiple messages have this Message-ID (diff)
From: luto@kernel.org (Andy Lutomirski)
Subject: [PATCH 2/2] nvme: Quirk APST on Intel 600P/P3100 devices
Date: Wed, 31 May 2017 06:54:51 -0700 [thread overview]
Message-ID: <CALCETrVa4xvAKyw=-dwRpOExwFrKuVdmMDixaCjaWV0HYtuO5A@mail.gmail.com> (raw)
In-Reply-To: <20170530153516.GB2845@localhost.localdomain>
On Tue, May 30, 2017@8:35 AM, Keith Busch <keith.busch@intel.com> wrote:
> On Wed, May 24, 2017@03:06:31PM -0700, Andy Lutomirski wrote:
>> They have known firmware bugs. A fix is apparently in the works --
>> once fixed firmware is available, someone from Intel (Hi, Keith!)
>> can adjust the quirk accordingly.
>
> Here's the latest firmware with all the known fixes:
>
> https://downloadcenter.intel.com/download/26491?v=t
>
> I am not 100% sure if this fixes the issue you're quirking, but I think
> it falls under the issues the link initialization and ASPM comments in
> the release notes.
Can you or someone at Intel supply a reliable way to distinguish a
fixed firmware from an unfixed firmware? We have access to the "fr"
string, but I don't know what to do with it.
next prev parent reply other threads:[~2017-05-31 13:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 22:06 [PATCH 0/2] nvme APST fixes Andy Lutomirski
2017-05-24 22:06 ` Andy Lutomirski
2017-05-24 22:06 ` [PATCH 1/2] nvme: Wait at least 6000ms before entering the deepest idle state Andy Lutomirski
2017-05-24 22:06 ` Andy Lutomirski
2017-05-26 8:52 ` Christoph Hellwig
2017-05-26 8:52 ` Christoph Hellwig
2017-05-27 16:08 ` Andy Lutomirski
2017-05-27 16:08 ` Andy Lutomirski
2017-05-27 16:14 ` Linus Torvalds
2017-05-27 16:14 ` Linus Torvalds
2017-05-24 22:06 ` [PATCH 2/2] nvme: Quirk APST on Intel 600P/P3100 devices Andy Lutomirski
2017-05-24 22:06 ` Andy Lutomirski
2017-05-26 8:52 ` Christoph Hellwig
2017-05-26 8:52 ` Christoph Hellwig
2017-05-30 15:35 ` Keith Busch
2017-05-30 15:35 ` Keith Busch
2017-05-31 13:54 ` Andy Lutomirski [this message]
2017-05-31 13:54 ` Andy Lutomirski
2017-06-02 7:23 ` Nicholas Sielicki
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='CALCETrVa4xvAKyw=-dwRpOExwFrKuVdmMDixaCjaWV0HYtuO5A@mail.gmail.com' \
--to=luto@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kai.heng.feng@canonical.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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 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.