From: Francesco Dolcini <francesco@dolcini.it>
To: Sergey Organov <sorganov@gmail.com>
Cc: "Stefan Wahren" <stefan.wahren@i2se.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Stefan Wahren" <stefan.wahren@chargebyte.com>,
linux-serial@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Tomasz Moń" <tomasz.mon@camlingroup.com>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>
Subject: Re: Regression: serial: imx: overrun errors on debug UART
Date: Sun, 26 Mar 2023 20:21:24 +0200 [thread overview]
Message-ID: <ZCCNJNWYCbbIsnWR@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <878rfk64hj.fsf@osv.gnss.ru>
On Sat, Mar 25, 2023 at 10:00:24PM +0300, Sergey Organov wrote:
> In correctly working RT system this doesn't typically happen, as CPUs
> are way faster than typical UART speeds, and are able to handle the
> loads easily, provided UART has decent FIFO. It's disabling IRQs for
> prolonged times that makes shit happen.
The first time we were looking into this issue was before 7a637784d517
and with a PREEMPT-RT patched kernel (if I remember correctly it was a
v5.4).
The system was not loaded at all and it was pretty surprising the
behavior, because of the reasons you just wrote here.
Francesco
WARNING: multiple messages have this Message-ID (diff)
From: Francesco Dolcini <francesco@dolcini.it>
To: Sergey Organov <sorganov@gmail.com>
Cc: "Stefan Wahren" <stefan.wahren@i2se.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Stefan Wahren" <stefan.wahren@chargebyte.com>,
linux-serial@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Tomasz Moń" <tomasz.mon@camlingroup.com>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>
Subject: Re: Regression: serial: imx: overrun errors on debug UART
Date: Sun, 26 Mar 2023 20:21:24 +0200 [thread overview]
Message-ID: <ZCCNJNWYCbbIsnWR@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <878rfk64hj.fsf@osv.gnss.ru>
On Sat, Mar 25, 2023 at 10:00:24PM +0300, Sergey Organov wrote:
> In correctly working RT system this doesn't typically happen, as CPUs
> are way faster than typical UART speeds, and are able to handle the
> loads easily, provided UART has decent FIFO. It's disabling IRQs for
> prolonged times that makes shit happen.
The first time we were looking into this issue was before 7a637784d517
and with a PREEMPT-RT patched kernel (if I remember correctly it was a
v5.4).
The system was not loaded at all and it was pretty surprising the
behavior, because of the reasons you just wrote here.
Francesco
_______________________________________________
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-26 18:21 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
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 [this message]
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=ZCCNJNWYCbbIsnWR@francesco-nb.int.toradex.com \
--to=francesco@dolcini.it \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--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.