From: keith.busch@intel.com (Keith Busch)
Subject: Two M.2 NVMe drives with same NQN, one gets removed
Date: Mon, 26 Nov 2018 08:31:11 -0700 [thread overview]
Message-ID: <20181126153110.GM26707@localhost.localdomain> (raw)
In-Reply-To: <20181126133839.GA4348@dingwall.me.uk>
On Mon, Nov 26, 2018@01:38:39PM +0000, James Dingwall wrote:
> Hi,
>
> We have also encountered this issue but the devices have a customised
> firmware from Lenovo:
>
> # nvme id-ctrl /dev/nvme0
> NVME Identify Controller:
> vid : 0x8086
> ssvid : 0x8086
> sn : BTHH82250N1X1P0E
> mn : INTEL SSDPEKKF010T8L
> fr : L08P
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803692?comments=all
>
> I tried to force install the Intel firmware but that did not work. I
> was fobbed off by Lenovo support with a 'we don't support Linux' even
> after pointing out the upstream Intel fix. Is there any possibility
> of being able to work around this in the nvme code?
>
> Thanks,
> James
Hi James,
According to the resolution discussion here:
https://downloadcenter.intel.com/download/28320/Known-Issue-Intel-SSD-760p-Pro-7600p-Series-SubNQN-Conflict-on-Linux
"
If you purchased your Intel? SSD from an OEM, your firmware version may
have a different naming. Contact your local OEM representative for
latest firmware revisions.
"
Sounds like Lenovo will need to merge the Intel update into their
specific firmware if they haven't already done so.
Thansk,
Keith
next prev parent reply other threads:[~2018-11-26 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 13:38 Two M.2 NVMe drives with same NQN, one gets removed James Dingwall
2018-11-26 15:31 ` Keith Busch [this message]
2018-11-27 7:54 ` Christoph Hellwig
2018-11-27 10:25 ` James Dingwall
2018-11-27 15:01 ` Keith Busch
2018-11-30 11:50 ` James Dingwall
-- strict thread matches above, loose matches on Subject: below --
2018-11-17 0:17 John Van Bockel
2018-11-17 1:33 ` Keith Busch
2018-11-18 19:08 ` John Van Bockel
[not found] ` <CAGmwwfc=g+4h12qMBvRVJoE66Z70kzzfkabjyxLC=d7LZp627A@mail.gmail.com>
2018-11-19 17:00 ` Keith Busch
2018-11-21 21:19 ` John Van Bockel
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=20181126153110.GM26707@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox