From: Ingo Molnar <mingo@elte.hu>
To: Roland Dreier <rdreier@cisco.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Early hang with 2.6.21-rc4-rt1
Date: Sun, 25 Mar 2007 10:06:26 +0200 [thread overview]
Message-ID: <20070325080626.GA22223@elte.hu> (raw)
In-Reply-To: <20070325073424.GA14242@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> hm - on 32-bit, CRITICAL_IRQSOFF_TIMING+FUNCTION_TRACING works fine
> for me. I'll try the 64-bit kernel too.
the 64-bit kernel indeed hangs. Does the patch below fix it for you?
Ingo
Index: linux/kernel/timer.c
===================================================================
--- linux.orig/kernel/timer.c
+++ linux/kernel/timer.c
@@ -822,8 +822,23 @@ EXPORT_SYMBOL(xtime);
/* XXX - all of this timekeeping code should be later moved to time.c */
#include <linux/clocksource.h>
+/*
+ * Dummy clocksource just in case someone tries to use the
+ * clocksource infrastructure before timekeeping_init() is
+ * called:
+ */
+static notrace cycle_t read_boot(void)
+{
+ return 0;
+}
+
+static __initdata struct clocksource clocksource_boot = {
+ .name = "boot",
+ .read = read_boot,
+};
+
/* pointer to current clocksource: */
-static __read_mostly struct clocksource *clock;
+static __read_mostly struct clocksource *clock = &clocksource_boot;
#ifdef CONFIG_GENERIC_TIME
/**
next prev parent reply other threads:[~2007-03-25 8:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 5:03 Early hang with 2.6.21-rc4-rt1 Roland Dreier
2007-03-25 5:29 ` Roland Dreier
2007-03-25 7:29 ` Ingo Molnar
2007-03-25 7:34 ` Ingo Molnar
2007-03-25 8:06 ` Ingo Molnar [this message]
2007-03-25 16:27 ` Roland Dreier
2007-03-25 7:31 ` Ingo Molnar
2007-03-25 14:35 ` Roland Dreier
2007-03-25 17:01 ` Roland Dreier
2007-03-27 19:22 ` Ingo Molnar
2007-03-27 19:24 ` Ingo Molnar
2007-03-27 19:42 ` Roland Dreier
2007-03-30 9:02 ` Ingo Molnar
2007-03-30 9:24 ` Ingo Molnar
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=20070325080626.GA22223@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
/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