From: Martin Orr <martin@martinorr.name>
To: Andi Kleen <andi@firstfloor.org>
Cc: Stefano Rivoir <s.rivoir@gts.it>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.22 released
Date: Wed, 11 Jul 2007 18:51:14 +0100 [thread overview]
Message-ID: <46951892.20406@martinorr.name> (raw)
In-Reply-To: <p73vecrxf0t.fsf@bingen.suse.de>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
O#n 11/07/07 14:10, Andi Kleen wrote:
> Stefano Rivoir <s.rivoir@gts.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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-07-11 17:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 23:52 Linux 2.6.22 released Linus Torvalds
2007-07-09 0:19 ` Jesper Juhl
2007-07-09 1:08 ` Phil Oester
2007-07-09 6:06 ` Jan De Luyck
2007-07-09 5:00 ` Willy Tarreau
2007-07-09 10:14 ` Alan Cox
2007-07-10 18:41 ` Chuck Ebbert
2007-07-09 10:30 ` Jan Engelhardt
2007-07-09 11:45 ` Jan Engelhardt
2007-07-09 14:25 ` Michal Piotrowski
2007-07-10 7:17 ` Stefano Rivoir
2007-07-10 8:52 ` Andrew Morton
2007-07-10 15:39 ` Linus Torvalds
2007-07-10 15:59 ` Stefan Richter
2007-07-11 6:38 ` Stefano Rivoir
2007-07-11 7:05 ` Linus Torvalds
2007-07-11 10:55 ` Stephen Frost
2007-07-11 14:28 ` Stefano Rivoir
2007-07-11 12:35 ` Martin Orr
2007-07-11 14:27 ` Stefano Rivoir
2007-07-11 13:10 ` Andi Kleen
2007-07-11 17:51 ` Martin Orr [this message]
2007-07-11 18:01 ` Linus Torvalds
2007-07-11 21:00 ` Martin Orr
2007-07-11 21:29 ` Linus Torvalds
2007-07-11 22:16 ` Andi Kleen
2007-07-11 22:33 ` Serge Belyshev
2007-07-11 22:37 ` Linus Torvalds
2007-07-11 22:43 ` Andi Kleen
2007-07-11 23:56 ` Stephen Frost
2007-07-14 15:48 ` Martin Orr
2007-07-11 16:25 ` Theodore Tso
2007-07-10 19:39 ` Valdis.Kletnieks
2007-07-10 22:26 ` Adrian Bunk
2007-07-10 23:12 ` Stefan Richter
2007-07-11 0:00 ` Adrian Bunk
2007-07-11 10:57 ` Stefan Richter
2007-07-11 0:32 ` Valdis.Kletnieks
2007-07-11 0:01 ` david
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46951892.20406@martinorr.name \
--to=martin@martinorr.name \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.rivoir@gts.it \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox