https://bugzilla.kernel.org/show_bug.cgi?id=85491 --- Comment #16 from Michel Dänzer <michel@xxxxxxxxxxx> --- (In reply to Marek from comment #15) > The result of bisection is that the first bad commit is: > > e5558d1a516fa6924fa8d53152b665d4c26f142e Merge branches 'dma-api', > 'pci/virtualization', 'pci/msi', 'pci/misc' and 'pci/resource' into next In general, if the result of a bisection is a merge commit, it indicates something might have gone wrong during the bisection. In this case, I suspect the problem might not happen every time even with affected kernels, so you need to test several times before declaring a commit good. You can double-check this by testing commit e5558d1a516fa6924fa8d53152b665d4c26f142e again several times. Does it happen every time? If yes, test its parent commit(s) again several times. Does it never happen? If the answer to either question is no, I'm afraid you need to start the bisection again. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
