Date: Mon, 5 Nov 2007 13:44:27 +0100
From: Eric Sesterhenn <snakebyte@gmx.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: oops in enqueue_entity with 2.6.24-rc1-g54866f03
Message-ID: <20071105124427.GA8765@alice>
References: <20071102123603.GA4988@alice> <1194266231.27652.437.camel@twins>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <1194266231.27652.437.camel@twins>
User-Agent: Mutt/1.5.16 (2007-06-09)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1048
Lines: 29

* Peter Zijlstra (peterz@infradead.org) wrote:
> On Fri, 2007-11-02 at 13:36 +0100, Eric Sesterhenn wrote:
> > hi,
> > 
> > I get the following crash with 2.6.24-rc1-g54866f03, the last version I
> > tested which booted fine was 2.6.24-rc1-gb1d08ac0
> > 
> 
> How reproducable is this?

happens every boot

> If its very much reproducable, could you git bisect it, as in between
> those commits you tested nothing much has changed, that is, nothing that
> stands out to me.

i did already bisect this but landed at a commit which wasnt the cause
(also failed when i reverted it), I am currently bisecting a second time with
-rc1 as the other starting point, because I am not sure how to make git
give me revision gb1d08ac0 again to test it another time (the binary i
have here boots fine)

Thanks, Eric

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/