From: Damien Wyart <damien.wyart@free.fr>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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 22:31:03 +0200 [thread overview]
Message-ID: <20090720203103.GA3022@brouette> (raw)
In-Reply-To: <alpine.LFD.2.01.0907201110390.13838@localhost.localdomain>
> > 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...
* Linus Torvalds <torvalds@linux-foundation.org> [2009-07-20 11:16]:
> Hmm. So you _had_ a working self-compiled 2.6.30 kernel at some point?
Yes, my case is very similar to the one described by Kiko Piris, and
I also think this is getting off topic.
> One thing to look out for is that a compiler upgrade/downgrade will be
> invisible to the kernel build system, so if you downgrade the compiler
> and recompile, you may not actually recompile things at all.
I tried the bisect with the same compiler and then for other tests
I recompiled from scratch each time on a tmpfs to make sure I was not
messing things up. On this machine, ccache is not used.
So I am suspecting a recent glibc or binutils upgrade (gcc downgrade did
not solve the problem) and even if some people noticed problems with
2.6.30.2, my issue seems different and only distro-related.
--
Damien Wyart
next prev parent reply other threads:[~2009-07-20 20:31 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 [this message]
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
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=20090720203103.GA3022@brouette \
--to=damien.wyart@free.fr \
--cc=gregkh@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox