We can perform a "Reverse" bisect to identify the commit that fixes this bug in v4.19. We first need to identify the last bad kernel version and the first good kernel version.
Can you test the following kernels: v4.16 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/ v4.17 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17/ v4.18 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18/ v4.19-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc1/
You don't have to test every kernel, just up until the first kernel that does not have the bug.
Thanks in advance!
We can perform a "Reverse" bisect to identify the commit that fixes this bug in v4.19. We first need to identify the last bad kernel version and the first good kernel version.
Can you test the following kernels: kernel. ubuntu. com/~kernel- ppa/mainline/ v4.16/ kernel. ubuntu. com/~kernel- ppa/mainline/ v4.17/ kernel. ubuntu. com/~kernel- ppa/mainline/ v4.18/ kernel. ubuntu. com/~kernel- ppa/mainline/ v4.19-rc1/
v4.16 Final: http://
v4.17 Final: http://
v4.18 Final: http://
v4.19-rc1: http://
You don't have to test every kernel, just up until the first kernel that does not have the bug.
Thanks in advance!