From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 29738] SIGBUS after upgrade to 2.6.36-rc1-git4 [full stacktrace]
Date: Wed, 25 Aug 2010 15:36:08 -0700 (PDT)
Message-ID: <20100825223608.36ACE130090@annarchy.freedesktop.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id 5772D9E756
for ;
Wed, 25 Aug 2010 15:36:08 -0700 (PDT)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=29738
--- Comment #7 from Nick Bowler 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.