public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Serge Noiraud <serge.noiraud@bull.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: RT : 2.6.12rc5 + realtime-preempt-2.6.12-rc5-V0.7.47-15
Date: Tue, 31 May 2005 15:47:04 -0400	[thread overview]
Message-ID: <1117568825.23283.5.camel@mindpipe> (raw)
In-Reply-To: <1117551231.19367.48.camel@ibiza.btsn.frna.bull.fr>

On Tue, 2005-05-31 at 16:53 +0200, Serge Noiraud wrote:
> I have a test program which made a loop in RT to mesure the system
> perturbation.
> It works finely in a tty environment.
> When I run it in an X environment ( xterm ), I get something like if I
> click the Enter key in the active window.
> If I open a new xterm, this is the new active window which receive these
> events.
> These events stop when the program stop.
> 
> I tried with X in RT and no RT : I have the problem.

Try adding:

Option "NoAccel"

to the Driver section of your X config.

Some buggy video drivers can stall the PCI bus for tens or hundreds of
*milliseconds*.  The "via" driver had this problem until I identified
the problem and the Unichrome guys fixed it.  If it goes away with
"NoAccel", then you are having the same problem.

For details search the unichrome-devel archives for "losing interrupts".

Lee


  reply	other threads:[~2005-05-31 19:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 14:53 RT : 2.6.12rc5 + realtime-preempt-2.6.12-rc5-V0.7.47-15 Serge Noiraud
2005-05-31 19:47 ` Lee Revell [this message]
2005-06-01  8:07   ` Serge Noiraud
2005-06-01  8:23     ` Ingo Molnar
2005-06-01 12:02       ` Serge Noiraud
2005-06-01 13:09         ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2005-06-06 12:12 Serge Noiraud

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=1117568825.23283.5.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=serge.noiraud@bull.net \
    /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