From: Charles Steinkuehler <charles@steinkuehler.net>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Hung task on Xenomai patched ARM 3.8.13 BeagleBone Kernel
Date: Wed, 16 Oct 2013 19:58:23 -0500 [thread overview]
Message-ID: <525F362F.6080109@steinkuehler.net> (raw)
In-Reply-To: <525EEBE2.8080708@steinkuehler.net>
On 10/16/2013 2:41 PM, Charles Steinkuehler wrote:
> On 10/16/2013 11:12 AM, Charles Steinkuehler wrote:
>> I'll test with ipipe disabled, go through the Arm Porting guide, and see
>> where that gets me...
>
> After building a patched kernel without ipipe or xenomai enabled:
>
> $ egrep '(IPIPE|XENO)' KERNEL/.config
> # CONFIG_XENOMAI is not set
> CONFIG_XENO_GENERIC_STACKPOOL=y
> CONFIG_XENO_FASTSYNCH_DEP=y
> CONFIG_XENO_FASTSYNCH=y
> # CONFIG_IPIPE is not set
>
> ...the mmc issue seems fixed. So according to the porting guide, this
> indicates a likely problem with interrupts or the interrupt controller
> (as Gilles indicated).
Based on the ARM porting guide, the first thing I did was to disable IRQ
muting by simply commenting out the two calls to:
ipipe_pic_muter_register
...in <linux>/drivers/gpio/gpio-omap.c
This results in a kernel that DOES NOT HANG with ipipe enabled!
So it looks like the issue is related to interrupt muting, and I have
two paths to push forward:
1) Build a kernel with ipipe and xenomai both enabled (but no IRQ
muting) and see if this works (and how much it affects worst-case latency)
2) Dig into the IRQ muting code and look for any goofs
I can handle #1, building and testing a kernel with IRQ muting disabled.
Can anyone advise on a good way to approach #2? Since everything
_almost_ works, I suspect a problem that could be difficult to find,
especially for someone like me who isn't really all that familiar with
the Linux kernel and ipipe internals.
--
Charles Steinkuehler
charles@steinkuehler.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20131016/330bf34d/attachment.pgp>
next prev parent reply other threads:[~2013-10-17 0:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 22:23 [Xenomai] Hung task on Xenomai patched ARM 3.8.13 BeagleBone Kernel Charles Steinkuehler
2013-10-16 10:44 ` Gilles Chanteperdrix
2013-10-16 11:10 ` Charles Steinkuehler
2013-10-16 11:13 ` Gilles Chanteperdrix
2013-10-16 11:09 ` Gilles Chanteperdrix
2013-10-16 11:38 ` Charles Steinkuehler
2013-10-16 11:50 ` Gilles Chanteperdrix
2013-10-16 12:08 ` Charles Steinkuehler
2013-10-16 12:28 ` Charles Steinkuehler
2013-10-16 12:44 ` Gilles Chanteperdrix
2013-10-16 12:52 ` Charles Steinkuehler
2013-10-16 15:25 ` Charles Steinkuehler
2013-10-16 15:58 ` Gilles Chanteperdrix
2013-10-16 16:12 ` Charles Steinkuehler
2013-10-16 19:41 ` Charles Steinkuehler
2013-10-17 0:58 ` Charles Steinkuehler [this message]
2013-10-17 2:21 ` Charles Steinkuehler
2013-10-17 9:29 ` Gilles Chanteperdrix
2013-10-17 10:24 ` Ralf Roesch
2013-10-17 12:39 ` Charles Steinkuehler
2013-10-17 15:12 ` Ralf Roesch
2013-10-17 18:43 ` Gilles Chanteperdrix
2013-11-04 12:38 ` Charles Steinkuehler
2013-10-16 18:12 ` Ralf Roesch
2013-10-16 12:51 ` Ralf Roesch
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=525F362F.6080109@steinkuehler.net \
--to=charles@steinkuehler.net \
--cc=gilles.chanteperdrix@xenomai.org \
--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.