From: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-rt-users@vger.kernel.org
Subject: Re: linux-rt stall on imx6dl on patch-5.4.22-rt13.patch
Date: Fri, 29 May 2020 15:46:46 +0200 [thread overview]
Message-ID: <CAOf5uwmQnX8SNOxD71mwcxc5Q4hKXo1VqnMbaSArNg0SmE5dqA@mail.gmail.com> (raw)
In-Reply-To: <20200529133107.y65eta5btvgpk6pu@linutronix.de>
Hi
On Fri, May 29, 2020 at 3:31 PM Sebastian Andrzej Siewior
<bigeasy@linutronix.de> wrote:
>
> On 2020-05-29 10:08:01 [+0200], Michael Nazzareno Trimarchi wrote:
> > Hi all
> Hi,
>
> > I get this stack trace
> > echo 3 > /proc/sys/vm/drop_caches chrt -f 99 sysbench --test=cpu --num-threads=2
> >
> > First of all, I need to know that if it is a valid use case because
> > was raised by the testing team and
> > how can I start and where to take a look at it
>
> Assuming that there is a `;' in front of `chrt' then I wouldn't be
> surprised. You are basically keeping two CPUs busy with sysbench at RT
> priority and then wondering why the system isn't making any progress. If
> it wouldn't be for the RT throttler, you might not even see any output
> and box hardware would appear be dead.
No, I'm not surprised but my answer to them was not enough. Right now
they are executing some bench.
Best
Michael
>
> > Best Regards
> > Michael
> >
> > [ 161.709260] 001: sh (480): drop_caches: 3
> > [ 180.234358] 001: sched: RT throttling activated
> > [ 180.283363] 001: fec 2188000.ethernet eth0: MDIO read timeout
> > [ 180.283406] 001: ------------[ cut here ]------------
> > [ 180.283416] 001: WARNING: CPU: 1 PID: 133 at
> > drivers/net/phy/phy.c:716 phy_er
> >
> > ror+0x24/0x64
> > [ 180.283460] 001: Modules linked in:
> > [ 180.283473] 001: CPU: 1 PID: 133 Comm: kworker/1:2 Tainted: G
> > W
>
> This is hard to read. Especially later in that mail. In future please
> try to not cut the lines.
>
> Sebastian
--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as] http://www.amarulasolutions.com |
next prev parent reply other threads:[~2020-05-29 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 8:08 linux-rt stall on imx6dl on patch-5.4.22-rt13.patch Michael Nazzareno Trimarchi
2020-05-29 13:31 ` Sebastian Andrzej Siewior
2020-05-29 13:46 ` Michael Nazzareno Trimarchi [this message]
2020-05-29 14:48 ` Sebastian Andrzej Siewior
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=CAOf5uwmQnX8SNOxD71mwcxc5Q4hKXo1VqnMbaSArNg0SmE5dqA@mail.gmail.com \
--to=michael@amarulasolutions.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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).