From: Pierre Ossman <drzeus-list@drzeus.cx>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Fedora's latest gcc produces unbootable kernels
Date: Sat, 1 Dec 2007 15:42:23 +0100 [thread overview]
Message-ID: <20071201154223.1b052d39@poseidon.drzeus.cx> (raw)
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.
The last message printed is:
isapnp: Scanning for PnP cards...
Comparing with the working kernel, the next steps are:
isapnp: Scanning for PnP cards...
Switched to high resolution mode on CPU 0
isapnp: No Plug & Play device found
Any ideas on how I can work around this? I'm rather unproductive when I can't build working kernels.. :/
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next reply other threads:[~2007-12-01 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 14:42 Pierre Ossman [this message]
2007-12-01 17:47 ` Fedora's latest gcc produces unbootable kernels Pierre Ossman
2007-12-01 18:37 ` Bill Davidsen
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=20071201154223.1b052d39@poseidon.drzeus.cx \
--to=drzeus-list@drzeus.cx \
--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