public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Frank Sorenson <frank@tuxrocks.com>,
	linux-kernel@vger.kernel.org, David Gerber <dg-lkml@zapek.com>
Subject: Re: Keyboard Stuttering
Date: Tue, 10 Oct 2006 11:25:14 -0700	[thread overview]
Message-ID: <1160504714.4973.6.camel@localhost> (raw)
In-Reply-To: <d120d5000610101009h49904afeq61b8e7f5dab79346@mail.gmail.com>

On Tue, 2006-10-10 at 13:09 -0400, Dmitry Torokhov wrote:
> On 10/6/06, David Gerber <dg-lkml@zapek.com> wrote:
> > > I'm experiencing some severe keyboard stuttering on my laptop.  The
> > > problem is particularly bad in X, and I believe it also occurs at the
> > > console, though I'm having a difficult time verifying that.  The problem
> > > shows up as repeated characters (not regular key-repeat-related), and
> > > sometimes dropped key presses.
> >
> > (I'm not subscribed to the list, CC: to me if needed)
> >
> > Same problem here. Intel Core 2 Duo with 2.6.19-rc1 x86_64 SMP. Happens on
> > 2.6.17 too. I use 'noapic' as a workaround but that disables one of the CPU
> > core of course.
> >
> > I cannot reproduce the problem within the console nor gdm. Only on the X
> > desktop.
> >
> 
> John,
> 
> It looks like the only clocksource available on David's box is
> "jiffies" although the processor shows that it supporst tsc and PM
> timer is enabled and I think that this is what causes keyboard
> stuttering in X. See http://bugzilla.kernel.org/show_bug.cgi?id=7291.
> I believe clocksources is your turf, could you please take a look at
> this.

Sure thing. I followed up in the bug, but I don't think the clocksource
code is involved. x86_64 hasn't converted to GENERIC_TIME, so jiffies is
what we use to increment xtime, but the TSC, ACPI PM, or HPET is used
for gettimeofday, etc. 

I suspect C3 idling is the culprit, since noapic works around the issue.

thanks
-john


  reply	other threads:[~2006-10-10 18:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 10:18 Keyboard Stuttering David Gerber
2006-10-06 20:24 ` Frank Sorenson
2006-10-10 17:09 ` Dmitry Torokhov
2006-10-10 18:25   ` john stultz [this message]
2006-10-12 16:12     ` Lee Revell
2006-10-13 20:45       ` john stultz
2006-10-16 10:59         ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2006-10-04 18:15 Frank Sorenson
2006-10-04 20:47 ` Rok Markovic

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=1160504714.4973.6.camel@localhost \
    --to=johnstul@us.ibm.com \
    --cc=dg-lkml@zapek.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=frank@tuxrocks.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