** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
Got it working 2nd try, enabling -proposed in Xenial resolved the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661131
Title:
kernel crash when NVMe drive inserted in one slot
To manage
May have spoken too soon, found server went into a kernel panic after I
got back from lunch. There's some complaints about the controller so I
am going to try the 4.4.47 kernel again to be sure it's not the
hardware.
Is there anything that needs to be ran besides "apt-get update" after
enabling
Sorry for the delay, had to wait for another issue to be debugged before
I could take over the hardware again. I enabled -proposed and performed
an apt-get update and fix is working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The proposed Xenial kernel now has the 4.4.47 updates and is in the
-proposed repository.
Would it be possible for you to test this latest kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank
v4.4.47 kernel has the fix and is working with the NVMe drive in the
"bad" slot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661131
Title:
kernel crash when NVMe drive inserted in one slot
To
I was able to git clone the v4.4.47 kernel over to the machine having
issues. When trying to apply the patches after 0001, it's unable to
locate the file to patch for some. I am seeing this same error on
another machine I've previously successfully upgraded to the 4.4.47
kernel with the same
Hi Joseph,
To confirm, in order to correctly install the v4.4.47 kernel, we need to
do the git clone and apply the patches before installing the kernel .deb
packages correct? My colleague was only copying the .deb packages which
may be causing us to see the root device timeout. I was able to
We tried with the 4.4.47 kernel but when booting it gives up waiting on
the root device. We are troubleshooting to try and get it to boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661131
Title:
Can you also test the latest upstream 4.4 kernel? That will tell us if
the fix in mainline was already cc'd to stable or if we need to perform
a "Reverse" bisect.
The 4.4.47 kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.47/
--
You received this bug
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661131
Title:
kernel crash when NVMe drive inserted in one slot
To manage notifications about this bug go to:
The mainline kernel seems to have resolved the issue so far. We're
running some IO just to make sure it's stable. I will update the tag
once we have confirmation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've asked the engineer to try the latest v4.10-rc6 kernel. This is
their first test with 16.04.1, so unknown if it works with previous
kernel version. I've asked them to check older versions to see if it
exists.
I'll update the tag and comment when I hear back from them. Thanks for
the
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.10
15 matches
Mail list logo
