linux-kernel - Re: oops in enqueue_entity with 2.6.24-rc1-g54866f03

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1194266832.27652.439.camel@twins>
Date:	Mon, 05 Nov 2007 13:47:12 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Eric Sesterhenn <snakebyte@....de>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>
Subject: Re: oops in enqueue_entity with 2.6.24-rc1-g54866f03

On Mon, 2007-11-05 at 13:44 +0100, Eric Sesterhenn wrote:
> * Peter Zijlstra (peterz@...radead.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)

git checkout b1d08ac0

should do I guess.

-
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/