*** This bug is a duplicate of bug 1647887 ***
https://bugs.launchpad.net/bugs/1647887
** 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/1639920
Title:
NVMe
*** This bug is a duplicate of bug 1647887 ***
https://bugs.launchpad.net/bugs/1647887
Please note, this is fixed in kernel 4.4.0.57.60, which is in -proposed
right now. See bug 1647887 for more details.
--
You received this bug notification because you are a member of Kernel
Packages,
*** This bug is a duplicate of bug 1647887 ***
https://bugs.launchpad.net/bugs/1647887
> I'd also like to know how or what we need to do in order to proceed
and getting this fix for GA?
I opened bug 1647887 separately for this (I'm working on this problem
for a separate situation and I
Hi Dan,
The test kernel is working. I'm not seeing the issue anymore. Here's
what I've tried with our on-off test:
1.) 1U system with (2x) 2-port NVMe controller with over 500 cycles = no issue
2.) 1U system with (1x) 4-port NVMe controller with over 300 cycles = no issue
3.) 2U system
** Tags removed: need-duplicate-check
--
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/1639920
Title:
NVMe detection failed during bootup
Status in linux package in Ubuntu:
Triaged
Hi Dexter,
before I jump onto the system to debug, can you try this test kernel:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1639920
I think that might fix the problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hi Dan,
Please email me directly dext...@supermicro.com
Thanks,
Dexter
--
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/1639920
Title:
NVMe detection failed during bootup
Status in
Dexter,
is it possible to get access to your ppc system to debug this? Or at
least, can you boot a debug kernel and provide the dmesg? The other
nvme probe timeout issue I'm debugging is looking like it's problem that
wouldn't exist on ppc, so I'd like to look at it on your system
directly.
**
Dan thanks for the update.
--
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/1639920
Title:
NVMe detection failed during bootup
Status in linux package in Ubuntu:
Triaged
Bug
> Is there any update on this issue?
I'm still debugging, but can give a summary of the problem, at least on
the system I'm working on.
First, to address:
> One is the vfree WARNING which indicates that the error paths are not quite
> right
this is a trival fix to the error handling path; it's
Hi Canonical,
Is there any update on this issue?
Thanks,
Dexter
--
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/1639920
Title:
NVMe detection failed during bootup
Status in linux
I should also note, the latest upstream kernel has similar timeout
problems while probing, so this isn't restricted to only the xenial
kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: severity-critical
** Tags added: severity-high
--
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/1639920
Title:
NVMe detection failed during bootup
Status in linux
I bisected to the commit that introduces the failing behavior which is:
df00a7683b417a15a6e695f9a3b200a799b787fa ("nvme: only add a controller
to dev_list after it's been fully initialized")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
--- Comment From craig.w...@us.ibm.com 2016-11-14 11:17 EDT---
dougmill-ibm commented 6 days ago
It appears that one of NVMe drives failed to function correctly during
boot/probe. The 'lspci' output does not show that drive, which means it was
taken after the failure but before recovery
** Package changed: apport (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
16 matches
Mail list logo
