[Bug 29738] SIGBUS after upgrade to 2.6.36-rc1-git4 [full stacktrace]

[bugzilla-daemon@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=29738

--- Comment #7 from Nick Bowler <nbowler@draconx.ca> 2010-08-25 15:36:08 PDT ---
(In reply to comment #6)
> Bisection pointed me to the merged drm-core-next branch which does not really
> came unexpected.
[...]
> Can you tell me how I bisect such a branch?

If the bisection pinpoints a merge, it _usually_ means that you mis-labeled an
earlier commit (although it is possible that the merge itself is actually the
culprit).  Unless you made a typo, all your 'bad' labels are likely correct.

So look at the output of 'git bisect log', and make a guess at which 'good'
commit might be mis-labeled (choose an older commit over a newer one if you're
unsure which to try first).  Check out that commit, and try again.  If it turns
out to be bad, you'll need to issue a 'git bisect bad' and then remove one or
more 'good' labels, see the git-bisect man page for details.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.