mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jerry Cooperstein <coop@axian.com>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, hemminger@osdl.org
Subject: Re: seqlock/unlock(&xtime_lock) problems cause keyboard, time skew problems
Date: Tue, 18 Mar 2003 16:21:19 -0800	[thread overview]
Message-ID: <20030319002119.GA5351@p3.attbi.com> (raw)
In-Reply-To: <200303182340.h2INeE4r098586@northrelay04.pok.ibm.com>

On Tue, Mar 18, 2003 at 03:34:32PM -0800, john stultz wrote:
... 
> Check the boot msgs. You're kernel is compiled w/ CONFIG_X86_TSC, so it
> should print a warning as such stating it is ignoring the notsc option.

yep, I missed it, the experiment was never performed.

> 
> Try compiling the kernel for i386 and the kernel then boot w/ notsc. Do be
> warned, if you're running w/ an i686 compiled glibc your box will hang
> after the "Freeing unused kernel memory: " msg. 

I compiled for no TSC using Stephen Hemminger's patch -- that worked.

> 
> Another thing to check is if the lost-tick compensation code is biting you.
> Try commenting out the "detect_lost_tick()" call from timer_interrupt() in
> arch/i386/kernel/time.c

I will try that out too, even though problem now seems 'solved.'

> 
> Let me know if that changes anything.
> 
> thanks
> -john

thanks

coop



  reply	other threads:[~2003-03-19  0:11 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 [this message]
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

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=20030319002119.GA5351@p3.attbi.com \
    --to=coop@axian.com \
    --cc=hemminger@osdl.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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®