mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jerry Cooperstein <coop@axian.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: linux-kernel@vger.kernel.org, coop@axian.com
Subject: Re: seqlock/unlock(&xtime_lock) problems cause keyboard, time skew problems
Date: Tue, 18 Mar 2003 16:27:33 -0800	[thread overview]
Message-ID: <20030319002733.GB5351@p3.attbi.com> (raw)
In-Reply-To: <1048030151.6297.71.camel@dell_ss3.pdx.osdl.net>

On Tue, Mar 18, 2003 at 03:29:11PM -0800, Stephen Hemminger wrote:
.....
> On Tue, 2003-03-18 at 14:58, Jerry Cooperstein wrote:
> > I tried turning on SpeedStep (which I didn't think I had...) and
> > I got:
> > 
> > cpufreq: Intel(R) SpeedStep(TM) for this chipset not (yet) available.
> 
> Unfortunately, Intel SpeedStep is proprietary and they won't tell Linux
> how to manage it.  The best thing might be to figure out how to force kernel
> not to use TSC on this beast.
> 
> Can you take CONFIG_X86_TSC out of your config.  Then the kernel shouldn't
> use TSC.

Well if you remove CONFIG_X86_TSC out of your .config file, the kernel
build always puts it back in (i guess it believes it knows best).  So
i just used your patch below, and indeed it does work; clock speed is
now normal as is keyboard repeat rate. Immediate problem solved 
--but case not closed. 

I have to go back and clean out the earlier patches which didn't help
on their own, but I doubt they make a difference.  I'll leave it to you
to submit this as patch to the kernel, as I'm not sure it is solving
or hiding the problem.  But it works for me:>

At any rate, there is something in the seqlock stuff that broke this
stuff.  I'll keep trying to figure out exactly what.  

Thanks for all your hard work.  I appreciate it.

======================================================================
 Jerry Cooperstein,  Senior Consultant,  <coop@axian.com>
 Axian, Inc., Software Consulting and Training
 4800 SW Griffith Dr., Ste. 202,  Beaverton, OR  97005 USA
 http://www.axian.com/               
======================================================================


> 
> Or try this patch and boot with "notsclock"
> 
> diff -Nru a/arch/i386/kernel/timers/timer_tsc.c b/arch/i386/kernel/timers/timer_tsc.c
> --- a/arch/i386/kernel/timers/timer_tsc.c	Tue Mar 18 15:28:10 2003
> +++ b/arch/i386/kernel/timers/timer_tsc.c	Tue Mar 18 15:28:10 2003
> @@ -15,6 +15,7 @@
>  #include <asm/processor.h>
>  
>  int tsc_disable __initdata = 0;
> +static int tsc_clock_disable __initdata = 0;
>  
>  extern spinlock_t i8253_lock;
>  
> @@ -241,6 +242,13 @@
>  };
>  #endif
>  
> +/* Don't use TSC for time of day clock */
> +static int __init tsc_noclock_setup(char *str)
> +{
> +	tsc_clock_disable = 1;
> +	return 1;
> +}
> +__setup("notsclock", tsc_noclock_setup);
>  
>  static int init_tsc(void)
>  {
> @@ -273,7 +281,7 @@
>  	cpufreq_register_notifier(&time_cpufreq_notifier_block, CPUFREQ_TRANSITION_NOTIFIER);
>  #endif
>  
> -	if (cpu_has_tsc) {
> +	if (cpu_has_tsc && !tsc_clock_disable) {
>  		unsigned long tsc_quotient = calibrate_tsc();
>  		if (tsc_quotient) {
>  			fast_gettimeoffset_quotient = tsc_quotient;
> 

      parent reply	other threads:[~2003-03-19  0:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18 19:05 Jerry Cooperstein
2003-03-18 20:32 ` Stephen Hemminger
2003-03-18 20:59   ` Jerry Cooperstein
2003-03-18 23:34     ` john stultz
2003-03-19  0:21       ` Jerry Cooperstein
2003-03-19  0:38         ` [PATCH] boot time parameter to turn of TSC usage Stephen Hemminger
2003-03-19  0:39           ` Andrew Morton
2003-03-19  1:03             ` Stephen Hemminger
2003-03-18 23:57     ` seqlock/unlock(&xtime_lock) problems cause keyboard, time skew problems Stephen Hemminger
     [not found]     ` <1048022686.6291.6.camel@dell_ss3.pdx.osdl.net>
     [not found]       ` <20030318214101.GA4527@p3.attbi.com>
     [not found]         ` <1048025052.6294.16.camel@dell_ss3.pdx.osdl.net>
     [not found]           ` <20030318222313.GA4831@p3.attbi.com>
     [not found]             ` <1048027027.6297.33.camel@dell_ss3.pdx.osdl.net>
     [not found]               ` <20030318225801.GC4831@p3.attbi.com>
     [not found]                 ` <1048030151.6297.71.camel@dell_ss3.pdx.osdl.net>
2003-03-19  0:27                   ` Jerry Cooperstein [this message]

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=20030319002733.GB5351@p3.attbi.com \
    --to=coop@axian.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@osdl.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

all inboxes | Powered by JetHome®