Re: 2.6.29 on MacBook 2,1 fails to reboot

Alistair John Strachan
2009-03-30T18:44:48Z

On Monday 30 March 2009 16:26:13 Trenton D. Adams wrote:
> On Mon, Mar 30, 2009 at 6:57 AM, Alistair John Strachan
>
> <alistair@devzero.co.uk> wrote:
> > On Monday 30 March 2009 08:33:06 Trenton D. Adams wrote:
> >> And, if I mark the 2.6.27 one as bad, it just remains on 2.6.27.
> >
> > Don't worry about the kernel version it generates. Git bisections
> > traverse merged branches, including those that weren't rebased before
> > being merged (in fact the preferred work flow). I usually add "-bisect"
> > to CONFIG_LOCALVERSION so I can isolate my work in progress bisection
> > from system kernels.
> >
> > You can trust git to involve only relevant commits between your initial
> > "good" and "bad" markers; don't add more unless you have to. Sometimes
> > you may need to "shift" the bisection midpoint if you encounter build
> > breakage. You should be able to find comments Linus made on the subject
> > by searching the LKML archive for "git bisect visualize".
> >
> > --
> > Cheers,
> > Alistair.
>
> Okay, so are you saying that switching back to 2.6.27 is okay, because
> the patch that caused this problem may have been created in 2.6.27 (as
> a patch to the released version perhaps), not applied to 2.6.28, and
> then applied to 2.6.29?

Yes. Give "gitk" a shot with your revision ID, it should be quite
illuminating.

--
Cheers,
Alistair.