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: Thu, 16 Jun 2016 19:16:05 +0200 [thread overview]
Message-ID: <20160616171605.GD32532@hermes.click-hack.org> (raw)
In-Reply-To: <D9EDB4F689BF9F4EA6F2158A073942732E801DAA@de08ex3008.global.ds.honeywell.com>
On Thu, Jun 16, 2016 at 03:51:17PM +0000, Heinick, J Michael wrote:
> problem, the stripped down driver would hang the core2 computer
> just like the i7 computer.
Are you running a graphic system? If yes, have you tried to plug a
serial console or netconsole to try and retrieve the kernel console
when the hang happens? Because if the hang is in fact a kernel oops,
the oops message may indicate what the problem is.
> Eventually, I noticed that only nrt
> handlers were specified in the ops structure. After moving our
> ioctl functions to .ioctl_rt, both the stripped down driver and
> the full driver run on both the core2 and i7 computers.
You can not call "sleeping" services from an _nrt handler. If that
is what you were doing.
> Why the core2 computers appeared to work with only the ioctl_nrt
> handler specified in the full driver and hang the i7 computer is
> still a mystery to us.
Did the two machines run with the same kernel? Or were there
differences in the kernel configuration? Like I-pipe checks
disabled/enabled?
--
Gilles.
https://click-hack.org
next prev parent reply other threads:[~2016-06-16 17:16 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
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 [this message]
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=20160616171605.GD32532@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.