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: <20090720182139.GA6784@merkur.ravnborg.org>
Date:	Mon, 20 Jul 2009 20:21:39 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Damien Wyart <damien.wyart@...e.fr>, 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, Jul 20, 2009 at 11:16:17AM -0700, Linus Torvalds wrote:
> 
> 
> 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.

The build system does notice if the build flag changes - with the
excemption that it does not care about the ordering of the build flags.

gcc version changes are not detected as long as the name of gcc stays
the same - which it does in all normal cases.

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