From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Thierry Bultel <thierry.bultel@domain.hid>
Cc: xenomai@xenomai.org,
Jean-Baptiste Tredez <jean-baptiste.tredez@domain.hid>
Subject: Re: [Xenomai-help] CAN: Locked in rtdm_sem_timeddown of tx_sem; Lost TX IRQ ?
Date: Mon, 02 Apr 2012 00:15:20 +0200 [thread overview]
Message-ID: <4F78D378.6000501@domain.hid> (raw)
In-Reply-To: <4F68BDBF.2030002@domain.hid>
On 03/20/2012 06:26 PM, Thierry Bultel wrote:
> Hello,
>
> the issue I am describing here happens on a dual-core Atom (without
> hyperthreading)
>
> It is easy to reproduce with 2.6.32.7+xenomai 2.5.2, which was my
> initial configuration until
> I remembered that Philippe told us that SMP was correctly supported from
> 2.6.38.8
>
> The fact is that I have been able to reproduce it with
> 2.6.38.8+xenomai-2.6 as well. Only once, but I did.
>
> I am using CAN with a IXXAT PCI-04 board .
> There is a single thread per bus.
>
> With the old kernel, after about 400-500 seconds, and heavy load the
> communication stops, and after some
> analysis, I found out that my process was stuck at :
>
> rtcan_raw.c
>
> /* Try to pass the guard in order to access the controller */
> * ret = rtdm_sem_timeddown(&dev->tx_sem, timeout, NULL);*
>
>
> The Refcount shown in /proc/rtcan/rtcan0/info is 1.
>
> The workaround I found was to set the timeout to a non-zero value with
> the appropriate ioctl,
> and when a timeout issues, to stop and restart the bus, with the effect
> to destroy and re-recreate the semaphore and
> thus to communicate again.
>
> By reading the code, the only reason I can see is that a TX interrupt is
> lost.
>
> I do not have much more ways to analyze deeper, so any advice would be
> greatly appreciated
Have you tried xenomai 2.5.6 ?
--
Gilles.
prev parent reply other threads:[~2012-04-01 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 17:26 [Xenomai-help] CAN: Locked in rtdm_sem_timeddown of tx_sem; Lost TX IRQ ? Thierry Bultel
2012-04-01 22:15 ` Gilles Chanteperdrix [this message]
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=4F78D378.6000501@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jean-baptiste.tredez@domain.hid \
--cc=thierry.bultel@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.