Rod B., the next step is to fully reverse commit bisect from kernel 4.4 to 4.16 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?
Please note, finding adjacent kernel versions, or providing a commit from a kernel version bisect is not fully 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 identified, you then mark this report Status Confirmed.
Rod B., the next step is to fully reverse commit bisect from kernel 4.4 to 4.16 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https:/ /wiki.ubuntu. com/Kernel/ KernelBisection ?
Please note, finding adjacent kernel versions, or providing a commit from a kernel version bisect is not fully 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 identified, you then mark this report Status Confirmed.
Thank you for your help.