From: Greg KH <gregkh@suse.de>
To: "Alejandro Riveira Fernández" <ariveira@gmail.com>
Cc: Damien Wyart <damien.wyart@free.fr>,
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
Date: Mon, 20 Jul 2009 12:42:29 -0700 [thread overview]
Message-ID: <20090720194229.GB29819@suse.de> (raw)
In-Reply-To: <20090720212318.2aa5be21@varda>
On Mon, Jul 20, 2009 at 09:23:18PM +0200, Alejandro Riveira Fernández wrote:
> 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)
What revert do you find needed?
thanks,
greg k-h
next prev parent reply other threads:[~2009-07-20 19:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 4:08 Linux 2.6.30.2 Greg KH
2009-07-20 4:08 ` Greg KH
2009-07-20 14:13 ` Linux 2.6.30.2: does not boot Wolfgang Walter
2009-07-20 14:38 ` Kiko Piris
2009-07-20 15:09 ` Greg KH
2009-07-20 18:03 ` Damien Wyart
2009-07-20 18:16 ` Linus Torvalds
2009-07-20 18:21 ` Sam Ravnborg
2009-07-20 20:31 ` Damien Wyart
2009-07-21 0:13 ` Stephen Rothwell
2009-07-21 0:28 ` Linus Torvalds
2009-07-21 4:09 ` Stephen Rothwell
2009-07-20 19:23 ` Alejandro Riveira Fernández
2009-07-20 19:42 ` Greg KH [this message]
2009-07-20 19:50 ` Alejandro Riveira Fernández
2009-07-20 21:34 ` Greg KH
2009-07-20 19:29 ` Kiko Piris
2009-07-20 19:50 ` Linus Torvalds
2009-07-20 21:19 ` Kiko Piris
2009-07-20 22:02 ` Linus Torvalds
2009-07-20 22:04 ` Linus Torvalds
2009-07-20 22:14 ` Kiko Piris
2009-07-21 0:42 ` Wolfgang Walter
2009-07-21 20:42 ` Bastian Blank
[not found] ` <4A6746B9.9010603@ubuntu.com>
2009-07-23 0:49 ` current binutils trunk fails to build bootable kernel image for some configurations Alan Modra
2009-07-23 5:05 ` Sam Ravnborg
2009-07-23 6:01 ` Alan Modra
2009-07-20 20:29 ` Linux 2.6.30.2: does not boot Marcel Beister
-- strict thread matches above, loose matches on Subject: below --
2009-07-20 15:21 Mario Vanoni
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=20090720194229.GB29819@suse.de \
--to=gregkh@suse.de \
--cc=ariveira@gmail.com \
--cc=damien.wyart@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wolfgang.walter@stwm.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.