On Tue, 2018-06-26 at 20:40 +0000, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular
> problem?
The problem first appeared after an upgrade of Debian Linux (mixed
"frankendebian" distro). I do not remember the exact versions of the
software.
In Ubuntu 18.04 the problem appeared immediately after installation. I
haven't tested with other versions of 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.18 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 this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
OK, I am going to do this later.
> Once testing of the upstream kernel is complete, please mark this bug
> as
> "Confirmed".
On Tue, 2018-06-26 at 20:40 +0000, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular
> problem?
The problem first appeared after an upgrade of Debian Linux (mixed
"frankendebian" distro). I do not remember the exact versions of the
software.
In Ubuntu 18.04 the problem appeared immediately after installation. I
haven't tested with other versions of Ubuntu.
> /wiki.ubuntu. com/KernelMainl ineBuilds . Please test the fixed-upstream' . bug-exists- upstream' .
> Would it be possible for you to test the latest upstream kernel?
> Refer
> to https:/
> latest
> v4.18 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-
OK, I am going to do this later.
> Once testing of the upstream kernel is complete, please mark this bug
> as
> "Confirmed".