linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andre Renaud <arenaud@designa-electronics.com>
To: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>
Cc: "Andy Duan" <fugang.duan@nxp.com>,
	s.hauer@pengutronix.de, "Fabio Estevam" <festevam@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: iMX6/UART imprecise external abort
Date: Sat, 21 Dec 2019 16:33:46 +1300	[thread overview]
Message-ID: <FD3C2267-A9B8-45BB-B027-C85DB5E60829@designa-electronics.com> (raw)
In-Reply-To: <CAEj2-1PyhkhEJ1+uRWio4vYxGuFOuR9mpZOdxmDDjGt_Az+3uA@mail.gmail.com>

> On 3/12/2019, at 9:40 AM, Andre Renaud <arenaud@designa-electronics.com> wrote:
> I am working with an iMX6Q system that is exhibiting a crash when
> using the serial ports.
> We have /dev/ttymxc2 configured as an RS485 UART, and are seeing an
> 'imprecise external abort' after some time of use (panic listed
> below).

Following up on this. After various attempts to replicate it on different boards, we found that after enabling the SER_RS485_RX_DURING_TX flag, the issue went away. This in turn led us to discover that the issue we were seeing is the same one discussed in this prior discussion: https://www.spinics.net/lists/arm-kernel/msg564268.html

We took the patch there, modified it to suite our kernel, and have confirmed that this resolves the issue.

Can anyone comment on whether that patch, or some variant on it, should be forward ported to the latest kernel? It has a slightly odd timeout in there, with no error return value, but apart from that it does resolve out issue.

Regards,
Andre
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-12-21  3:34 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 [this message]
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=FD3C2267-A9B8-45BB-B027-C85DB5E60829@designa-electronics.com \
    --to=arenaud@designa-electronics.com \
    --cc=festevam@gmail.com \
    --cc=fugang.duan@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    --cc=u.kleine-koenig@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).