Michiel Janssens: >"Should I file this in a new bug report?" Not at this point.
>"Think I will report these results in the upstream bug report too." It's best not to mix and match multiple, even seemingly highly related issues into one report. What would be best, is this issue is settled first, and then any others may be dealt with separately. With this in mind, the next step is to fully reverse commit bisect from kernel 3.13 to 4.1 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? Please note, finding adjacent kernel versions is not fully commit bisecting. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Tags removed: kernel-fixed-upstream-4.1.0-040100 ** Tags added: kernel-fixed-upstream-4.1 needs-reverse-bisect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412730 Title: DELL U2415 monitor detection issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412730/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
