From: Bill Davidsen <davidsen@tmr.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LKML <linux-kernel@vger.kernel.org>, jakub@redhat.com
Subject: Re: Fedora's latest gcc produces unbootable kernels
Date: Sat, 01 Dec 2007 13:37:44 -0500 [thread overview]
Message-ID: <4751A9F8.1090505@tmr.com> (raw)
In-Reply-To: <20071201184752.33536d09@poseidon.drzeus.cx>
Pierre Ossman wrote:
> On Sat, 1 Dec 2007 15:42:23 +0100
> Pierre Ossman <drzeus-list@drzeus.cx> wrote:
>
>> The latest GCC in Fedora rawhide contains some serious bug (or provokes a latent one in the kernel) that makes every kernel built unbootable. It just locks up halfway through the init. Kernels that previously worked fine all now experience the same symptom. Even RH's own kernels exhibit this. The kernel built Nov 24th works, Nov 26th doesn't. gcc was updated 26th, 14 hours earlier.
>>
>
> Digging a bit further, it is indeed the high-res stuff (the first missing message) that hangs. If I hard code the kernel to just be non-high-res capable, it boots, but time keeping is horribly broken.
>
> Anyway, hopefully this means I'll soon have the object file that gets miscompiled. Jakub also pointed me to an older gcc RPM so that I can produce an object file with that as well and see what differs.
>
If you are referring to the "compat" RPMs, be aware that they use the
current headers, which is a good or bad thing depending on what you want
to do. If you want to build old software, you get to keep a down-rev
virtual machine to do it right :-(
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-12-01 18:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 14:42 Fedora's latest gcc produces unbootable kernels Pierre Ossman
2007-12-01 17:47 ` Pierre Ossman
2007-12-01 18:37 ` Bill Davidsen [this message]
2007-12-01 20:11 ` Pierre Ossman
2007-12-01 20:20 ` Pierre Ossman
2007-12-03 8:17 ` Thomas Gleixner
2007-12-03 8:58 ` Jakub Jelinek
2007-12-03 11:34 ` Thomas Gleixner
2007-12-03 11:51 ` Jakub Jelinek
2007-12-03 12:03 ` Thomas Gleixner
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=4751A9F8.1090505@tmr.com \
--to=davidsen@tmr.com \
--cc=drzeus-list@drzeus.cx \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.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