From: "Gardner, Brent G. (GRC-LEM0)" <brent.g.gardner@nasa.gov>
To: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Need help in interpreting ip status output
Date: Mon, 31 Aug 2020 20:59:49 +0000 [thread overview]
Message-ID: <SA9PR09MB5280A7B98637AE7B7A0014B4D6510@SA9PR09MB5280.namprd09.prod.outlook.com> (raw)
I apologize for not knowing how to join the thread in the subject, but I'm trying to investigate similar issues. I'm using a Raspberry Pi CM3+ with a MCP2515 dtoverlay. During moments of high CAN traffic (and possibly more prevalent during high CPU usage), many RX overruns occur. The physical CAN bus signals appears sound, as I can verify the dropped frames are present and valid with an oscilloscope, so I believe the issue is related to the SocketCAN driver. Did upgrading the kernel help? To what version? Thanks for your help.
$uname -a
4.19.118-v7+ #1311 SMP Mon Apr 27 14:21:24 BST 2020 armv7l GNU/Linux
$ ip -s link show can0
2: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 200
link/can
RX: bytes packets errors dropped overrun mcast
14992 14992 71 15 71 0
TX: bytes packets errors dropped carrier collsns
1364 3028 0 0 0 0
next reply other threads:[~2020-08-31 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 20:59 Gardner, Brent G. (GRC-LEM0) [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2020-03-23 7:19 ` André Hartmann
2020-03-23 7:44 ` Marc Kleine-Budde
2020-03-23 11:16 ` André Hartmann
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=SA9PR09MB5280A7B98637AE7B7A0014B4D6510@SA9PR09MB5280.namprd09.prod.outlook.com \
--to=brent.g.gardner@nasa.gov \
--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).