From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: "Tomasz Moń" <tomasz.mon@camlingroup.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Sergey Organov" <sorganov@gmail.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
linux-serial@vger.kernel.org,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"Shawn Guo" <shawnguo@kernel.org>,
"Stefan Wahren" <stefan.wahren@chargebyte.com>
Subject: Re: Regression: serial: imx: overrun errors on debug UART
Date: Fri, 24 Mar 2023 13:47:59 +0200 (EET) [thread overview]
Message-ID: <d660e3cf-5686-d989-3b59-efe83ec9d590@linux.intel.com> (raw)
In-Reply-To: <2c29454b-9369-4360-8eb4-c151f59460cb@i2se.com>
On Fri, 24 Mar 2023, Stefan Wahren wrote:
> Hi,
>
> after switching to Linux 6.1.21 on our Tarragon board (i.MX6ULL SoC), we
> experience the following issues with the debug UART (115200 baud, 8N1, no
> hardware flow control):
>
> - overrun errors if we paste in multiple text lines while system is idle
> - no reaction to single key strokes while system is on higher load
>
> After reverting 7a637784d517 ("serial: imx: reduce RX interrupt frequency")
> the issue disappear.
>
> Maybe it's worth to mention that the Tarragon board uses two additional
> application UARTs with similiar baud rates (9600 - 115200 baud, no hardware
> flow control) for RS485 communication, but there are no overrun errors (with
> and without the mention change).
This has come up earlier, see e.g.:
https://lore.kernel.org/linux-serial/20221003110850.GA28338@francesco-nb.int.toradex.com/
My somewhat uninformed suggestion: if the overrun problems mostly show up
with console ports, maybe the trigger level could depend on the port
being a console or not?
--
i.
WARNING: multiple messages have this Message-ID (diff)
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: "Tomasz Moń" <tomasz.mon@camlingroup.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Sergey Organov" <sorganov@gmail.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
linux-serial@vger.kernel.org,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"Shawn Guo" <shawnguo@kernel.org>,
"Stefan Wahren" <stefan.wahren@chargebyte.com>
Subject: Re: Regression: serial: imx: overrun errors on debug UART
Date: Fri, 24 Mar 2023 13:47:59 +0200 (EET) [thread overview]
Message-ID: <d660e3cf-5686-d989-3b59-efe83ec9d590@linux.intel.com> (raw)
In-Reply-To: <2c29454b-9369-4360-8eb4-c151f59460cb@i2se.com>
On Fri, 24 Mar 2023, Stefan Wahren wrote:
> Hi,
>
> after switching to Linux 6.1.21 on our Tarragon board (i.MX6ULL SoC), we
> experience the following issues with the debug UART (115200 baud, 8N1, no
> hardware flow control):
>
> - overrun errors if we paste in multiple text lines while system is idle
> - no reaction to single key strokes while system is on higher load
>
> After reverting 7a637784d517 ("serial: imx: reduce RX interrupt frequency")
> the issue disappear.
>
> Maybe it's worth to mention that the Tarragon board uses two additional
> application UARTs with similiar baud rates (9600 - 115200 baud, no hardware
> flow control) for RS485 communication, but there are no overrun errors (with
> and without the mention change).
This has come up earlier, see e.g.:
https://lore.kernel.org/linux-serial/20221003110850.GA28338@francesco-nb.int.toradex.com/
My somewhat uninformed suggestion: if the overrun problems mostly show up
with console ports, maybe the trigger level could depend on the port
being a console or not?
--
i.
_______________________________________________
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:[~2023-03-24 11:48 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 8:57 Regression: serial: imx: overrun errors on debug UART Stefan Wahren
2023-03-24 8:57 ` Stefan Wahren
2023-03-24 10:12 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-03-24 10:12 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-03-24 11:47 ` Ilpo Järvinen [this message]
2023-03-24 11:47 ` Ilpo Järvinen
2023-03-24 12:26 ` Francesco Dolcini
2023-03-24 12:26 ` Francesco Dolcini
2023-03-24 12:35 ` Ilpo Järvinen
2023-03-24 12:35 ` Ilpo Järvinen
2023-03-24 12:49 ` Stefan Wahren
2023-03-24 12:49 ` Stefan Wahren
2023-03-24 13:06 ` Francesco Dolcini
2023-03-24 13:06 ` Francesco Dolcini
2023-03-24 12:57 ` Fabio Estevam
2023-03-24 12:57 ` Fabio Estevam
2023-03-24 13:37 ` Uwe Kleine-König
2023-03-24 13:37 ` Uwe Kleine-König
2023-03-24 14:19 ` Stefan Wahren
2023-03-24 14:19 ` Stefan Wahren
2023-03-24 14:39 ` Uwe Kleine-König
2023-03-24 14:39 ` Uwe Kleine-König
2023-03-24 21:57 ` Sergey Organov
2023-03-24 21:57 ` Sergey Organov
2023-03-24 15:00 ` Stefan Wahren
2023-03-24 15:00 ` Stefan Wahren
2023-03-25 11:31 ` Stefan Wahren
2023-03-25 11:31 ` Stefan Wahren
2023-03-25 12:23 ` Fabio Estevam
2023-03-25 12:23 ` Fabio Estevam
2023-03-25 15:11 ` Uwe Kleine-König
2023-03-25 15:11 ` Uwe Kleine-König
2023-03-25 17:05 ` Stefan Wahren
2023-03-25 17:05 ` Stefan Wahren
2023-03-25 19:00 ` Sergey Organov
2023-03-25 19:00 ` Sergey Organov
2023-03-26 18:21 ` Francesco Dolcini
2023-03-26 18:21 ` Francesco Dolcini
2023-03-27 8:07 ` Tomasz Moń
2023-03-27 8:07 ` Tomasz Moń
2023-03-25 18:30 ` Sergey Organov
2023-03-25 18:30 ` Sergey Organov
2023-03-27 14:42 ` Stefan Wahren
2023-03-27 14:42 ` Stefan Wahren
2023-03-27 15:11 ` Sergey Organov
2023-03-27 15:11 ` Sergey Organov
2023-03-27 15:30 ` Russell King (Oracle)
2023-03-27 15:30 ` Russell King (Oracle)
2023-04-16 13:43 ` Stefan Wahren
2023-04-16 13:43 ` Stefan Wahren
2023-04-17 16:50 ` Sergey Organov
2023-04-17 16:50 ` Sergey Organov
2023-04-17 18:40 ` Stefan Wahren
2023-04-17 18:40 ` Stefan Wahren
2023-04-18 16:16 ` Stefan Wahren
2023-04-18 16:16 ` Stefan Wahren
2023-05-22 9:25 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 9:25 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-23 15:12 ` Stefan Wahren
2023-05-23 15:12 ` Stefan Wahren
2023-05-23 19:44 ` Sergey Organov
2023-05-23 19:44 ` Sergey Organov
2023-05-24 10:48 ` Thorsten Leemhuis
2023-05-24 10:48 ` Thorsten Leemhuis
2023-05-24 12:41 ` Uwe Kleine-König
2023-05-24 12:41 ` Uwe Kleine-König
2023-05-24 13:45 ` Sergey Organov
2023-05-24 13:45 ` Sergey Organov
2023-05-24 13:07 ` Stefan Wahren
2023-05-24 13:07 ` Stefan Wahren
2023-06-20 14:47 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-20 14:47 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-20 14:59 ` Greg Kroah-Hartman
2023-06-20 14:59 ` Greg Kroah-Hartman
2023-06-20 15:34 ` Sergey Organov
2023-06-20 15:34 ` Sergey Organov
2023-06-20 16:30 ` Stefan Wahren
2023-06-20 16:30 ` Stefan Wahren
2023-06-20 16:40 ` Lucas Stach
2023-06-20 16:40 ` Lucas Stach
2023-06-20 16:55 ` Stefan Wahren
2023-06-20 16:55 ` Stefan Wahren
2023-06-20 19:27 ` Uwe Kleine-König
2023-06-20 19:27 ` Uwe Kleine-König
2023-06-21 8:43 ` Greg Kroah-Hartman
2023-06-21 8:43 ` Greg Kroah-Hartman
2023-06-21 6:23 ` Stefan Wahren
2023-06-21 6:23 ` Stefan Wahren
2023-06-21 13:42 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-21 13:42 ` Linux regression tracking (Thorsten Leemhuis)
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=d660e3cf-5686-d989-3b59-efe83ec9d590@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-serial@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=sorganov@gmail.com \
--cc=stefan.wahren@chargebyte.com \
--cc=stefan.wahren@i2se.com \
--cc=tomasz.mon@camlingroup.com \
--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 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.