From: Andre Renaud <arenaud@designa-electronics.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Fugang Duan <fugang.duan@nxp.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: iMX6/UART imprecise external abort
Date: Tue, 3 Dec 2019 19:24:48 +1300 [thread overview]
Message-ID: <CAEj2-1Ps3XMjxtnN56jdCRvNtE_84T70asBrCGZJE05wUPEbyQ@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5AxvuWETvubZU1Tu=0-SeoSzJs=LZcj-JJFE1+4O6-FxA@mail.gmail.com>
Hi Fabio,
> Could you please try a vanilla 5.4.1 kernel?
Yes, it continues to occur on 5.4.1 vanilla kernel.
We have managed to speed up the replication of the fault with the
following fairly simple UART stress test:
https://gist.github.com/AndreRenaud/712abbef1340d907fca6bdadafb4ac92
Our kernel .config is here:
https://gist.github.com/AndreRenaud/39b1eee0ca9a6d2db2ee86f5d3cc6d4d
The unit is essentially idle - just a minimal buildroot filesystem.
Bootlog is available here:
https://gist.github.com/AndreRenaud/a4aef8a57cfe33b90f43a17bb0d2395b
We are starting to look at some of the other suggestions - disabling
the clocking in drivers/tty/serial/imx.c for instance.
Regards,
Andre
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-03 6:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 20:40 iMX6/UART imprecise external abort Andre Renaud
2019-12-02 20:56 ` Fabio Estevam
2019-12-03 1:53 ` [EXT] " Andy Duan
2019-12-03 2:01 ` Andre Renaud
2019-12-03 2:06 ` Andy Duan
2019-12-03 2:28 ` Fabio Estevam
2019-12-03 6:24 ` Andre Renaud [this message]
2019-12-10 4:03 ` Andre Renaud
2019-12-10 5:46 ` [EXT] " Andy Duan
2019-12-10 22:07 ` Andre Renaud
2019-12-11 0:27 ` Fabio Estevam
2019-12-11 1:35 ` [EXT] " Andre Renaud
2019-12-11 1:59 ` Andre Renaud
2019-12-12 1:35 ` Fabio Estevam
2019-12-15 23:41 ` Andre Renaud
2019-12-02 21:29 ` Uwe Kleine-König
2019-12-05 19:29 ` Andre Renaud
2019-12-21 3:33 ` Andre Renaud
2019-12-21 7:31 ` [EXT] " Andy Duan
2019-12-21 12:03 ` Fabio Estevam
2019-12-23 1:53 ` Andy Duan
2019-12-23 10:16 ` Uwe Kleine-König
2020-01-07 22:24 ` Uwe Kleine-König
2020-01-08 1:43 ` Andy Duan
2020-01-08 4:03 ` Andre Renaud
2020-01-08 5:11 ` Andy Duan
2020-01-08 6:43 ` Uwe Kleine-König
2020-01-08 6:40 ` Uwe Kleine-König
2020-01-08 11:23 ` Uwe Kleine-König
2020-01-09 1:33 ` Andy Duan
2020-01-19 23:29 ` Andre Renaud
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=CAEj2-1Ps3XMjxtnN56jdCRvNtE_84T70asBrCGZJE05wUPEbyQ@mail.gmail.com \
--to=arenaud@designa-electronics.com \
--cc=festevam@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=linux-arm-kernel@lists.infradead.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).