[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46951892.20406@martinorr.name>
Date: Wed, 11 Jul 2007 18:51:14 +0100
From: Martin Orr <martin@...tinorr.name>
To: Andi Kleen <andi@...stfloor.org>
CC: Stefano Rivoir <s.rivoir@....it>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.22 released
O#n 11/07/07 14:10, Andi Kleen wrote:
> Stefano Rivoir <s.rivoir@....it> writes:
>> Linus Torvalds wrote:
>>> On Tue, 10 Jul 2007, Stefano Rivoir wrote:
>> Ok, the guilty bit is gcc: in my box, compiling kernel with gcc 4.2.x
>> (which is installed on my debian/sid) turns into a hang (in init,
>> seemingly, maybe not even in kernel itself), while gcc-4.1 is allright.
>
> The standard way to track this down is to compile different directories
> of the kernel with different gcc versions. Then when you find the directory
> go down to files. Then you could eventually go down to functions, although
> that tends to involve quite some editing work. But already knowing
> the file would be useful.
I have done this. The file is arch/x86_64/kernel/signal.c: if I compile
this with gcc 20070627 then everything works, if I compile it with gcc
20070707 then udevsettle hangs. This is independent of the gcc version used
to compile the rest of the kernel. (The dates refer to versions of the
Debian gcc-4.2 package and its dependencies.)
--
Martin Orr
Download attachment "signature.asc" of type "application/pgp-signature" (253 bytes)
Powered by blists - more mailing lists