I'd like to perform a kernel bisect to figure out which commit caused this regression. We need to identify the earliest kernel that did not exhibit the bug and the first kernel that did exhibit the bug.
Can you test the following kernels and post back? 4.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/ 4.9-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc1/ 4.9 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/ 4.10-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/ 4.10-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc4/ You don't have to test every kernel, just up until the kernel that first has this bug. Based on your test results, we can figure out which kernel to test next. Thanks in advance! ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Zesty) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Zesty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678585 Title: [Zesty] TSO doesn't work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
