From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Tim Hotfilter <thotfilter@osdr.org>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Problem using Linux CAN
Date: Sat, 25 Jul 2015 15:45:38 +0200 [thread overview]
Message-ID: <55B39302.70505@hartkopp.net> (raw)
In-Reply-To: <839E49C8-4EA6-4DE5-8901-3AAECD1435CA@osdr.org>
Hi Tim,
On 24.07.2015 09:53, Tim Hotfilter wrote:
> 1. 500kBaud results in the same problem.
> 2. The problem also occurs with the final configuration (about 5 can nodes). As i mentioned in the first mail, one node has a can-frame watchdog and turns off.
> 3. I had kernel 3.17. before. For testing I upgraded to 3.19
Hm.
> I think the problem is the stopped tx queue.
How did you get this information that the queue is stopped?
The sja1000 queue is stopped in sja1000_start_xmit() and is enabled in
sja1000_interrupt() again when the tx-ok interrupt (IRQ_TI) occurred.
So when the sja1000 has a stopped queue after some successful time of
operation the tx-ok interrupt obviously got lost.
As you have two sja1000 cores (from opencores?) in you FPGA: Do you have them
connected to separate irq lines?
> Is there any chance to implement something like a timeout function, which wakes the queue if the buffer fill level is over a threshold.
We should better try to fix the real issue than implementing workarounds like
this. There is a timeout recovery for bus-off states (restart-ms option) - but
your device does not get into bus-off.
Regards,
Oliver
prev parent reply other threads:[~2015-07-25 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 10:49 Problem using Linux CAN Tim Hotfilter
2015-07-22 17:41 ` Oliver Hartkopp
2015-07-22 17:52 ` Tim Hotfilter
2015-07-22 18:39 ` Oliver Hartkopp
[not found] ` <0948A186-060F-4A31-8359-755DE78647A0@osdr.org>
2015-07-23 13:13 ` Tim Hotfilter
2015-07-23 17:26 ` Oliver Hartkopp
2015-07-24 7:53 ` Tim Hotfilter
2015-07-25 13:45 ` Oliver Hartkopp [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=55B39302.70505@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=thotfilter@osdr.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.