Given the new kernel, this bug should remain open as long as the 4.4.0-66 is available for installation as it appears to be directly relevant to upgrading to this kernel.
The severity of the bug may be mitigated by the new upstream kernel, but I think it's fairly severe currently given it has been the primary kernel of an LTS release for some time.
Given the new kernel, this bug should remain open as long as the 4.4.0-66 is available for installation as it appears to be directly relevant to upgrading to this kernel.
The severity of the bug may be mitigated by the new upstream kernel, but I think it's fairly severe currently given it has been the primary kernel of an LTS release for some time.