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: Thu, 17 Oct 2013 11:29:30 +0200 [thread overview]
Message-ID: <525FADFA.2020009@xenomai.org> (raw)
In-Reply-To: <525F362F.6080109@steinkuehler.net>
On 10/17/2013 02:58 AM, Charles Steinkuehler wrote:
> 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!
It does not really make sense: when I-pipe is enabled but Xenomai
disabled, the PIC muting is only used to tweak the interrupt controller
priority. Since there are only secondary mode irqs, they all should use
the same priority.
Is arch/arm/mach-omap2/irq.c modified by the BeagleBone patches, if yes,
could you put the modified version somewhere I could have a look at it?
Regards.
--
Gilles.
next prev parent reply other threads:[~2013-10-17 9:29 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
2013-10-17 2:21 ` Charles Steinkuehler
2013-10-17 9:29 ` Gilles Chanteperdrix [this message]
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=525FADFA.2020009@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.