Re: Problem using Linux CAN

[Oliver Hartkopp <socketcan@hartkopp.net>]

On 22.07.2015 12:49, Tim Hotfilter wrote:

> I am developing a control unit using four CAN Controllers based on the Xilinx Zynq 7000. Two CAN Controllers (based on the sja1000) are implemented in the Zynq’s FPGA and two are already integrated. The control unit runs Linux 3.19 with socket can.
> Under higher CAN busload (30% or more) socket CAN returns Error 105: No buffer space available.

How did you get this error?
What tools/kernel/distro are you using?

Did you try 'cangen' from https://github.com/linux-can/can-utils ?

Regards,
Oliver

> The problem is independent from the hardware, it occurs on both sja1000 and xilinx can. Restarting the network device by bringing it down and up enables to send again. But since there are other ECUs using watchdogs this solution is not suitable.
> After some kernel debugging it exposes that somehow a transmit interrupt gets lost. This results in a stopped tx queue and the transmit buffer overflows.
>
> Is there a possibility to handle with the lost interrupt, like waking up the queue after a short timeout?
>
> Thank you in advance!
>
> Best regards
> Tim Hotfilter
>
> --
> 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
>