Bug persists after upgrade to 4.10.0-30.
It continues to be necessary to boot a 4.8 kernel to avoid catastrophic
work loss.
Surely this regression merits higher priority attention.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected xenial
** Description changed:
- Immediately after upgrading to 4.10.0-27, system unresponsive after
- suspend. This did not occur previously with 4.8.0-56. HP Z820, XEON
- ES-2669, Nvidia Quadro K2000.
+ Immediately after upgrading to
We are not able to test the upstream kernel at this time. The consensus
is that the risk, however unlikely, of extended downtime is too great at
this point in our development cycle. It must wait for a break in the
action, my apologies.
--
You received this bug notification because you are a
> Does this issue go away if you boot back into the prior kernel?
Yes
> Would it be possible for you to test the latest upstream kernel?
I'll have a go at it. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Does this issue go away if you boot back into the prior kernel?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705859
Title:
ubuntu
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.13 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
