DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer
         :mime-version:content-type:content-transfer-encoding;
        b=LeBPCxS3697w51HivfG1IJSiKfGRN63vgo9z/w8JE6fAYYapE80JAJSFR0lU0iPJRk
         L5hD5f5gGahWFRFVp8iR8cHUQj0v47p0Erbi+dWwShji2CKwEEh40z+NKsiYqey8ZCJ6
         1EbL47T0iaWRaAUutoSUpQtpK/R9cxnU6+Li8=
Date: Mon, 20 Jul 2009 21:23:18 +0200
From: Alejandro Riveira =?UTF-8?B?RmVybsOhbmRleg==?= 
	<ariveira@gmail.com>
To: Damien Wyart <damien.wyart@free.fr>
Cc: Greg KH <gregkh@suse.de>, Wolfgang Walter <wolfgang.walter@stwm.de>,
       linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: Linux 2.6.30.2: does not boot
Message-ID: <20090720212318.2aa5be21@varda>
In-Reply-To: <20090720180333.GA2905@brouette>
References: <20090720040813.GC11940@kroah.com>
	<200907201613.22483.wolfgang.walter@stwm.de>
	<20090720150916.GB10015@suse.de>
	<20090720180333.GA2905@brouette>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1613
Lines: 37

El Mon, 20 Jul 2009 20:03:33 +0200
Damien Wyart <damien.wyart@free.fr> escribió:

> > > Built 2.6.30.2 but it hangs when booting immediately after the message:
> 
> > > Booting the kernel.
> 
> > > I built it with gcc version 4.3.3 on debian/sid and used exactly the
> > > same .config as I used with 2.6.32.1 (ok, + "DEFAULT_MMAP_MIN_ADDR
> > > 4096" which didn't exist before).
> 
> * Greg KH <gregkh@suse.de> [2009-07-20 08:09]:
> > Can you do 'git bisect' to see which patch caused the problem? It
> > might be the one, "Don't use '-fwrapv' compiler option: it's buggy in
> > gcc-4.1.x", but it would be good to figure it out for sure.
> 
> 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...
> 
I did not have any probelm with the gcc shipped in ubuntu gcc (Ubuntu
4.3.3-5ubuntu4) 4.3.3 (64 bit jaunty 9.04)

All three 2.6.30 2.6.30.1 and .2 boot just fine (i carry a revert but i
doubt it changes things)

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