From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
"wg@grandegger.com" <wg@grandegger.com>,
Pankaj Bansal <pankaj.bansal@nxp.com>,
"Pankaj Bansal (OSS)" <pankaj.bansal@oss.nxp.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Joakim Zhang <qiangqing.zhang@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: canfdtest on flexcan loopback
Date: Thu, 17 Sep 2020 12:59:14 +0000 [thread overview]
Message-ID: <20200917125913.leisscxw2rrbuzyw@skbuf> (raw)
In-Reply-To: <20200916121437.lfk5vd22qfe3pyjg@skbuf>
On Wed, Sep 16, 2020 at 03:14:37PM +0300, Vladimir Oltean wrote:
> Nonetheless, you bring up a good point. I'll try to bring into net-next
> the minimum amount of required delta (which seems to be the
> fsl_lx2160a_r1_devtype_data structure only), and I'll re-test.
So I'm back with some interesting results.
Test 1:
NXP LSDK 20.04 based on v5.4.3 - reordering reproduces instantly
Test 2:
net-next 5.9-rc3 with upstream defconfig and all downstream patches
imported from LSDK - hasn't reproduced in 20 hours of testing
Test 3:
net-next 5.9-rc3 with .config imported from LSDK - hasn't reproduced in
335 iterations
Test 4:
linux stable linux-5.4.y - hasn't reproduced in 137 iterations
Test 5:
torvalds v5.4.3 - reproduces instantly
Thanks,
-Vladimir
next prev parent reply other threads:[~2020-09-17 12:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <VI1PR04MB4093944944C574B138371F51F12F0@VI1PR04MB4093.eurprd04.prod.outlook.com>
2020-09-16 11:01 ` canfdtest on flexcan loopback Vladimir Oltean
2020-09-16 11:04 ` Vladimir Oltean
2020-09-16 11:32 ` Marc Kleine-Budde
2020-09-16 11:45 ` Vladimir Oltean
2020-09-16 12:01 ` Marc Kleine-Budde
2020-09-16 12:14 ` Vladimir Oltean
2020-09-17 12:59 ` Vladimir Oltean [this message]
2020-09-17 13:10 ` Marc Kleine-Budde
2020-09-18 12:27 ` Vladimir Oltean
2020-09-18 12:35 ` Marc Kleine-Budde
2020-09-17 2:28 ` Joakim Zhang
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=20200917125913.leisscxw2rrbuzyw@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pankaj.bansal@nxp.com \
--cc=pankaj.bansal@oss.nxp.com \
--cc=qiangqing.zhang@nxp.com \
--cc=wg@grandegger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox