** 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/1626894
Title:
nvme drive probe failure
Status in linux package in Ubuntu:
Fix Released
Status in linux source
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/1626894
Title:
nvme drive probe failure
Status in linux package in
I just ran into this issue (2018-01-04) on Amazon AWS. The nvme drive was not
detected on Amazon's Ubunto 16.04. Fixed after running
apt-get update
apt-get upgrade
apt-get dist-upgrade
reboot.
dist-upgrade seems to be the key. lsb_release -a says 16.04.03 now.
--
You received this bug
@Andre,
I believe what happens here is filed at LP: #1678184.
Kernel parameter 'nvme_core.default_ps_max_latency_us=0' can workaround the
issue as a temporary fix.
Please also try other value I suggested in comment #6 in LP: #1678184.
--
You received this bug notification because you are a
Is it possible that this bug could also affects zesty (linux-
image-4.10.0-19-generic)?
For me it feels like this, randomly my system (Dell XPS15 9550, Samsung
NVMe PM951 512GB) hangs and I am unable to execute commands. Even dmesg
is not callable :/ ... I can reproduce this bug most of the times
This bug was fixed in the package linux - 4.8.0-37.39
---
linux (4.8.0-37.39) yakkety; urgency=low
[ Thadeu Lima de Souza Cascardo ]
* Release Tracking Bug
- LP: #1659381
* Mouse cursor invisible or does not move (LP: #1646574)
- drm/nouveau/disp/nv50-: split chid
This bug was fixed in the package linux - 4.4.0-62.83
---
linux (4.4.0-62.83) xenial; urgency=low
[ Thadeu Lima de Souza Cascardo ]
* Release Tracking Bug
- LP: #1657430
* Backport DP MST fixes to i915 (LP: #1657353)
- SAUCE: i915_bpo: Fix DP link rate math
-
Just installed kernel 4.4.0-62-generic from -proposed and both drives
are appearing with no problems in dmesg.
--
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/1626894
Title:
nvme drive
Hmm I tried that earlier today and thought it failed to boot, let me try
-proposed again now.
--
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/1626894
Title:
nvme drive probe failure
> hey @ddstreet I've just tried your kernel at
> https://launchpad.net/~ddstreet/+archive/ubuntu/lp1626894 and it now shows
> both disks for me.
> Please let me know how we can get this moved along. Happy to test.
It's already in -proposed, please see
hey @ddstreet I've just tried your kernel at
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1626894 and it now
shows both disks for me. Please let me know how we can get this moved
along. Happy to test.
--
You received this bug notification because you are a member of Kernel
Packages, which
Seems to be working for me now.
--
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/1626894
Title:
nvme drive probe failure
Status in linux package in Ubuntu:
Confirmed
Status in linux
i does not work with the stock kernel, I work with a patched kernel.
(https://forum.proxmox.com/threads/nvme-storage-issue.31572/page-2#post-159444)
my first results, only Only a few hours old, Are up to now good:
(a skylake Fujitsu D3417-B Mainboard with Intel C236 Chipset)
only one Line in
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
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/1626894
Title:
nvme drive probe failure
Status in linux package in Ubuntu:
Maybe some symptoms with my old mainboard will be helpful for general
debugging this issue:
-The drive was *sometimes* recognised fine at boot in first place, showed with
"lspci" and "nvme list" would give me correct output
-After boot, the drive would go "missing" after a duration of approx. 5
Dan,
unfortunately I can't, as the bug won't show up with my new mainboard
anymore, that's why I suspected it to be chipset-specific (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/comments/36).
roots.
--
You received this bug notification because you are a member of Kernel
Will do, this testing can be tricky since the issue appears randomly (can take
minutes, hours, even a day for me).
Can we review the patch for the issue somewhere as well?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Wayne, Guillaume, roots, Stéphane, can any/all of you test with the
-proposed kernel (using directions from comment 39) to verify the bug is
fixed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Yakkety)
Status: Confirmed => Fix Committed
--
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/1626894
Title:
nvme drive probe failure
Status in linux
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Committed
--
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/1626894
Title:
nvme drive probe failure
Status in linux
For the record, I'm using my SSD on on M2 slot on an Intel NUC
(http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5i3ryk.html).
@ddstreet, I tried to use your kernel but for whatever reason, it won't
zork with my LVM based installation.
--
You received this bug notification because you are
With this Hardware:
a skylake Fujitsu D3417-B Mainboard with Intel C236 Chipset with 64GB DDR4 ECC
RAM and a
E3-1245-v5 XEON and one ADATA SSD M.2 2280 NVMe 1.2 PCIe Gen3x4 128GB XPG
SX8000
with ext4 and thin LVM
I also get this error:
=> [45512.825928] nvme :01:00.0: Failed status:
@All:
In the meantime, I've switched to a different motherboard, where the
issue does not occur _within linux_ anymore (with none of the default
Ubuntu Kernels (4.4.0-53, -57, -59, 4.8.0-32 and 4.9.0 from the mainline
ppa). This applies for both the NVME SSD being hooked to a PCIe-Slot
(via
@Wayne Scott: I succeeded in catching some of those scrolling screen
messages (for another issue) by filming the screen output with my mobile
phone. However, I had to set a high recording framerate (50 or 60Hz).
--
You received this bug notification because you are a member of Kernel
Packages,
Guillaume, roots, Stéphane, can you also test with my PPA kernel from
comment 30? It would help to know if your NVMe failures are also due to
the patches we're reverting, or some other problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu Xenial)
Assignee: Kamal Mostafa (kamalmostafa) => Dan Streetman (ddstreet)
** Changed in: linux (Ubuntu Yakkety)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Kernel
Packages, which is
Yeah, ddstreet's -59 kernel boots just fine and sees my NVMe drives.
Let me know if I can help.
--
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/1626894
Title:
nvme drive probe failure
fyi:
# nvme list
Node SN Model
Version Namespace Usage Format FW Rev
- --
The -40 kernel recommend by jsalisbury faults immediately on boot. The fault
scrolled off the page and I don't know how to capture it, but it had nvme
routines at the end of it.
Note: the existing kernels don't fault, the probes for these drives just fail.
Trying ddstreet's suggestion now, it
Alternately, as this may have been caused by my recent NVMe patches, can those
affeected by this please test with this kernel PPA which is 4.4.0-59 with my
patches reverted:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1626894
--
You received this bug notification because you are a member
For those that are still affected by this bug, can you please test the
following kernel:
http://kernel.ubuntu.com/~jsalisbury/lp1626894/d2b59ee-reverted/
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Fix Released => Confirmed
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of
Odd, but I have another machine with almost the same Intel SSD and it is
running kernel -57 just fine.
--
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/1626894
Title:
nvme drive probe
Another data point...
I have 2 Intel P3700 NVMe SSDs on an x99 chipset motherboard.
For me Ubuntu 16.04 Kernel 4.4.0-53 works, but -57 and -59 both fail to find
the SSDs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Yes please re-open as this bug does not not seem to be fixed due to the last
mentioned change.
See:
[56990.782669] nvme0n1: detected capacity change from 128035676160 to 0
[56990.782652] nvme :03:00.0: Removing after probe failure
[56990.531978] nvme :03:00.0: Failed status: 0x,
Hi,
I second Stephanes post: Please set this bug to NOT FIXED - I'm having
this issue with Ubuntu 16.04, Kernels 4.4.0-53, -57, -58 and 4.9.0.
Drive is a Samsung 960 Pro M2 SSD on a PCIe-M2 - Adapter hooked to a
PCIe16x slot, Gigabyte GA-Z77X-UD3H mobo.
[0.715691] nvme0n1: p1
[ 171.849770]
Please mark as OPEN, see my post below. Thanks.
--
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/1626894
Title:
nvme drive probe failure
Status in linux package in Ubuntu:
Fix Released
Anybody to raise to not fixed ?
--
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/1626894
Title:
nvme drive probe failure
Status in linux package in Ubuntu:
Fix Released
Status in linux
Servers with two controllers. The second one disappear (with a kernel
trace).
> cat /proc/version
Linux version 4.4.0-47-generic (buildd@lcy01-03) (gcc version 5.4.0 20160609
(Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016
After upgrading kernel, my ZFS pool
Hi:
4.4.0-38: My computer was working perfectly.
4.4.0-41 and 4.4.0-42: My computer is "crashing" quite often.
When I go back to 4.4.0-38, my computer does not crash anymore.
When I see a crash, It's like having the nve drive disconnected.
All my environment crashes. If I do a "ls", I see that
This bug was fixed in the package linux - 4.4.0-42.62
---
linux (4.4.0-42.62) xenial; urgency=low
* Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1626894
Title:
nvme drive probe failure
Status in
In trying to confirm bug 1619756 I encountered this using an earlier version of
4.4.0-*.
I can confirm that 4.4.0-41-generic #61 fixes this bug for NVMe on my system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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/1626894
Title:
nvme drive probe failure
Status in linux
Thanks everyone for your quick response and fix of the problem!
I can also confirm that Kamal's Kernel works.
$ cat /proc/version
Linux version 4.4.0-41-generic (root@gomeisa) (gcc version 5.4.0 20160609
(Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #61~lp1626894KamalPatched SMP Mon Sep 26
19:28:58 UTC
Thanks for the quick feedback Stefan. We'll get this fix into the
pipeline immediately.
https://lists.ubuntu.com/archives/kernel-team/2016-September/080123.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
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/1626894
Title:
nvme drive probe failure
Tried it successfully. Thanks, great work!
$ cat /proc/version
Linux version 4.4.0-41-generic (root@gomeisa) (gcc version 5.4.0 20160609
(Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #61~lp1626894KamalPatched SMP Mon Sep 26
19:28:58 UTC 2016
--
You received this bug notification because you are a member
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Yakkety)
Importance: Medium => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The is a patch that may fix this issue without a revert. I built a test
kernel with this patch. It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1626894/PATCHED/
Can you test this kernel and see if it resolves this bug? You will need
to install both the linux-image and
Sorry for the late respond, I didn't have access to the hardware during
the weekend.
I've just tested both kernels and can confirm, that the second one works
correctly:
->%-
root@Ubuntu-1604-xenial-64-minimal ~ # uname -a
Linux Ubuntu-1604-xenial-64-minimal
I've tested both and the second one (30d6592-reverted) worked for me!
The first one (d2b59ee-reverted) got stuck.
Many thanks,
/Stefan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The second one (30d6592-reverted) worked for me, but not the first one.
Thanks,
/Stefan
On Fri, Sep 23, 2016 at 7:41 PM Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> The second test kernel is available at:
> http://kernel.ubuntu.com/~jsalisbury/lp1626894/30d6592-reverted/
>
> Can
The second test kernel is available at:
http://kernel.ubuntu.com/~jsalisbury/lp1626894/30d6592-reverted/
Can you see if either of these kernels resolve this bug?
** Tags added: kernel-da-key xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is
I built a test kernel with commit d2b59ee("UBUNTU: SAUCE: nvme: Don't
suspend admin queue that wasn't created") reverted it can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1626894/d2b59ee-reverted/
Can you see if this kernel resolves this bug?
I'll also build a kernel with
** Also affects: linux (Ubuntu Yakkety)
Importance: Medium
Status: Confirmed
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Yakkety)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Xenial)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1626894
Title:
nvme drive probe failure
Status in linux package in
There are 2 patches that might affect nvme:
UBUNTU: SAUCE: nvme: Don't suspend admin queue that wasn't created
NVMe: Don't unmap controller registers on reset
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1626894
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746845/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746844/+files/uname-a.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Attachment added: "release.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746843/+files/release.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
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/1626894
Title:
nvme drive probe failure
Status in linux package in Ubuntu:
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746841/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Attachment added: "policy.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746842/+files/policy.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
67 matches
Mail list logo
