From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "André Hartmann" <aha_1980@gmx.de>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"Alex Blasche" <alexander.blasche@qt.io>,
"Marc Kleine-Budde" <mkl@pengutronix.de>
Subject: Re: Need help in interpreting ip status output
Date: Sat, 21 Mar 2020 18:04:35 +0100 [thread overview]
Message-ID: <fe141541-7e79-3bee-8c75-29e6f9f3bc4e@hartkopp.net> (raw)
In-Reply-To: <75a1a6b5-141e-e741-f6c2-bab5e9e4e541@gmx.de>
+ Marc
Hi André,
On 21/03/2020 16.19, André Hartmann wrote:
>> On 12/03/2020 18.43, André Hartmann wrote:
>>
>>>> can someone help me interpreting the following ip output:
>> The reason for the overrun error is a notification from the CAN
>> controller itself. It tells us that the received CAN frame has not been
>> read from the controller until the next CAN frame arrived.
>
> Ok, that's what I thought too, thanks for the confirmation.
>
>> The dropped counter usually indicates that the CAN driver did not get a
>> skbuff data structure (e.g. out of memory condition).
>>
>> This is NOT good. What CAN hardware/setup are you using?
>
> Actually it's not my system. The report is from a customer doing a full
> load test on an iMX8: https://bugreports.qt.io/browse/QTBUG-82610
Thanks for the link!
> I guess the customer should try a more recent Kernel than 4.14 first?
The FlexCAN driver (which is used in the IMX8 AFAIK) had a remarkable
number of changes last year:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/drivers/net/can/flexcan.c
So I would definitely suggest an update.
I added Marc to this thread as he was very active on the FlexCAN
improvements.
Best,
Oliver
next prev parent reply other threads:[~2020-03-21 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 20:13 Need help in interpreting ip status output André Hartmann
2020-03-12 17:43 ` André Hartmann
2020-03-21 12:38 ` Oliver Hartkopp
2020-03-21 15:19 ` André Hartmann
2020-03-21 17:04 ` Oliver Hartkopp [this message]
2020-03-23 7:19 ` André Hartmann
2020-03-23 7:44 ` Marc Kleine-Budde
2020-03-23 11:16 ` André Hartmann
2020-08-31 20:59 Gardner, Brent G. (GRC-LEM0)
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=fe141541-7e79-3bee-8c75-29e6f9f3bc4e@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=aha_1980@gmx.de \
--cc=alexander.blasche@qt.io \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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).