From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Tim Sander <tim@krieglstein.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: problems with 4.14.6-rt7
Date: Tue, 20 Feb 2018 19:48:06 +0100 [thread overview]
Message-ID: <20180220184806.ytte4af5uhfpytlm@linutronix.de> (raw)
In-Reply-To: <2627538.QZmOYvPzcF@dabox>
On 2018-01-26 17:01:09 [+0100], Tim Sander wrote:
> Hi Sebastian
Hi Tim,
> I just double checked with your 4.14.15-rt12 release. I have not seen
> any throtteling messages? (the double "cut here" line is no copy error of mine, but
> verbatim kernel output)
>
> Here is the dmesg output of a testrun:
>
> BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 56s!
> Showing busy workqueues and worker pools:
> workqueue mm_percpu_wq: flags=0x8
> pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256
> pending: vmstat_update
I don't see all of this but I don't see the lockdep detector unless I
boot UP. This bothers me little, let me look why…
Sebastian
next prev parent reply other threads:[~2018-02-20 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 14:56 problems with 4.14.6-rt7 Tim Sander
2018-01-24 14:18 ` Sebastian Andrzej Siewior
2018-01-26 16:01 ` Tim Sander
2018-02-20 18:48 ` Sebastian Andrzej Siewior [this message]
2018-02-20 19:36 ` 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=20180220184806.ytte4af5uhfpytlm@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=tim@krieglstein.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).