Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1654262
| From | Andy Lutomirski <luto@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 2/2] nvme: Quirk APST on Intel 600P/P3100 devices |
| Date | 2017-05-31 16:00 +0200 |
| Message-ID | <tNcki-5yl-21@gated-at.bofh.it> (permalink) |
| References | <tKMDD-84u-5@gated-at.bofh.it> <tKMDE-84u-13@gated-at.bofh.it> <tMRfQ-DG-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH 2/2] nvme: Quirk APST on Intel 600P/P3100 devices Keith Busch <keith.busch@intel.com> - 2017-05-30 17:30 +0200 Re: [PATCH 2/2] nvme: Quirk APST on Intel 600P/P3100 devices Andy Lutomirski <luto@kernel.org> - 2017-05-31 16:00 +0200
csiph-web