From: guenther@tum.de (Stephan Günther)
Subject: nvme: controller resets
Date: Tue, 10 Nov 2015 23:02:54 +0100 [thread overview]
Message-ID: <583e84ac40f8b40a0929dbfee15c9322@localhost> (raw)
In-Reply-To: <CAKajsGPLmCiVc4it0bY1qAeLKmrMQMM0FRKcJoAntFb_nE1erA@mail.gmail.com>
On 2015/November/11 03:13, Vedant Lath wrote:
> On Wed, Nov 11, 2015@3:04 AM, Stephan G?nther <guenther@tum.de> wrote:
> > Mine:
> >
> > | NVME Identify Controller:
> > | vid : 0x106b
> > | ssvid : 0x106b
> > | sn : C025xxxxxxxxxxxxxx
> > | mn : APPLE SSD AP0512H
> > | fr : 5.841.01
> >
> > I have reports of other guys with firmware 5.831.01 and 5.844.01. Both
> > have the same problems.
>
> That's a different firmware revision than mine. Mine is 7.831.01. But
> the minor version and patch number is same. :/ Maybe the first digit
> is indicative of the MacBook it is built for?
Educated guess since you have a MacBook7,1.
>
> I have a feeling that this SSD's NVMe implementation is more like a
> draft implementation of the NVMe standard. I am hopeful that future
> firmware upgrades will make it fully compliant with NVMe.
I don't have much hope regarding that. But let's see.
I wrote to opensource at apple.com asking for help in that matter. After
the pleasant surprise with Broadcom/WLAN yesterday I have some hope.
>
> > Are using a MacBook8,1 oder MacBook7,1?
>
> I am using a MacBookAir7,1. It is the 11" MacBook Air (Early 2015)
> model with 256 GB SSD.
next prev parent reply other threads:[~2015-11-10 22:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 14:30 nvme: controller resets Stephan Günther
2015-11-10 15:51 ` Keith Busch
2015-11-10 20:45 ` Stephan Günther
2015-11-10 21:16 ` Vedant Lath
2015-11-10 21:34 ` Stephan Günther
2015-11-10 21:43 ` Vedant Lath
2015-11-10 22:02 ` Stephan Günther [this message]
2015-11-10 22:28 ` Vedant Lath
2015-11-11 21:56 ` Vedant Lath
2015-11-11 22:09 ` Stephan Günther
2015-11-12 14:02 ` Vedant Lath
2015-11-11 22:14 ` Keith Busch
2015-11-12 9:45 ` Vedant Lath
2015-11-12 11:26 ` Vedant Lath
2015-11-16 21:33 ` Stephan Günther
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=583e84ac40f8b40a0929dbfee15c9322@localhost \
--to=guenther@tum.de \
/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