From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Daniel M. Drucker, Ph.D." <dmd@interactive-motion.com>
Cc: Andrew Tannenbaum <trb@interactive-motion.com>, xenomai@xenomai.org
Subject: Re: [Xenomai] x86 Linux with xenomai and i915 graphics stall
Date: Fri, 25 Jan 2013 12:44:50 +0100 [thread overview]
Message-ID: <51027032.7010009@xenomai.org> (raw)
In-Reply-To: <CAD1Etohk3SO-dtSOUSPrwgA-oDFfQAMt_eJK9PYMrVWhO=SJjw@mail.gmail.com>
On 01/24/2013 11:22 PM, Daniel M. Drucker, Ph.D. wrote:
> Hi Gilles et al.,
>
> We tried setting processor type more correctly, turning off CONFIG_M686
> and turning on CONFIG_MCORE2, and also turned off CONFIG_X86_GENERIC.
>
> That change has caused our worst latencies to drop to around 200us, but
> those are actually rare - we can only [but reliably] trigger that by
> using glxgears with a very large (1200x700 or larger or so) window size.
> (Other things we tried had no latency-increasing effects - we tried
> heavy disk and network activity, playing youtube videos, etc.)''
>
> /proc/ipipe/trace/frozen, without glxgears running: http://ix.io/46I
> with glxgears running: http://ix.io/46J
It would be interesting to know what happens on other cpus at the time
when this happens. Or could you try forcing glxgears to run on the same
CPU as the latency test?
>
> Log of latency: http://ix.io/46L
>
> And.... here is a video of the
> problem: http://www.youtube.com/watch?v=l4rYvhqZql8
> (problem starts at about 0:41)
>
> Can you think of anything else we could try? We've tried enabling SMI
Yes, but did you run dmesg | grep SMI to see if your chipset is acutally
supported?
Have you tried to turn off graphic acceleration in X window configuration?
--
Gilles.
next prev parent reply other threads:[~2013-01-25 11:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 22:23 [Xenomai] x86 Linux with xenomai and i915 graphics stall Daniel M. Drucker, Ph.D.
2013-01-22 22:27 ` Gilles Chanteperdrix
2013-01-22 22:29 ` Daniel M. Drucker, Ph.D.
2013-01-22 22:47 ` Gilles Chanteperdrix
[not found] ` <CAD1EtogPNsGWkA0_puttwFTGMfZ6aW1_1WniND0GRJYRba389Q@mail.gmail.com>
2013-01-24 22:22 ` Daniel M. Drucker, Ph.D.
2013-01-25 11:44 ` Gilles Chanteperdrix [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-21 23:04 A User
2013-01-21 23:13 ` Gilles Chanteperdrix
2013-01-22 19:32 ` A User
2013-01-22 19:37 ` Gilles Chanteperdrix
2013-04-13 13:27 ` Gilles Chanteperdrix
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=51027032.7010009@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=dmd@interactive-motion.com \
--cc=trb@interactive-motion.com \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.