From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Heinick, J Michael" <Michael.Heinick@Honeywell.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Xenomai/Cobalt on i7-3770S CPU
Date: Wed, 8 Jun 2016 21:39:11 +0200 [thread overview]
Message-ID: <20160608193911.GA31360@hermes.click-hack.org> (raw)
In-Reply-To: <D9EDB4F689BF9F4EA6F2158A073942732E8007D6@de08ex3008.global.ds.honeywell.com>
On Wed, Jun 08, 2016 at 09:42:26AM +0000, Heinick, J Michael wrote:
>
> We currently have an RTDM driver that is running well on Xenomai/Cobalt 3.0.1 on 2 Dell computers with Core2 processors, but will hang (unresponsive mouse and keyboard, no discernable activity) an entire SuperLogics i7 computer with a Core i7-3770S processor (4 physical cores, 4 logical cores). The hang occurs in the ioctl function at an rtdm_sem_down call that waits for the interrupt handler to signal the handling of an interrupt. We suspect that we have a problem with our kernel build/installation configuration options. We have attempted to configure the Core i7-3770S system so that Xenomai/Cobalt only uses 2 cores like the other 2 working Core2 computers, but the system still hangs (more detail on the results of our attempt is included beow). Eventually, we would like to configure Xenomai/Cobalt to run on 4 cores of the i7 computer if possible.
>
> Any suggestions to help us make/install/configure Xenomai/Cobalt to run on the SuperLogics computer with the i7-3770S processor so that the rtdm_sem_down call in the RTDM driver does not hang the entire system would be appreciated.
This sounds like an irq conflict: a device handled by an RTDM driver
can not use the same irq line as a device handled by a plain Linux
driver without modifying the plain Linux driver. See FAQ for
solutions to that problem.
--
Gilles.
https://click-hack.org
next prev parent reply other threads:[~2016-06-08 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 9:42 [Xenomai] Xenomai/Cobalt on i7-3770S CPU Heinick, J Michael
2016-06-08 19:39 ` Gilles Chanteperdrix [this message]
2016-06-09 17:32 ` Heinick, J Michael
2016-06-09 17:41 ` Gilles Chanteperdrix
2016-06-10 17:03 ` Jan Kiszka
2016-06-16 15:51 ` Heinick, J Michael
2016-06-16 17:16 ` Gilles Chanteperdrix
2016-06-17 13:25 ` Heinick, J Michael
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=20160608193911.GA31360@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Michael.Heinick@Honeywell.com \
--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.