* Peter Zijlstra ([EMAIL PROTECTED]) wrote: > On Mon, 2007-11-05 at 13:44 +0100, Eric Sesterhenn wrote: > > * Peter Zijlstra ([EMAIL PROTECTED]) 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)
hmm did another git bisect, which also gave a bogus commit, made a fresh checkout into an empty dir and the current kernel boots fine, seems like there was something wrong with my local sources. Greetings, Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
