Hi,
We think we are affected by the same bug.
We were on version 4.15.0-139 and upgraded to 144 before finding this post.
Is there any confirmation that this issue also occurs in 4.15.0-144?
I have have installed version 4.15.0-136 in the meantime to allow us to reboot and select that kernel, incase the issue is present.
Hi,
We think we are affected by the same bug.
We were on version 4.15.0-139 and upgraded to 144 before finding this post.
Is there any confirmation that this issue also occurs in 4.15.0-144?
I have have installed version 4.15.0-136 in the meantime to allow us to reboot and select that kernel, incase the issue is present.
Hope to see a fix for this issue soon.