From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Andre Renaud <arenaud@designa-electronics.com>
Cc: Fabio Estevam <festevam@gmail.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
Andy Duan <fugang.duan@nxp.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [EXT] Re: iMX6/UART imprecise external abort
Date: Wed, 8 Jan 2020 07:43:39 +0100 [thread overview]
Message-ID: <20200108064339.pobiwqq6feu53jpm@pengutronix.de> (raw)
In-Reply-To: <CAEj2-1Nh=-Qc4Q1diDSbe=9yOO-UBYR2BQm7hF9vo-qgCOst=Q@mail.gmail.com>
Hello,
On Wed, Jan 08, 2020 at 05:03:18PM +1300, Andre Renaud wrote:
> On Wed, Jan 8, 2020 at 2:43 PM Andy Duan <fugang.duan@nxp.com> wrote:
> > @Andre Renaud, can you add kernel command line "nosmp" to check the issue ?
> > Suppose one core cannot reproduce the issue.
>
> We have done this test previously, and 'nosmp' does resolve the issue.
Not surprising as the problem goes away by (only) ensuring that irq
handler and uart user run on the same cpu. Limiting the whole system to
a single CPU is just another way to ensure this same cpu handling.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
_______________________________________________
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:[~2020-01-08 6:43 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
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 [this message]
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=20200108064339.pobiwqq6feu53jpm@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=arenaud@designa-electronics.com \
--cc=festevam@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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).