From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfgang Grandegger Subject: Re: Bus off Date: Fri, 27 Jun 2014 17:35:39 +0200 Message-ID: <53AD8F4B.7090900@grandegger.com> References: <20140627050512.GA1291@vandijck-laurijssen.be> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from ngcobalt02.manitu.net ([217.11.48.102]:35314 "EHLO ngcobalt02.manitu.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753976AbaF0Pn5 (ORCPT ); Fri, 27 Jun 2014 11:43:57 -0400 In-Reply-To: Sender: linux-can-owner@vger.kernel.org List-ID: To: Jason R1 White , linux-can@vger.kernel.org, linux-can-owner@vger.kernel.org On 06/27/2014 05:22 PM, Jason R1 White wrote: >> >> On Thu, Jun 26, 2014 at 10:13:17AM -0700, Austin Schuh wrote: >>> Does anyone know if the TX queues are cleared on BUS-OFF? >> >> No queues are emptied, you will only loose the curent pending > transmission. >> >>> > > I thought the restart mechanism flushed the transmit queues (ip link set > can0 type can restart). Is this not the case? That is what we are > relying upon. We used to close and open the interface explicitly. "restart" and "restart-ms" should trigger a bus-off recovery: http://lxr.free-electrons.com/source/Documentation/networking/can.txt#L1087 > > For controls its not a good practice to let stale data sit in the output > buffer. The intention of restart(-ms) was to simply trigger a bus-off recovery. The name is not well chosen, though. Wolfgang.