Jason C. McDonald, the next step is to fully commit bisect from kernel 4.4.0.53 to 4.4.0-57 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 ?
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.
Jason C. McDonald, the next step is to fully commit bisect from kernel 4.4.0.53 to 4.4.0-57 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 ?
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.