I tested the most recent proposed kernel (4.4.0-138) using the same
power faulting methodology as before. Everything looks good. I updated
the tag.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member
To clarify -- I ran the testing with all of your kernel packages
installed and live, except for cloud-tools, which we don't use on HP
hardware (haha).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hey Joseph! I just ran one of our machines through our drive power
faulting test. It survived 5 hotplug events without crashing. Usually
it's 100% repro of the crash. Seems to work. Thanks much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Attaching logs gathered by the apport utility. This is for one of our HP
boxes running kernel 4.4.0-131.
** Attachment added: "apport.linux.4RjMFB.apport"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791790/+attachment/5187217/+files/apport.linux.4RjMFB.apport
** Changed in: linux
Public bug reported:
A bug was introduced when backporting the fix for
http://bugs.launchpad.net/bugs/1597908. This bug exists in all Ubuntu
16.04 LTS 4.4 kernels >= 4.4.0-36, and many other non-LTS kernels.
This patch changes the context in which timeout work is scheduled for
block devices in
This bug is hitting for me on 16.04 LTS running kernel 4.13.0-16. udev
is stuck in the following stack:
[] blk_mq_freeze_queue_wait+0x4b/0xb0
[] blk_mq_freeze_queue+0x1a/0x20
[] __nvme_revalidate_disk+0x7a/0x3f0 [nvme_core]
[] nvme_revalidate_disk+0x53/0x90 [nvme_core]
[]
