From: Philippe Gerum <rpm@xenomai.org>
To: Steve Deiters <SteveDeiters@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Page fault in real time task causes lockup
Date: Thu, 19 Aug 2010 07:58:57 +0200 [thread overview]
Message-ID: <1282197537.1730.411.camel@domain.hid> (raw)
In-Reply-To: <181804936ABC2349BE503168465576460FAB4A0C@exchserver.basler.com>
On Wed, 2010-08-18 at 18:05 -0500, Steve Deiters wrote:
> > It turns out my problem was caused by an interrupt storm. I
> > had set up the interrupt to propagate to the Linux domain.
> > When my rt task transferred to the Linux domain from the page
> > fault it wasn't able to clear the device interrupt flag. The
> > interrupt was reenabled at the PIC level after Linux was done
> > with it, and as soon as that happened it got interrupted again.
> >
> > My fix was to disable the interrupt at the device level as
> > soon as rt_intr_wait returns, and reenable it before calling
> > rt_intr_wait. I'm still not sure why I was getting that exception.
>
> I'm still getting exceptions like I was getting before. With the
> interrupt fix I had in there, the system stays responsive, just that
> task gets killed. I'm still trying to track down the problem.
>
> I'm using rt_intr_wait so I am synchronized with an external FPGA, but
> it is just periodic. If I replace the rt_intr_wait with a timed wait
> with rt_wait_period it does not crash. There seems to be some
> interaction with the rt_intr_wait I still do not understand.
>
> I'm trying to make sense of the exception numbers it prints in messages
> like the following. Maybe this will give me some better insight to what
> is happening.
>
> [ 24.480199] Xenomai: Switching dsp_task to secondary mode after
> exception #1792 in kernel-space at 0xc0062f48 (pid 595)
>
> I tried turning on the I-pipe tracer to get some more information, but
> it crashes on startup.
Make sure to have CONFIG_IPIPE_TRACE_VMALLOC enabled. You may also want
to check whether disabling CONFIG_IPIPE_TRACE_IRQSOFF helps.
--
Philippe.
next prev parent reply other threads:[~2010-08-19 5:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 22:15 [Xenomai-help] Page fault in real time task causes lockup Steve Deiters
2010-08-13 22:47 ` Steve Deiters
2010-08-14 13:01 ` Gilles Chanteperdrix
2010-08-14 13:19 ` Gilles Chanteperdrix
2010-08-17 15:03 ` Steve Deiters
2010-08-18 23:05 ` Steve Deiters
2010-08-19 5:06 ` Philippe Gerum
2010-08-19 5:58 ` Philippe Gerum [this message]
2010-08-19 17:05 ` Steve Deiters
2010-08-20 8:09 ` Philippe Gerum
2010-08-19 12:34 ` Gilles Chanteperdrix
2010-08-19 5:55 ` Philippe Gerum
-- strict thread matches above, loose matches on Subject: below --
2010-08-16 5:17 Andreas Glatz
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=1282197537.1730.411.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=SteveDeiters@domain.hid \
--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.