Michael Stocks wrote: > >> Hello, > > > I've found that after one or more sends (which don't get to the bus) an > 'ifconfig can0 down' will flush the first unsent message onto the bus, all > other unsent messages are lost. > >>> Using the same hardware with my previous image, kernel 2.6.30 using out >>> of kernel (svn) socketcan everything works. >>> Using vcan instead of real hardware everything thing works OK. > > I'll try the SVN driver to see if I get different behaviour. > >>> I did a trawl of the net before posting and found a similar thread in >>> the socketcan-core forum but there was no conclusion. > > I'll see if I can find the patch and give that a go as well. > I need to solve this problem so any other hints or ideas would be welcome. > > Cheers Mike. >
Hi Mike! Did you succeed? I have same problem here with a system based on i.MX. But I have two applications running on the same system using the same bus but different NodeIDs. The first packets can be exchanged without any problem, then I only see 'No buffer space available'. The rest of the story is exactly like yours. (Unfortunately I just stepped into CAN and may be I need a helping hand in patching and recompiling it. Still crawling the docs...) Ulrich ----- Best regards Ulrich -- View this message in context: http://old.nabble.com/write%3A-No-buffer-space-available-tp29329439p30729007.html Sent from the Socket-CAN Users mailing list archive at Nabble.com. _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
