Comment 21 for bug 1767180

Bob, the next step is to fully reverse commit bisect from kernel 4.16.6 to 4.17-rc6, in order to identify the earliest good kernel commit, preceded 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 ?

Please note, finding adjacent kernel versions, or providing a commit without testing it and reverting it is not fully reverse commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

It is most helpful that after the fix commit (not kernel version) has been confirmed via testing, you then mark this report Status Confirmed.

Thank you for your help.