'd like to perform a reverse bisect to figure out which commit upstream fixes this regression. It would be very helpful to know the last kernel that had this issue and the first kernel that did not.
Can you test the following kernels and report back? We are looking for the earliest kernel version that doesn't have this bug: v4.1-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc4-unstable/ v4.1-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc3-unstable/ v4.1-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc2-unstable/ v4.1-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc1-unstable/ You don't have to test every kernel. We are just looking for the last kernel that had the bug and the first kernel that did not. Once we know these two versions, we can bisect between them. ** 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/1439780 Title: [Hyper-V] Fiber Channel critical target error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1439780/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
