https://bugzilla.kernel.org/show_bug.cgi?id=202511 --- Comment #5 from Bjorn Helgaas (bhelgaas@xxxxxxxxxx) --- The bisect log in comment #3 shows 3a3869f1c443 ("Merge tag 'pci-v4.18-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci") as the first bad commit. That's a large merge commit so I can't pick out anything useful. The previous good commit was 3036bc45364f ("Merge tag 'media/v4.18-2' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media"). I'm not a bisect expert, but there must be a way to bisect between those two commits to zero in on something specific. Is this any help? 05:49:21 ~/linux (junk)$ git bisect start 05:49:47 ~/linux (junk|BISECTING)$ git bisect good 3036bc45364f98515a2c446d7fac2c34dcfbeff4 05:50:01 ~/linux (junk|BISECTING)$ git bisect bad 3a3869f1c443383ef8354ffa0e5fb8df65d8b549 Bisecting: 88 revisions left to test after this (roughly 6 steps) [13fbadcd512c225c907d6e8147fb48a88114bf03] Merge branch 'pci/sparc' -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
