I was hoping the fix was already cc'd to stable, but it appears to not have been from your test results.
We could perform a bisect to identify the commit that caused the regression. However, it's probably better to perform a "Reverse" bisect to identify the commit that fixes the bug. We first need to identify the last kernel version with the bug and the first kernel version without the bug. Can you also test the following kernels: 4.0: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/ 4.2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-wily/ 4.4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/ 4.6-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/ You don't have to test every kernel, just up until the first kernel that fixes the bug. We can then narrow it down further. ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Tags added: performing-bisect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568830 Title: make_request bug: can't convert block across chunks or bigger than 512k 2554601336 124 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
