From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: linux-can@vger.kernel.org
Subject: Re: m_can error/overrun frames on high speed
Date: Wed, 31 Mar 2021 10:37:44 +0200 [thread overview]
Message-ID: <20210331083744.pui7rtjexvejjvf6@pengutronix.de> (raw)
In-Reply-To: <CAAfyv37vMxhN2B1uR5xUzZwVzAqrQOyPA6stWYj_5346xO0s3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]
On 28.03.2021 08:31:14, Belisko Marek wrote:
> I have a beaglebone based board and I'm performing some tests.
As far as I know the beagle bone boards all have d_can controllers, not
m_can.
> I discovered that when set bitrate to 500k during replaying can file
> from PC to board ip detect 4-5 error/overrun frames. When comparing
> the original file with received one few lines in candump are missing.
> When decreased can speed to 125KB replaying the same file no
> error/overruns are detected and files are the same. I'm not can expert
> thus I'm asking for some advice on how to debug such phenomena. I'm
> using mainline 4.12 kernel which shows this symptom. I compared
> changes with the latest mainline kernel and there are few patches only
> which seems can influence can behavior (others are only cosmetical). I
> took :
>
> 3cb3eaac52c0f145d895f4b6c22834d5f02b8569 - can: c_can: c_can_poll():
> only read status register after status IRQ
> 23c5a9488f076bab336177cd1d1a366bd8ddf087 - can: c_can: D_CAN:
> c_can_chip_config(): perform a sofware reset on open
> 6f12001ad5e79d0a0b08c599731d45c34cafd376 - can: c_can: C_CAN: add bus
> recovery events
>
> I know most of the answers for such issues is to try latest kernel
> (i'm in process trying 5.10).
That's going into the right direction. Please try the lastest
net-next/master, which includes this merge:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=9c0ee085c49c11381dcbd609ea85e902eab88a92
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-03-31 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 6:31 m_can error/overrun frames on high speed Belisko Marek
2021-03-31 8:37 ` Marc Kleine-Budde [this message]
2021-04-01 9:04 ` Belisko Marek
2021-04-01 9:23 ` Marc Kleine-Budde
2021-04-01 9:36 ` Belisko Marek
2021-04-02 19:27 ` Marc Kleine-Budde
2021-04-05 17:31 ` Belisko Marek
2021-04-05 19:41 ` Belisko Marek
2021-04-28 8:18 ` Belisko Marek
2021-04-28 8:20 ` Marc Kleine-Budde
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=20210331083744.pui7rtjexvejjvf6@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=marek.belisko@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.