All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Meier <matthias.j.meier@gmx.net>
To: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: Long max latencies on Wandbaord / Freescale i.MX6
Date: Thu, 1 Oct 2015 10:08:18 +0200	[thread overview]
Message-ID: <560CE9F2.4010401@gmx.net> (raw)
In-Reply-To: <alpine.DEB.2.11.1509300909240.4500@nanos>

PROVE_LOCKING is not so bad I thought

finally I guess my latency problem is caused by a spurious interrupt on 
a unused mmc slot causing heavy load when using PROVE_LOCKING ...


Here a little more in detail what I did:

Disabling CONFIG_PROVE_LOCKING together with a lot other debug options 
as Thomas proposed indeed gave max latencies in the range of 100us - at 
least most of the time...

After adding besides 'hackbench' additional heavy network load via the 
on-board WiFi interface, the max latency raised further and finally I 
the kernel fired a backtrace which ended in a "Disabling IRQ #284"

/proc/interrupts indeed shows a hugh amout of interrupts on mmc1 
although I don't use mmc1 at all (the Wandboard boots via mmc0)

(possible a pullup config is missing at the mmc interfaces?)

After reboot I tried to stop the spurious interrupts by inserting a 
sd-card on mmc1 but this does not work - still high interrupts.

Now I'm trying to disable mmc1 and mmc2 completely which is not as easy 
as I thought: via sysfs it seems not to be possible and via DT I think I 
would have to modify all imx6* DTS files of all imx6 boards - otherwise 
the dtbs does not compile...


Is there a simple solution to disable either a single interrupt or a 
individual mmc interface from userspace?

Thanks,
	Matthias


  reply	other threads:[~2015-10-01  8:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-26  9:38 Long max latencies on Wandbaord / Freescale i.MX6 Matthias Meier
2015-09-26 14:16 ` Joe Korty
2015-09-26 14:52   ` Matthias Meier
2015-09-27 11:49 ` Thomas Gleixner
2015-09-29  6:30   ` Matthias Meier
2015-09-29  7:04     ` Re[2]: " Matthias Klein
2015-09-30  7:11     ` Thomas Gleixner
2015-10-01  8:08       ` Matthias Meier [this message]
2015-10-02  6:48       ` Matthias Meier
2015-10-02  7:40         ` Mats Karrman

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=560CE9F2.4010401@gmx.net \
    --to=matthias.j.meier@gmx.net \
    --cc=linux-rt-users@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 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.