From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Andrew Bell <andrew.bell.ia@gmail.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Fwd: Socket CAN - ENOBUFS on write()
Date: Tue, 03 Jul 2012 18:21:59 +0200 [thread overview]
Message-ID: <4FF31C27.50905@pengutronix.de> (raw)
In-Reply-To: <CACJ51z0uOH3Wu1TShhVbj8hqHL-L6M8DEz0XM8o=gru01ahqqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
Hey Andew,
please subscribe to the linux-can mailinglist linux-can@vger.kernel.org.
On 07/03/2012 05:55 PM, Andrew Bell wrote:
> I saw an old mail that you wrote about fixing the problem with receiving an
> ENOBUFS error on write() with CAN. I searched the latest kernel but did
> not see the patch there. Can you tell me what has happened with this fix?
Here's no proper fix, yet. If you receive an ENOBUFS, use poll or select
to wait until you can write again. Unfortunately poll will return too
early, so that the next write will probably fail again. Just keep
trying. You can work around the problem by you increasing the
tx_queue_len of your CAN card (before ifconfig up):
ifconfig can0 txqueuelen 10000
Regards, 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: 262 bytes --]
parent reply other threads:[~2012-07-03 16:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CACJ51z0uOH3Wu1TShhVbj8hqHL-L6M8DEz0XM8o=gru01ahqqA@mail.gmail.com>]
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=4FF31C27.50905@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=andrew.bell.ia@gmail.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