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
Date: Mon, 20 Jul 2009 15:02:36 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0907201458000.19335@localhost.localdomain> (raw)
In-Reply-To: <20090720211908.GA31814@superlopez.pirispons.net>
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
next prev parent reply other threads:[~2009-07-20 22:02 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
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 [this message]
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=alpine.LFD.2.01.0907201458000.19335@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=damien.wyart@free.fr \
--cc=gregkh@suse.de \
--cc=kernel@pirispons.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox