public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Frank Sorenson <frank@tuxrocks.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Darren Hart <dvhltc@us.ibm.com>,
	Nishanth Aravamudan <nacc@us.ibm.com>,
	George Anzinger <george@mvista.com>,
	Roman Zippel <zippel@linux-m68k.org>,
	Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/13] Time: Generic Timeofday Subsystem (v B10)
Date: Mon, 14 Nov 2005 14:02:15 -0800	[thread overview]
Message-ID: <1132005736.4668.34.camel@leatherman> (raw)
In-Reply-To: <4379074D.5060308@tuxrocks.com>

On Mon, 2005-11-14 at 14:53 -0700, Frank Sorenson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> john stultz wrote:
> > Hmm... Not sure if this is mis-calibration or just bad-interaction w/
> > kthrt. Mind sending a dmesg to me?
> 
> dmesg attached

Thanks, I'll start looking into it.

> >>and 'pit' seems to produce errors (system will not switch from pit to
> >>another clocksource anymore):
> 
> Odd.  This time, I got the errors when I switched from acpi_pm (which it
> had defaulted to at bootup) to jiffies.  System has not locked at one
> clocksource yet, though.

Yea, jiffies and pit are similarly non-continuous clocksources.

> > Do the TOD patches have this issue by themselves, or is this only with
> > kthrt? I know I had some issues with non-continuous clocksources (pit,
> > jiffies) with the kthrt patch, where it wouldn't fall back to
> > non-high-res when the clocksource stopped supporting it.
> 
> I only tried with kthrt because I ran into lots of conflicts when
> applying the patches to more recent kernels otherwise.  I can try again
> with 2.6.14-mm2 in order to test it out.

You can alternatively drop the patches in the kthrt set that are after
the timeofday patches in Thomas' series file. Or even just disable the
high-res config option and see if that changes anything.

thanks
-john



  reply	other threads:[~2005-11-14 22:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12  4:48 [PATCH 0/13] Time: Generic Timeofday Subsystem (v B10) john stultz
2005-11-12  4:48 ` [PATCH 1/13] Time: Reduced NTP rework (part 1) john stultz
2005-11-12  4:49 ` [PATCH 2/13] Time: Reduced NTP Rework (part 2) john stultz
2005-11-12  4:49 ` [PATCH 3/13] Time: Clocksource Infrastructure john stultz
2005-11-12  4:49 ` [PATCH 4/13] Time: Generic Timekeeping Infrastructure john stultz
2005-11-12  4:49 ` [PATCH 5/13] Time: i386 Conversion - part 1: Move timer_pit.c to i8253.c john stultz
2005-11-12  4:49 ` [PATCH 6/13] Time: i386 Conversion - part 2: Move timer_tsc.c to tsc.c john stultz
2005-11-12  4:49 ` [PATCH 7/13] Time: i386 Conversion - part 3: Rework TSC Support john stultz
2005-11-12  4:49 ` [PATCH 8/13] Time: i386 Conversion - part 4: ACPI PM variable renaming john stultz
2005-11-12  4:49 ` [PATCH 9/13] Time: i386 Conversion - part 5: Enable Generic Timekeeping john stultz
2005-11-12  4:49 ` [PATCH 10/13] Time: i386 Conversion - part 6: Remove Old Code john stultz
2005-11-12  4:50 ` [PATCH 11/13] Time: x86-64 Conversion to Generic Timekeeping john stultz
2005-11-12  4:50 ` [PATCH 12/13] Time: i386/x86-64 Clocksource Drivers john stultz
2005-11-12  4:50 ` [PATCH 13/13] Time: Generic Timekeeping Paraniod Debug Patch john stultz
2005-11-13  1:24 ` [PATCH 0/13] Time: Generic Timeofday Subsystem (v B10) Andi Kleen
2005-11-13  2:34   ` john stultz
2005-11-13  7:32   ` Ingo Molnar
2005-11-13 10:53     ` Andi Kleen
2005-11-14 17:41       ` john stultz
2005-11-14 18:23       ` Ingo Molnar
2005-11-14 21:22 ` Frank Sorenson
2005-11-14 21:38   ` john stultz
2005-11-14 21:53     ` Frank Sorenson
2005-11-14 22:02       ` john stultz [this message]
2005-11-14 23:07         ` Frank Sorenson
2005-11-14 23:25           ` john stultz
2005-11-15  5:04             ` Frank Sorenson
2005-11-15 19:53               ` john stultz
2005-11-15 20:53                 ` Ingo Molnar
2005-11-15 21:04                   ` john stultz

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=1132005736.4668.34.camel@leatherman \
    --to=johnstul@us.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=frank@tuxrocks.com \
    --cc=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nacc@us.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=ulrich.windl@rz.uni-regensburg.de \
    --cc=zippel@linux-m68k.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