This bug was fixed in the package linux - 4.4.0-128.154
---
linux (4.4.0-128.154) xenial; urgency=medium
* linux: 4.4.0-128.154 -proposed tracker (LP: #1772960)
* CVE-2018-3639 (x86)
- x86/cpu: Make alternative_msr_write work for 32-bit code
- x86/bugs: Fix the parameters
I have confirmation from the user who reported this that they have
tested the new kernel 4.4.0-128.154 in their test environment for a 24
hours stress test and could not reproduce the issue. I changed the tag
to verification done.
** Tags removed: verification-needed-xenial
** Tags added: verifica
Created By: David Coronel (28/05/2018 4:28 PM)
Good day Sam, Jamie,
The kernel 4.4.0-128-generic #154 is now ready for testing by Nvidia:
linux | 4.4.0-128.154 | xenial-proposed | source
linux-image-4.4.0-128-generic | 4.4.0-128.154 | xenial-proposed | amd64, arm64,
armhf, i386, ppc64el, s390x
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 'verifica
** 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/1750038
Title:
user space process hung in 'D' state waiting for disk io
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubu
** Description changed:
+ == SRU Justification ==
+
+ [Impact]
+ Occasionally an application gets stuck in "D" state on NFS reads/sync and
close system calls. All the subsequent operations on the NFS mounts are stuck
and reboot is required to rectify the situation.
+
+ [Fix]
+ Use GPF_NOIO in
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.16 kernel[
