From: Wolfgang Grandegger <wg@grandegger.com>
To: Henrik Bork Steffensen <hbs@rosetechnology.dk>
Cc: linux-can@vger.kernel.org
Subject: Re: at91_can.c: Data transmission stops
Date: Mon, 26 Nov 2012 16:25:10 +0100 [thread overview]
Message-ID: <50B389D6.4050308@grandegger.com> (raw)
In-Reply-To: <50B37C90.3040904@rosetechnology.dk>
On 11/26/2012 03:28 PM, Henrik Bork Steffensen wrote:
> Hi All,
>
> We use the canopen on an at91sam9263, and experience a can problem.
> Sometimes data transmission simply stops. Data reception continues
> normally.
>
> Reloading the at91_can module seems to be the only action to bring our
> system back on can.
> When we experience this problem, the TXF counter in /proc/net/can/stats
> is frozen.
>
> I have followed the thread on a similar issue "pch_can", and I was
> wondering
> if this is the same problem, and if the real problem might be in a
> higher level.
>
> In our case the lockup occurs approximately 1 time in 50 days.
:(
> I tried reducing the number of mailboxes used for TX, from 4 to 1.
> That seem to increase the frequency of this lockup by a factor 2-5.
> These numbers are very uncertain due to the randomness and rarity of
> this bug.
>
> Some numbers to give an impression of our system:
> 125 kbit bus speed
> can bus load <1%
> max tx burst 1-6 telegrams, rx is a little bit higher.
> 240MHz ARM 9 (at91sam9263B)
> 2.6.32 kernel, with at91_can (and related files) patched with a few
> important fixes.
> I would like to move to a recent kernel, but that is not possible right
> now.
>
>
> I am considering protecting tx objects as Wolfgang suggests in the
> pch_can thread.
This problem is with SMP in the first place. Can you show your .config.
The c_can driver uses similar code than the at91_can and they have
therefore the same issues if the kernel is preemptable, IIUC. Should not
be a big deal to adapt the following patch:
http://marc.info/?l=linux-can&m=135391821814519&w=2
Wolfgang.
next prev parent reply other threads:[~2012-11-26 15:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 14:28 at91_can.c: Data transmission stops Henrik Bork Steffensen
2012-11-26 15:25 ` Wolfgang Grandegger [this message]
2012-11-26 16:29 ` Henrik Bork Steffensen
2012-11-27 14:11 ` Henrik Bork Steffensen
2012-11-27 16:31 ` Wolfgang Grandegger
2012-11-28 14:22 ` Henrik Bork Steffensen
2012-11-28 14:29 ` Marc Kleine-Budde
2012-11-28 15:09 ` Henrik Bork Steffensen
2012-11-28 15:12 ` Marc Kleine-Budde
2012-11-28 15:44 ` Henrik Bork Steffensen
2012-11-28 16:23 ` Wolfgang Grandegger
2012-12-03 16:13 ` Henrik Bork Steffensen
2012-11-28 14:38 ` Wolfgang Grandegger
2012-11-28 15:17 ` Henrik Bork Steffensen
2012-11-28 14:56 ` Marc Kleine-Budde
2012-11-28 15:17 ` Wolfgang Grandegger
2012-11-26 16:36 ` Marc Kleine-Budde
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=50B389D6.4050308@grandegger.com \
--to=wg@grandegger.com \
--cc=hbs@rosetechnology.dk \
--cc=linux-can@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).