Thanks for the update. We can perform a "Reverse" bisect to identify the commit that fixes the bug in v4.10-rc4. We first need to identify the last bad kernel and first good one.
Can you test the following kernels:
4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ 4.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/ 4.10-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/
You don't have to test every kernel, just up until the kernel that first kernel that does not have this bug.
We can SRU the commit to all releases this bug affects once we identify it.
Thanks for the update. We can perform a "Reverse" bisect to identify the commit that fixes the bug in v4.10-rc4. We first need to identify the last bad kernel and first good one.
Can you test the following kernels:
4.5 final: http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v4.5-wily/ kernel. ubuntu. com/~kernel- ppa/mainline/ v4.8-rc1/ kernel. ubuntu. com/~kernel- ppa/mainline/ v4.10-rc1/
4.8-rc1: http://
4.10-rc1: http://
You don't have to test every kernel, just up until the kernel that first kernel that does not have this bug.
We can SRU the commit to all releases this bug affects once we identify it.