Date: Mon, 20 Jul 2009 15:02:36 -0700 (PDT)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kiko Piris <kernel@pirispons.net>
cc: Damien Wyart <damien.wyart@free.fr>, Greg KH <gregkh@suse.de>,
       Wolfgang Walter <wolfgang.walter@stwm.de>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.30.2: does not boot
In-Reply-To: <20090720211908.GA31814@superlopez.pirispons.net>
Message-ID: <alpine.LFD.2.01.0907201458000.19335@localhost.localdomain>
References: <20090720040813.GC11940@kroah.com> <200907201613.22483.wolfgang.walter@stwm.de> <20090720150916.GB10015@suse.de> <20090720180333.GA2905@brouette> <20090720192933.GA22641@superlopez.pirispons.net> <alpine.LFD.2.01.0907201241490.19335@localhost.localdomain>
 <20090720211908.GA31814@superlopez.pirispons.net>
User-Agent: Alpine 2.01 (LFD 1184 2008-12-16)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-7
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1659
Lines: 47


On Mon, 20 Jul 2009, Kiko Piris wrote:
> > Just to clarify:
> > 
> >  - you literally have a _working_ 2.6.30.1 that you compiled yourself a 
> >    few days ago.
> 
> That?s correct.
> 
> >  - But when you try to compile that same kernel _now_, it fails with an 
> >    immediate reboot? And not just 2.6.30.2, but 2.6.30.1 does that too?
> 
> Also correct.
> 
> > That certainly implies something else than just the -fwrapv vs 
> > -fno-strict-overflow thing.
> 
> Yes, as Marcel Beister pointed, it resulted some binutils bug.
> Downgrading the package produced a perfectly bootable 2.6.30.2.

Ok, so it's been narrowed down to binutils. Good.

> > But we may be looking at two different issues, so maybe your "unable to 
> > compile a working kernel" issue is different from the other reports.
> 
> Totally unrelated to other reports, and not a kernel bug, in fact.

Well, it's still not entirely clear that it's unrelated.

It seems that all the people involved are running Debian/sid, and I don't 
think we have any firm confirmation yet that it's the compiler flag for 
anybody. It was certainly the primary suspect, but maybe that was always 
just a red herring guess.

Wolfgang hasn't actually tried to compile without the -fno-strict-overflow 
flag yet, and maybe his hang is the same binutils bug.

Of course, maybe I missed some gcc flag confirmation that wasn't cc'd to 
me. So who knows..

		Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/