From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] 3.14 hangs with ipipe patch applied
Date: Thu, 14 May 2015 18:28:31 +0200 [thread overview]
Message-ID: <20150514162831.GH3759@hermes.click-hack.org> (raw)
In-Reply-To: <20150514162351.GE6169@csclub.uwaterloo.ca>
On Thu, May 14, 2015 at 12:23:51PM -0400, Lennart Sorensen wrote:
> On Wed, May 13, 2015 at 04:38:33PM -0400, Lennart Sorensen wrote:
> > On Wed, May 13, 2015 at 10:37:43PM +0200, Gilles Chanteperdrix wrote:
> > > On Wed, May 13, 2015 at 04:33:01PM -0400, Lennart Sorensen wrote:
> > > > Any suggestion for what part of the code to look at to explain what
> > > > could be happening right after the timer is enabled?
> > >
> > > Sorry, nothing more to suggest than what is already in the porting guide.
> >
> > I am trying to check that the 3.12 and 3.14 configs don't have some
> > stupid difference I missed.
>
> OK it is getting stuck here:
>
> static bool hvc_dcc_check(void)
> {
> unsigned long time = jiffies + (HZ / 10);
>
> /* Write a test character to check if it is handled */
> __dcc_putchar('\n');
>
> // it gets here
> while (time_is_after_jiffies(time)) {
> if (!(__dcc_getstatus() & DCC_STATUS_TX))
> return true;
> }
> // it never gets here
>
> return false;
> }
>
> Any idea how the ipipe patch (even with CONFIG_IPIPE=n) causes that look
> to get stuck forever?
The DCC should not be used with SMP for the obvious reason shown by
this code. I observed bugs on Zynq without the I-pipe patch.
Now the second obvious thing is that if time_is_after_jiffies() does
not make progress, it is because the timer does not tick. Once
again, how to debug this is explained in the troubleshooting section
of the porting guide.
--
Gilles.
next prev parent reply other threads:[~2015-05-14 16:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 20:33 [Xenomai] 3.14 hangs with ipipe patch applied Lennart Sorensen
2015-05-13 20:37 ` Gilles Chanteperdrix
2015-05-13 20:38 ` Lennart Sorensen
2015-05-14 16:23 ` Lennart Sorensen
2015-05-14 16:28 ` Gilles Chanteperdrix [this message]
2015-05-14 16:47 ` Lennart Sorensen
2015-05-14 19:34 ` Lennart Sorensen
2015-05-21 16:32 ` Lennart Sorensen
2015-05-21 16:34 ` Gilles Chanteperdrix
2015-05-21 16:59 ` Lennart Sorensen
2015-05-21 17:03 ` Gilles Chanteperdrix
2015-05-21 17:04 ` Lennart Sorensen
2015-05-21 17:07 ` Lennart Sorensen
2015-05-21 17:10 ` Gilles Chanteperdrix
2015-05-21 17:13 ` Lennart Sorensen
2015-05-21 17:16 ` Lennart Sorensen
2015-05-21 17:20 ` Gilles Chanteperdrix
2015-05-21 17:26 ` Lennart Sorensen
2015-05-21 17:29 ` Lennart Sorensen
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=20150514162831.GH3759@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=lsorense@csclub.uwaterloo.ca \
--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.