Re: SocketCAN stops read after RX overflow, is it normal?

From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Guillaume Picquet <guillaume@picquet.fr>
Cc: linux-can@vger.kernel.org
Subject: Re: SocketCAN stops read after RX overflow, is it normal?
Date: Thu, 03 Sep 2015 11:16:35 +0200	[thread overview]
Message-ID: <8605150.LGJ155yN3b@ws-stein> (raw)
In-Reply-To: <55E6CCC8.7010908@picquet.fr>

Hi Guillaume,

On Wednesday 02 September 2015 12:17:44, Guillaume Picquet wrote:
> I’m doing tests on embedded hardware with integrated CAN bus interface 
> (based on AT91). The driver provides Linux Socket API and I try to see 
> the limits:
> I have one transmitter that writes CAN frames (CAN_RAW) as fast as 
> possible and a receiver that reads continuously.
> After a moment the receiver gets an error frame signalling RX overflow. 
> I have no problem with that, it's normal and expected.
> But question is why at this point no more frame is received ?
> 
> read() do not return, I've tested also with select() which return timeout.
> (The restart-ms option is set)
> 
> I expected some dropped frames and others RX buffer errors but not the 
> end of reception.

Maybe you are hitting the same problem as I was last year: http://marc.info/?l=linux-can&m=141225364212703&w=2
It seems the at91_can driver hasn't changed essentially since that time. So please give the patches Marc sent today a try.

Best regards,
Alexander
-- 
Dipl.-Inf. Alexander Stein
SYS TEC electronic GmbH
alexander.stein@systec-electronic.com

Legal and Commercial Address:
Am Windrad 2
08468 Heinsdorfergrund
Germany

Office: +49 (0) 3765 38600-0
Fax:    +49 (0) 3765 38600-4100

Managing Directors:
	Director Technology/CEO: Dipl.-Phys. Siegmar Schmidt;
	Director Commercial Affairs/COO: Dipl. Ing. (FH) Armin von Collrepp
Commercial Registry:
	Amtsgericht Chemnitz, HRB 28082; USt.-Id Nr. DE150534010