From: Eric Sesterhenn <snakebyte@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>
Subject: Re: oops in enqueue_entity with 2.6.24-rc1-g54866f03
Date: Mon, 5 Nov 2007 20:15:16 +0100 [thread overview]
Message-ID: <20071105191516.GC20465@alice> (raw)
In-Reply-To: <1194266832.27652.439.camel@twins>
* Peter Zijlstra (peterz@infradead.org) wrote:
> On Mon, 2007-11-05 at 13:44 +0100, Eric Sesterhenn wrote:
> > * 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)
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
prev parent reply other threads:[~2007-11-05 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 12:36 oops in enqueue_entity with 2.6.24-rc1-g54866f03 Eric Sesterhenn
2007-11-02 14:13 ` Rafael J. Wysocki
2007-11-02 15:26 ` Eric Sesterhenn
2007-11-05 12:37 ` Peter Zijlstra
2007-11-05 12:44 ` Eric Sesterhenn
2007-11-05 12:47 ` Peter Zijlstra
2007-11-05 19:15 ` Eric Sesterhenn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071105191516.GC20465@alice \
--to=snakebyte@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.