From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "André Hartmann" <aha_1980@gmx.de>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Need help in interpreting ip status output
Date: Sat, 21 Mar 2020 13:38:49 +0100 [thread overview]
Message-ID: <86b34b1b-7bda-e481-2087-1be8e64d2fed@hartkopp.net> (raw)
In-Reply-To: <f029f731-25bc-a3f0-c5a9-380012a16839@gmx.de>
Hi André,
I have an idea ;-)
On 12/03/2020 18.43, André Hartmann wrote:
>> can someone help me interpreting the following ip output:
>>
>> ip -s link show can1
>> 3: can1: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state
>> UNKNOWN mode DEFAULT group default qlen 100
>> link/can
>> RX: bytes packets errors dropped overrun mcast
>> 0 9987413 1 74 1 0
>> TX: bytes packets errors dropped carrier collsns
>> 0 0 0 0 0 0
>>
>> I'm especially interested in the meaning of the
>>
>> * 1 errors
>> * 74 dropped
>> * 1 overrun
E.g. if you look into
linux/drivers/net/can/sja1000/sja1000.c
you can see that an overrun error also triggers the error counter to
increase - that's why both are set to 1.
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.
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?
Regards,
Oliver
next prev parent reply other threads:[~2020-03-21 12:38 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 [this message]
2020-03-21 15:19 ` André Hartmann
2020-03-21 17:04 ` Oliver Hartkopp
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=86b34b1b-7bda-e481-2087-1be8e64d2fed@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=aha_1980@gmx.de \
--cc=linux-can@vger.kernel.org \
/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).