linux-kernel - Re: failure to boot any kernel since 2.6.36rc6-git2.

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] [day] [month] [year] [list]

Message-ID: <AANLkTi=MLowxVT2BoXuA9r8EnYDWPNTYyMP9AhHseznB@mail.gmail.com>
Date:	Tue, 16 Nov 2010 21:52:12 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Len Brown <lenb@...nel.org>
Subject: Re: failure to boot any kernel since 2.6.36rc6-git2.

On Tue, Nov 16, 2010 at 7:27 PM, Dave Jones <davej@...hat.com> wrote:
> Every kernel between 2.6.36-rc6 and 2.6.37rc2 fails to boot on my laptop.
> The -git's that followed -rc6 had a fairly large (considering rc6) acpi merge,
> which I suspected was the cause.

You have marked (for example) commit 77f890223338 as bad, but that's
way before the ACPI merge.

So there's something wrong with your bisect. When you marked c9d66d35
as bad, that is literally _exactly_ v2.6.36-rc6 plus one mfd commit.
So if that kernel doesnt' boot for you, then neither will plain
2.6.36-rc6.

I see a few possibilities:

 - you somehow tested/booted the wrong kernels and thus marked things
"bad" when they weren't.

 - 2.6.36-rc6 doesn't work either, so you started out saying it was
good even though it wasn't really. Everything after it is obviously
also broken, so you'll just end up with everything marked "bad", and
bisection will decide it must be the first commit after 2.6.36-rc6
(since that was marked "good").

 - there's some bug that affects boot of the "next" kernel, and the
kernel you go back to in between has that problem.

 - you switched compiler or other build tool in between things, so
back when you started, 2.6.36-rc6 was good, but then when you compiled
that same kernel with the trivial mfd thing on top, the build tool
change resulted in it no longer working - but not having anything to
do with the actual kernel sources in question.

So double-check that 2.6.36-rc6 kernel.

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