public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Daniel Walker <dwalker@mvista.com>,
	Esben Nielsen <nielsen.esben@googlemail.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: 2.6.19-rc6-rt0, -rt YUM repository
Date: Fri, 17 Nov 2006 20:13:50 +0100	[thread overview]
Message-ID: <20061117191350.GA19101@elte.hu> (raw)
In-Reply-To: <1163789144.6953.57.camel@mindpipe>


* Lee Revell <rlrevell@joe-job.com> wrote:

> On Fri, 2006-11-17 at 17:17 +0100, Ingo Molnar wrote:
> > thanks, please do that. Right now i have no open boot-crash regression 
> > left that i can reproduce.
> 
> Possibly old news, but with 2.6.18-rt7 this user gets an Oops in
> read_hpet() if high res timers are enabled.
> 
> http://ubuntuforums.org/showthread.php?t=292071

hm, that bug could still be around - does the patch below fix it? I've 
uploaded -rt3 and soon there will be -rt3 rpms in the YUM repository 
too.

	Ingo

Index: linux/drivers/char/hpet.c
===================================================================
--- linux.orig/drivers/char/hpet.c
+++ linux/drivers/char/hpet.c
@@ -909,9 +909,7 @@ int hpet_alloc(struct hpet_data *hdp)
 	hpetp->hp_delta = hpet_calibrate(hpetp);
 
 	if (!hpet_clocksource_p) {
-#ifdef CONFIG_IA64
-        	clocksource_hpet.fsys_mmio_ptr = hpet_mc_ptr = &hpetp->hp_hpet->hpet_mc;
-#endif
+        	hpet_mc_ptr = &hpetp->hp_hpet->hpet_mc;
         	clocksource_hpet.mult = clocksource_hz2mult(hpetp->hp_tick_freq,
                                                    clocksource_hpet.shift);
         	clocksource_register(&clocksource_hpet);

  reply	other threads:[~2006-11-17 19:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 15:35 2.6.19-rc6-rt0, -rt YUM repository Ingo Molnar
2006-11-16 16:31 ` Daniel Walker
2006-11-16 20:16   ` Ingo Molnar
2006-11-16 21:12   ` Esben Nielsen
2006-11-16 21:44     ` Daniel Walker
2006-11-16 22:07       ` Ingo Molnar
2006-11-16 22:37         ` Daniel Walker
2006-11-17  5:55           ` Ingo Molnar
2006-11-17  6:50             ` Ingo Molnar
2006-11-17  6:54               ` Ingo Molnar
2006-11-17  6:59                 ` Ingo Molnar
2006-11-17 15:58         ` Lee Revell
2006-11-17 16:17           ` Ingo Molnar
2006-11-17 17:44             ` Daniel Walker
2006-11-21  8:22               ` Ingo Molnar
2006-11-17 18:45             ` Lee Revell
2006-11-17 19:13               ` Ingo Molnar [this message]
2006-11-17  0:06 ` Sergio Monteiro Basto
2006-11-17  9:22   ` Ingo Molnar
2006-11-20  2:09     ` Sergio Monteiro Basto

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=20061117191350.GA19101@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nielsen.esben@googlemail.com \
    --cc=rlrevell@joe-job.com \
    --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