Dmitry Malykhanov, the next step is to fully commit bisect from Ubuntu kernel 4.15.0-10.11 to Ubuntu kernel 4.15.0-12.13, in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was written for folks who don't know anything about linux, so it's easy to follow.
Please note, finding adjacent kernel versions, or providing a commit without testing it and reverting it is not fully commit bisecting.
Also, the kernel release names are irrelevant for the purposes of bisecting.
It is most helpful that after the bad commit (not kernel version) has been confirmed via testing, you then mark this report Status Confirmed.
Dmitry Malykhanov, the next step is to fully commit bisect from Ubuntu kernel 4.15.0-10.11 to Ubuntu kernel 4.15.0-12.13, in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https:/ /wiki.ubuntu. com/Kernel/ KernelBisection ? This article was written for folks who don't know anything about linux, so it's easy to follow.
Please note, finding adjacent kernel versions, or providing a commit without testing it and reverting it is not fully commit bisecting.
Also, the kernel release names are irrelevant for the purposes of bisecting.
It is most helpful that after the bad commit (not kernel version) has been confirmed via testing, you then mark this report Status Confirmed.
Thank you for your help.