From: Wolfgang Grandegger <wg@grandegger.com>
To: Steffen Rose <ro@emtas.de>
Cc: linux-can@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: unsure - socketCAN blocking
Date: Mon, 08 Oct 2012 16:56:37 +0200 [thread overview]
Message-ID: <5072E9A5.2060908@grandegger.com> (raw)
In-Reply-To: <1722972.yqiF7qX92T@lisa>
On 10/08/2012 04:36 PM, Steffen Rose wrote:
> Hello,
>
> Am Montag, 8. Oktober 2012, 13:46:06 schrieb Marc Kleine-Budde:
>>> I use:
>>> Virtual box - Host Win 7/Guest kubuntu
>>> Linux lisa 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012
>>> x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> SocketCAN connector is a EMS CPC-USB.
>
> [...]
>
>> Your program probably produces CAN frames faster than they could be
>> delivered by your CAN hardware. Your choices are:
>
> I'm unsure.
> My CPU load is high. My application polling is not optimal at the moment. But
> the CAN busload is not so high.
>
> At the moment I would think, it is more a problem internal or on USB. I'm
> unsure. I search information to analyze the current situation.
>
>> 2) Increase txqueue length to 10000 or so.
>> (ifconfig can0 txqueuelen 10000)
>
> I did it.
>
> after a little bit time...
Did it run longer than before? Anyway, the candump utility shows how to
count messages dropped because the queue was full. Search for the option
"-d".
>
> Now my error:
> write: Interrupted system call
Hm, who has interrupted the write system call? gdb?
>
>
> $ ./candump can0
Please use "candump can0 any,0:0,#FFFFFFFF" to also see error messages.
>
> I see nothing.
Maybe error frames?
> But: There is traffic on the CAN and the USB traffic light of the CPC-USB is
> blinking. Means, the CAN-USB transfer data from the CAN to the socketcan CAN
> driver.
>
> Can I see more states about the can, can_raw or the ems_usb modules?
The stats below should tell you if you still receive messages.
>
> $ ip -det -stat link show can0
> 4: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen
> 10000
> link/can
> can state ERROR-ACTIVE restart-ms 0
> bitrate 250000 sample-point 0.875
> tq 250 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1
> ems_usb: tseg1 1..16 tseg2 1..8 sjw 1..4 brp 1..64 brp-inc 1
> clock 8000000
> re-started bus-errors arbit-lost error-warn error-pass bus-off
> 0 19 0 1 1 0
You seemed to have electrical problem on the bus. Not sure if it's
related, though.
Wolfgang.
next prev parent reply other threads:[~2012-10-08 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 10:16 unsure - socketCAN blocking Steffen Rose
2012-10-08 11:46 ` Marc Kleine-Budde
2012-10-08 14:36 ` Steffen Rose
2012-10-08 14:56 ` Wolfgang Grandegger [this message]
2012-10-08 15:00 ` Marc Kleine-Budde
2012-10-08 15:21 ` Steffen Rose
2012-10-08 15:19 ` Steffen Rose
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=5072E9A5.2060908@grandegger.com \
--to=wg@grandegger.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=ro@emtas.de \
/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