public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "K.R. Foley" <kr@cybsft.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Real-Time Preemption -RT-V0.7.51-17 - Keyboard Problems
Date: Fri, 08 Jul 2005 15:20:35 -0500	[thread overview]
Message-ID: <42CEE013.2000306@cybsft.com> (raw)
In-Reply-To: <20050708191326.GA6503@elte.hu>

Ingo Molnar wrote:
> * K.R. Foley <kr@cybsft.com> wrote:
> 
> 
>>Ingo,
>>
>>I have an issue with keys VERY SPORADICALLY repeating, SOMETIMES, when 
>>running the RT patches. The problem manifests itself as if the key 
>>were stuck but happens far too quickly for that to be the case. I 
>>realize that the statements above are far from scientific, but I can't 
>>seem to narrow it down further. 2.6.12 doesn't seem to have the 
>>problem at all, only when running the RT patches. It SEEMS to have 
>>gotten worse lately. I am attaching my config as well as the output 
>>from lspci.
>>
>>Adjusting the delay in the keyboard repeat seems to help. Any ideas?
> 
> 
> hm. Would be nice to somehow find a condition that triggers it. One 
> possibility is that something else is starving the keyboard handling 
> path. Right now it's handled via workqueues, which live in keventd. Do 
> things improve if you chrt keventd up to prio 99? Also i'd chrt the 
> keyboard IRQ thread up to prio 99 too.

I would like very much to come up with a condition that causes it. 
Unfortunately, the only event that I know of that is associated with 
this typing. :-) There does not seem to be a method to the madness.

As for bumping the priorities, I tried them all, at least the ones 
mentioned above. I also tried the timer just for grins, after changing 
the keyboard repeat delay seemed to help a bit. None of them seemed to 
help, at least not for an extended period of time.

> 
> the other possibility is some IRQ handling bug - those are usually 
> specific to the IRQ controller, so try turning off (or on) the IO-APIC 
> [if the box has an IO-APIC], does that change anything?
> 

You may be on to something here. Booting with noapic SEEMS to help.

> 	Ingo
> 


-- 
    kr

  parent reply	other threads:[~2005-07-08 20:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08 18:36 Real-Time Preemption -RT-V0.7.51-17 - Keyboard Problems K.R. Foley
2005-07-08 19:13 ` Ingo Molnar
2005-07-08 19:35   ` Doug Maxey
2005-07-08 20:03     ` Ingo Molnar
2005-07-08 20:27     ` K.R. Foley
2005-07-08 19:38   ` Dave Neuer
2005-07-08 20:35     ` K.R. Foley
2005-07-08 20:20   ` K.R. Foley [this message]
2005-07-09 18:31   ` Peter Zijlstra

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=42CEE013.2000306@cybsft.com \
    --to=kr@cybsft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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