All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Greg Lee" <glee@casabyte.com>
To: <git@vger.kernel.org>
Cc: "'sean'" <seanlkml@sympatico.ca>, "'Tony Luck'" <tony.luck@intel.com>
Subject: RE: Problem with git bisect between 2.6.15 and 2.6.16
Date: Wed, 29 Mar 2006 14:28:07 -0500	[thread overview]
Message-ID: <117a01c65366$e952dfd0$a100a8c0@casabyte.com> (raw)
In-Reply-To: <12c511ca0603271622n6e4614b2s6f936469863efd9d@mail.gmail.com>

> You'll need to invert "good" and bad" for this.  I.e. mark 2.6.15 as good, 2.6.16 as
bad, and
> then as you test mark kernels with the bug as good, and ones without as bad.  Try not to
go
> insane while working in this inverted parallel universe :-)
> 
> -Tony

This was progressing fine until I ran into an issue that makes the kernel unstable causing
it to crash at semi-random times.  I'm down to about 350 commits left in the bisect.  I've
tried:

git reset --hard HEAD~3

no luck, same problem, unstable

then I tried --hard HEAD~50

no luck, same problem, unstable

I'm concerned about moving too much further in the "~" direction, will this cause me other
problems?

Greg

  reply	other threads:[~2006-03-29 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28  0:00 Problem with git bisect between 2.6.15 and 2.6.16 Greg Lee
2006-03-28  0:06 ` sean
2006-03-28  0:06   ` sean
2006-03-28  0:16     ` Greg Lee
2006-03-28  0:22       ` Tony Luck
2006-03-29 19:28         ` Greg Lee [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-29 19:43 Luck, Tony

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='117a01c65366$e952dfd0$a100a8c0@casabyte.com' \
    --to=glee@casabyte.com \
    --cc=git@vger.kernel.org \
    --cc=seanlkml@sympatico.ca \
    --cc=tony.luck@intel.com \
    /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.