[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080304124241.GD29777@elte.hu>
Date: Tue, 4 Mar 2008 13:42:41 +0100
From: Ingo Molnar <mingo@...e.hu>
To: "Klaus S. Madsen" <ksm@...rnemadsen.org>
Cc: Pavel Machek <pavel@....cz>,
Suspend-devel list <suspend-devel@...ts.sourceforge.net>,
"H. Peter Anvin" <hpa@...or.com>,
LKML <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Thomas Gleixner <tglx@...utronix.de>,
Matthew Garrett <mjg59@...f.ucam.org>
Subject: Re: Regression in 2.6.25-rc3: s2ram segfaults before suspending
* Klaus S. Madsen <ksm@...rnemadsen.org> wrote:
> > are you sure you ID-ed the right commit that broke things?
>
> I can't be sure. It was my third attempt, and there seems to be some
> sort of Makefile trouble in that area, which causes the problem to
> appear and disappear at random, unless I do a make clean && make. But
> the triggering commit was found with make clean && make, and I made
> sure that reverting the resulting commit did actually solve the
> problem...
btw., even if it turns out to be the wrong commit, you sure poked in the
right general area. This is one of the reoccuring problems with git
bisection: a small mistake near the end of a long bisection session can
point to the wrong commit. Especially with more sporadic failure modes
it can be quite a challenge.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists