From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Charles Steinkuehler <charles@steinkuehler.net>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Hung task on Xenomai patched ARM 3.8.13 BeagleBone Kernel
Date: Wed, 16 Oct 2013 17:58:26 +0200 [thread overview]
Message-ID: <525EB7A2.1050601@xenomai.org> (raw)
In-Reply-To: <525EAFFD.3010207@steinkuehler.net>
On 10/16/2013 05:25 PM, Charles Steinkuehler wrote:
> On 10/16/2013 7:52 AM, Charles Steinkuehler wrote:
>> Anyway, are there any in-between steps I can test with the kernel that
>> might help isolate what code to go over in the mmc driver? Anything
>> between "no xenomai patches" and "patched and configured to run xenomai"
>> might potentially be enlightening.
>
> I built and tested a patched kernel that has no xenomai configure
> options enabled:
>
> # CONFIG_XEN is not set
CONFIG_XEN is for Xen, not Xenomai. The interesting steps are:
- CONFIG_IPIPE enabled with CONFIG_XENOMAI disabled
- patched kernel with CONFIG_IPIPE off and CONFIG_XENOMAI off.
In addition to the troubleshooting guide, you may find the following
documentation useful:
https://www.xenomai.org/index.php/I-pipe-core:ArmPorting
If the issue is not a timer issue, and it does not seem to be, the most
probable explanation is that either the MMC driver or the interrupt
controller does not like receiving interrupts while they are masked. In
this case, you will find that the patched kernel does not work with
CONFIG_IPIPE but works with CONFIG_IPIPE off and CONFIG_XENOMAI off.
Do you know if the interrupt is level or edge triggered?
Regards.
--
Gilles.
next prev parent reply other threads:[~2013-10-16 15: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 [this message]
2013-10-16 16:12 ` Charles Steinkuehler
2013-10-16 19:41 ` Charles Steinkuehler
2013-10-17 0:58 ` Charles Steinkuehler
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=525EB7A2.1050601@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=charles@steinkuehler.net \
--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.