linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LKML <linux-kernel@vger.kernel.org>,
	jakub@redhat.com, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Fedora's latest gcc produces unbootable kernels
Date: Sat, 1 Dec 2007 21:20:54 +0100	[thread overview]
Message-ID: <20071201212054.2377c8be@poseidon.drzeus.cx> (raw)
In-Reply-To: <20071201184752.33536d09@poseidon.drzeus.cx>

[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]

On Sat, 1 Dec 2007 18:47:52 +0100
Pierre Ossman <drzeus-list@drzeus.cx> 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.
> 

I've now pinpointed where it hangs. And it doesn't hang in fact. It gets stuck in an infinite loop in tick_setup_sched_timer():

	for (;;) {
		hrtimer_forward(&ts->sched_timer, now, tick_period);
		hrtimer_start(&ts->sched_timer, ts->sched_timer.expires,
			      HRTIMER_MODE_ABS);
		/* Check, if the timer was already in the past */
		if (hrtimer_active(&ts->sched_timer))
			break;
		now = ktime_get();
	}

I've added Thomas as cc as this is his domain, so perhaps he has some idea what the compiler does wrong here. I've also included the two object files (one good, one bad). HEAD is v2.6.24-rc3.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

[-- Attachment #2: tick-sched.bad --]
[-- Type: application/octet-stream, Size: 64104 bytes --]

[-- Attachment #3: tick-sched.good --]
[-- Type: application/octet-stream, Size: 64116 bytes --]

  parent reply	other threads:[~2007-12-01 20:21 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
2007-12-01 20:11     ` Pierre Ossman
2007-12-01 20:20   ` Pierre Ossman [this message]
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=20071201212054.2377c8be@poseidon.drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=jakub@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).