From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Daniel M. Drucker, Ph.D." <dmd@interactive-motion.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] x86 Linux with xenomai and i915 graphics stall
Date: Tue, 22 Jan 2013 23:47:05 +0100 [thread overview]
Message-ID: <50FF16E9.7050902@xenomai.org> (raw)
In-Reply-To: <CAD1EtoiMKsipxzaDZOHFHfzQWRX1Oub=HspCCn01UNC3C9e53A@mail.gmail.com>
On 01/22/2013 11:29 PM, Daniel M. Drucker, Ph.D. wrote:
>
> And you are sure that it is not an SMI issue? Could you post your kernel
> configuration?
>
>
> Here it
> is: https://gist.github.com/raw/4599242/0eea44377371e4d7213eea28cd33823950afeaca/gistfile1
You can try disabling CONFIG_PM_RUNTIME
What could take long in __xnpod_schedule is locking the spinlock, that
could be because another CPU has the lock, in which case you will be
able to catch the culprit by enabling CONFIG_XENO_OPT_DEBUG_XNLOCK
or because the bus is locked for a long time, you could also try
disabling CONFIG_MTRR or CONFIG_X86_PAT.
Finally, what may happen is an NMI, the perf system uses NMIs and
oprofile as well. You can avoid compiling oprofile, but I am not sure
perf can be disabled, but you can comment out the code enabling the NMI
with the following patch:
diff --git a/arch/x86/kernel/cpu/perf_event.c
b/arch/x86/kernel/cpu/perf_event.c
index bb8e034..a26df66 100644
--- a/arch/x86/kernel/cpu/perf_event.c
+++ b/arch/x86/kernel/cpu/perf_event.c
@@ -1324,6 +1324,8 @@ static int __init init_hw_perf_events(void)
struct event_constraint *c;
int err;
+ return 0;
+
pr_info("Performance Events: ");
switch (boot_cpu_data.x86_vendor) {
--
Gilles.
next prev parent reply other threads:[~2013-01-22 22:47 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 [this message]
[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
-- 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=50FF16E9.7050902@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=dmd@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.