Please file a new bug if it's a different device.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1803692
Title:
bionic 4.15 nvme regression from trusty 4.4 with two identical devices
Ahhh, but from what I am seeing here
https://github.com/torvalds/linux/blob/master/drivers/nvme/host/core.c,
this quirks wouldn't work in my case, right? :(
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi,
I am getting exactly that one:
Duplicate cntlid 0 with nvme0, rejecting
Removing after probe failure status: -22
And indeed it is ADATA S70. So you are saying, if I add that and build
the kernel, it might work? Sounds good, I will give a try, thank you so
much for the direction!
--
You
Do you have messages like this in the kernel boot log?
[ 2.072227] nvme nvme1: ignoring ctrl due to duplicate subnqn
(nqn.2017-12.org.nvmexpress:uuid:----).
[ 2.072231] nvme nvme1: Removing after probe failure status: -22
It looks like since 5.2
Hi,
I am still hitting this same problem on Ubuntu 20.04.02 with 2 AData XPG
S70 disks. I've tried to hide them behind RAID but this is not working
as well, I am not sure whether this is is the issue:
https://superuser.com/questions/1605038/nvme-raid-on-linux-with-amd-
ryzen-line-up-possible
I
A fix for those who has this issue with Intel SSD / NVMe drives:
Firmware update with Intel SSD Data Center Tool (DCT)
https://downloadcenter.intel.com/search?keyword=SSD+Firmware+Update+Tool
wget
https://downloadmirror.intel.com/28999/eng/Intel_SSD_Data_Center_Tool_3.0.20_Linux.zip
-O
** Tags added: ubuntu-certified
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1803692
Title:
bionic 4.15 nvme regression from trusty 4.4 with two identical devices
The fix is available in the at least the 4.18 branch:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/log/drivers/nvme/host?h=Ubuntu-hwe-4.18.0-21.22_18.04.1
This is good enough for our needs so closing the issue.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
The fix has been merged to the mainline kernel tree as commit
6299358d198a0635da2dd3c4b3ec37789e811e44.
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-fixed-upstream
--
You received this bug notification
A workaround in the kernel nvme driver has been tested and proposed:
http://lists.infradead.org/pipermail/linux-
nvme/2018-November/021366.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I tried to force install the Intel firmware which contains the fix but
that did not work as the utility refused to overwrite the custom Lenovo
firmware. I opened a support case with Lenovo referencing the Intel fix
but the case was closed with 'we don't support Linux' :( Perhaps it
would be
I have changed the bug to 'invalid' as I do not expect a fix in Ubuntu
for the firmware bug.
https://downloadcenter.intel.com/download/28320/Known-Issue-Intel-SSD-
760p-Pro-7600p-Series-SubNQN-Conflict-on-Linux
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received
The linked thread on fedoraproject.org indicates that a firmware update
for the device will be necessary to resolve this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1803692
The issue exists upstream:
$ uname -r
4.20.0-042000rc3-generic
$ dmesg | grep nvme
[1.857861] nvme nvme0: pci function :02:00.0
[1.857900] nvme nvme1: pci function :04:00.0
[1.968167] nvme0n1: p1 p2 p3 p4
[2.072227] nvme nvme1: ignoring ctrl due to duplicate subnqn
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.20 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
apport information
** Tags added: apport-collected trusty
** Description changed:
I have a system containing two identical nvme devices. When booting a
trusty PXE image with kernel 4.4.0-38-generic both devices are detected
and available:
# nvme id-ctrl /dev/nvme0
NVME Identify
16 matches
Mail list logo
