mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wolfgang Walter <wolfgang.walter@stwm.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kiko Piris <kernel@pirispons.net>,
	Damien Wyart <damien.wyart@free.fr>, Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.30.2: does not boot
Date: Tue, 21 Jul 2009 02:42:33 +0200	[thread overview]
Message-ID: <200907210242.33602.wolfgang.walter@stwm.de> (raw)
In-Reply-To: <alpine.LFD.2.01.0907201458000.19335@localhost.localdomain>

On Tuesday 21 July 2009, Linus Torvalds wrote:
> 
> 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.

Yes, it is.

I built with -fwrapv instead of  -fno-strict-overflow and without either, both 
fail to boot.

Downgrading binutils to those of debian/testing and the unmodified 2.6.30.2 
works.

So this seems to be indeed a problem with binutils in debian/sids.

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts
Leiter EDV
Leopoldstraße 15
80802 München
Tel: +49 89 38196-276
Fax: +49 89 38196-144
wolfgang.walter@stwm.de
http://www.studentenwerk-muenchen.de/

  parent reply	other threads:[~2009-07-21  0:42 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
2009-07-20 22:04               ` Linus Torvalds
2009-07-20 22:14               ` Kiko Piris
2009-07-21  0:42               ` Wolfgang Walter [this message]
2009-07-21 20:42               ` Bastian Blank
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
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=200907210242.33602.wolfgang.walter@stwm.de \
    --to=wolfgang.walter@stwm.de \
    --cc=damien.wyart@free.fr \
    --cc=gregkh@suse.de \
    --cc=kernel@pirispons.net \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®