linux-kernel - Re: Linux 2.6.30.2: does not boot

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: <alpine.LFD.2.01.0907201110390.13838@localhost.localdomain>
Date:	Mon, 20 Jul 2009 11:16:17 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Damien Wyart <damien.wyart@...e.fr>
cc:	Greg KH <gregkh@...e.de>,
	Wolfgang Walter <wolfgang.walter@...m.de>,
	linux-kernel@...r.kernel.org
Subject: Re: Linux 2.6.30.2: does not boot

On Mon, 20 Jul 2009, Damien Wyart wrote:
> 
> I am seeing a similar problem (no hang but an immediate reboot) on the
> same distro. I tried to bisect but got no good kernel in the end.
> 
> To clarify things I recompiled again 2.6.30.1 with the orginial .config
> and it also failed to boot (I was happy to have renamed it so the
> working kernel was still available). I suspected a recent gcc 4.3
> upgrade so downgraded gcc, but no luck, still getting the same problem.
> So for now I am quite stuck, but there is clearly a bad problem
> somewhere...

Hmm. So you _had_ a working self-compiled 2.6.30 kernel at some point?

One thing to look out for is that a compiler upgrade/downgrade will be 
invisible to the kernel build system, so if you downgrade the compiler and 
recompile, you may not actually recompile things at all.

The kernel build system _should_ notice when the build flags change, but 
gcc versions changing under it, not so much. So you might want to do a 
"make clean" to be sure.

And quite frankly, I'm not 100% sure even that will always do it.

Why? Many distro's use ccache, and so you may actually get a cached object 
file from a previous compile (with a previous compiler). Now, ccache is 
pretty good at noticing when things change, and I can well imagine that it 
also checks the compiler version (in addition to checking the hash of the 
preprocessed output and build flags etc), but I haven't double-checked.

So to make doubly sure that you really don't end up using cached object 
files, you might want to run "ccache -C".

			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/