Comment # 14
on bug 92858
from Michel Dänzer
(In reply to Darren D. from comment #13) > Another update: I think I'm either finished or close to finished--shouldn't > bisect say which of the revisions is bad once i get down to 0, though? > > Bisecting: 0 revisions left to test after this (roughly 0 steps) > [bdcddf95e82b1c4e370fc1196b1f4f50f775dab4] Backmerge v4.1-rc4 into into > drm-next That refers to the number of commits that need to be tested after the current one (bdcddf95). You'd still need to mark the current commit as good or bad to get the result. However... > Any bisects that say bad after 81663016dbfd53e29d1b5c5ddbc9b12ae1d66474 are > marked bad not because of lack of accel, but because they didn't boot up. I > was able to locate, however, the next bootable kernel after the 'initial > ramdisk" boot failures started. Commit ID > 744b058827b3db9a4f6027522dd9c73a208c2d31, and it both booted and had > functional accelerated OpenGL on the videocard. ... I think you'll need to restart the bisection process with 744b058827b3db9a4f6027522dd9c73a208c2d31 as the initial good commit and the nearest bad one you've found so far. Otherwise the result will likely be inconsistent, because you marked different commits bad according to different criteria.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
