Fix can be found in Eoan, mark this as fix-released.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788035
Title:
nvme:
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788035
Title:
nvme: avoid cqe corruption
To manage notifications about this bug go to:
Some updates here: the patch was released in the -proposed pocket, and
is available in the kernel 4.4.0-1075-aws - to enable the proposed
repository please see this
https://wiki.ubuntu.com/Testing/EnableProposed. The plan is to have this
kernel released in the first week of February, after all
I'm investigating this issue, and built a kernel with the following two
patches:
a)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7776db1ccc1
b) A debug patch present in
http://lists.infradead.org/pipermail/linux-nvme/2017-February/008498.html
The idea of the
We encountered an instance that had a nvme failure very early on in boot
today. I've updated our internal Canonical case as well as our Amazon
case on this, but posting relevant details here as well for consistency:
# uname -a
Linux XXX 4.4.0-1069-aws #79-Ubuntu SMP Mon Sep 24 15:01:41 UTC 2018
As this issue seems far from being solved and I dont see any progess
coming from canonical neither aws which I find quite annoying
considering the impact for them today we switched back our instances to
m4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
We can confirm that this patch does not solve the issue as we are still
seeing the same dmesg pattern with the 4.4.0-1069-aws kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788035
Title:
We did not have a series of steps to reproduce this. Just left a server
running without much happening and boom.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788035
Title:
nvme: avoid cqe
I didn't find so far way to reproduce the issue systematically.
It doesn't seem to me load related as nodes with lower load crash more
often then ones with high load.
But I can confirm that the fix released with ubuntu 4.4.0-135 kernel
doesn't fix the issue.
As this morning (17/10/28) we faced
So far the best I could reach is get the kernel call trace but not
crashing the node yet.
Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.306845] INFO: task java:1932
blocked for more than 120 seconds.
Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.308573] Not tainted
4.4.0-1069-aws
I have the same.
I have the less loaded instances in my real environment crashing and
the environment where I am trying to reproduce the issue stressing it
not crashing.
I am finding a way to reproduce it.
How did you reproduce it?
--
You received this bug notification because you are a
We were reproducing this multiple times a day on multiple of our EC2 M5
instances. Interesting anecdote, our least loaded instances produced the
bug more often than our heavily loaded instances.
We've since switched to M4 servers and do not have time to flip back and
help test this right now.
--
I am trying to reproduce it.
Has anyone tried it ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788035
Title:
nvme: avoid cqe corruption
To manage notifications about this bug go to:
i am also still seeing this bug after the fix.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788035/+attachment/5193195/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello, it seems that this issue or a similar one still occurs despite
the fix.
Please find syslog output here after.
Best regards
** Attachment added: "Bug still present on 4.4.0-135"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788035/+attachment/5193088/+files/nvme_4.4.0.log
--
This bug was fixed in the package linux - 4.4.0-135.161
---
linux (4.4.0-135.161) xenial; urgency=medium
* linux: 4.4.0-135.161 -proposed tracker (LP: #1788766)
* [Regression] APM Merlin boards fail to recover link after interface down/up
(LP: #1785739)
- net: phylib:
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 the problem still exists,
change the tag
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788035
Title:
nvme: avoid cqe corruption
To manage notifications
** Tags added: kernel-da-key xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788035
Title:
nvme: avoid cqe corruption
To manage notifications about this bug go to:
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
20 matches
Mail list logo
