mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jerry Cooperstein <coop@axian.com>
To: linux-kernel@vger.kernel.org
Subject: seqlock/unlock(&xtime_lock) problems cause keyboard, time skew problems
Date: Tue, 18 Mar 2003 11:05:57 -0800	[thread overview]
Message-ID: <20030318190557.GA14447@p3.attbi.com> (raw)

Since 2.5.60 my thinkpad keyboard repeat rate has been erratic when
started up on battery power; plugging into AC after startup only makes
it worse.  Starting up on AC is fine.  Compiling without apm in any
form is fine.

I posted on this a month ago and noone had solutions although I got
several emails from folks with similarly afflicted machines.

Since then I've noticed that I also get a bad time skew, with the
system clock jumping forward.

I'm pretty sure the problem arose with the introduction of the
seqlock/unlock interface to protect xtime_lock instead of a regular rw
lock.  Short of trying to back the whole thing out, does any one have
similar observations, suggestions, solutions?

======================================================================
 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/               
======================================================================

             reply	other threads:[~2003-03-18 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18 19:05 Jerry Cooperstein [this message]
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

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=20030318190557.GA14447@p3.attbi.com \
    --to=coop@axian.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®