From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Cc: Jeroen Lammertink <jeroen.lammertink@nl.abb.com>
Subject: Re: Fwd: Loosing CAN messages with socket-CAN
Date: Wed, 03 Apr 2013 17:17:13 +0200 [thread overview]
Message-ID: <515C47F9.20708@pengutronix.de> (raw)
In-Reply-To: <515C064F.2060503@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2243 bytes --]
On 04/03/2013 12:37 PM, Marc Kleine-Budde wrote:
> We are sending batches of 80 CAN messages using socket CAN to transfer an
> image for download. After the 80 messages we wait for a response
Are you evaluating the return value of the write() or sendmsg() systemcall?
> consisting of a single CAN message. Within the messages we have coded a
> sequence number, so that we can detect lost messages. Besides the CAN
> device that is subject of download, we have also a (hardware) CAN sniffer
> on the CAN bus. We typically log CAN messages when we put them in the
> socket. With this set-up we typically detect loosing a short series of
> (mostly 5) CAN messages, somewhere halfway the batch of 80. No other
> devices are present on the CAN bus.
>
> I've dumped below some version and set-up info of Ubuntu, socket-can and
> ifconfig.
>
> Is this problem known?
> May this problem be related to using an old version of socket can?
This is either a userspace problem or a buggy driver. The driver problem
may have been fixed in the meantime.
> How can I upgrade Ubuntu to the latest versions of socket-can?
First we have to figure out what's brokoen.
> Thanks in advance,
>
> Jeroen Lammertink
>
>
> bmterra@q7buntu:~/user/jla$ uname -a
> Linux q7buntu 3.5.0-26-generic #42~precise1-Ubuntu SMP Mon Mar 11 22:19:42
> UTC 2013 i686 i686 i386 GNU/Linux
> bmterra@q7buntu:~/user/jla$ cat /proc/net/can/version
> rev 20090105 abi 8
> bmterra@q7buntu:~/user/jla$ ifconfig can0
> can0 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> UP RUNNING NOARP MTU:16 Metric:1
> RX packets:1128 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4400 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1024
> RX bytes:9024 (9.0 KB) TX bytes:34176 (34.1 KB)
> Interrupt:18
Which CAN hardware are you using?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2013-04-03 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFFDCA8F9E.6364F5F1-ONC1257B42.00342754-C1257B42.003887D3@de.abb.com>
2013-04-03 10:37 ` Fwd: Loosing CAN messages with socket-CAN Marc Kleine-Budde
2013-04-03 15:17 ` Marc Kleine-Budde [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=515C47F9.20708@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=jeroen.lammertink@nl.abb.com \
--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).