Unfortunately, I can't really reproduce it. Journalctl shows the bug
having occurred twice since the beginnen of March, om kernel 4.10.0.
I'll install the 4.12 kernel and see the coming weeks if it triggers again.
Thanks!
Bas.
On 15-05-17 22:03, Joseph Salisbury wrote:
> Do you have a way to reproduce this bug?
>
> If so, would it be possible for you to test the latest upstream kernel?
> Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
> latest v4.12 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'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => High
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
Unfortunately, I can't really reproduce it. Journalctl shows the bug
having occurred twice since the beginnen of March, om kernel 4.10.0.
I'll install the 4.12 kernel and see the coming weeks if it triggers again.
Thanks!
Bas.
On 15-05-17 22:03, Joseph Salisbury wrote: /wiki.ubuntu. com/KernelMainl ineBuilds . Please test the fixed-upstream' . bug-exists- upstream' . kernel. ubuntu. com/~kernel- ppa/mainline/ v4.12-rc1/
> Do you have a way to reproduce this bug?
>
> If so, would it be possible for you to test the latest upstream kernel?
> Refer to https:/
> latest v4.12 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-
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => High
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>