linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "Michael Thénault" <michael.thenault@gmail.com>
Cc: linux-can@vger.kernel.org
Subject: Re: write: No buffer space available
Date: Thu, 07 Mar 2013 17:36:27 +0100	[thread overview]
Message-ID: <5138C20B.1070306@hartkopp.net> (raw)
In-Reply-To: <CACekSAN4Roq50mr7+2P5Fk8zxY6hSOErqgrxu-3sLbyS7SzwJQ@mail.gmail.com>

Hello Michael,

there are more than one threads handling the "no buffer space" question :-)

Usually there is no correct CAN network attached to the CAN interface, means:

- there is a least a second CAN node which can acknowledge the sent CAN frames
- the bitrate is identical for all CAN nodes
- the CAN bus is terminated properly (with 2x 120 = 60 Ohms)

If you have a working CAN network try to attach your Linux box and read the
data from the working environment first.

So you can be sure, that the bitrate settings and terminations are correct.

Regards,
Oliver


On 07.03.2013 10:55, Michael Thénault wrote:

> hello,
> 
> I'm working on a arm system with the 2.6.38.8 kernel.
> When I try to send can frames (with cansend, cangen or sockets) the tx
> queue is getting full and then i get this error :
> 
> write: No buffer space available
> 
> I've been monitoring the CAN bus with an oscilloscope and nothing
> seems to happen.
> I saw a thread with the similar problem, and there was some problem
> with the one-shot mode. This mode doesn't work with me :
> 
> # ip link set can0 up type can one-shot on
> RTNETLINK answers: Operation not supported
> 
> here are some details :
> 
> # ip -details -statistics link show can0
> 4: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN qlen 10
>     link/can
>     can state ERROR-PASSIVE restart-ms 0
>     bitrate 125000 sample-point 0.875
>     tq 500 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1
>     mcp251x: tseg1 3..16 tseg2 2..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          0          0          4          4          0
>     RX: bytes  packets  errors  dropped overrun mcast
>     0          0        0       0       0       0
>     TX: bytes  packets  errors  dropped carrier collsns
>     0          0        3       3       0       0
> 
> what am i doing wrong ?
> Thank you in advance for your help
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2013-03-07 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07  9:55 write: No buffer space available Michael Thénault
2013-03-07 16:36 ` Oliver Hartkopp [this message]
2013-03-08 10:24   ` Michael Thénault
2013-03-08 10:39     ` Max S.

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=5138C20B.1070306@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=linux-can@vger.kernel.org \
    --cc=michael.thenault@gmail.com \
    /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).