linux-kernel - Re: 2.6.29 on MacBook 2,1 fails to reboot

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: <200903301944.30030.alistair@devzero.co.uk>
Date:	Mon, 30 Mar 2009 19:44:29 +0100
From:	Alistair John Strachan <alistair@...zero.co.uk>
To:	"Trenton D. Adams" <trenton.d.adams@...il.com>
Cc:	"Morten P.D. Stevens" <mstevens@...-professional.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.29 on MacBook 2,1 fails to reboot

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@...zero.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.
--
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/