From: Heiner Kallweit <hkallweit1@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: WQ_UNBOUND warning since recent workqueue refactoring
Date: Wed, 30 Aug 2023 16:57:42 +0200 [thread overview]
Message-ID: <f7e21caa-e98d-e5b5-932a-fe12d27fde9b@gmail.com> (raw)
Recently I started to see the following warning on linux-next and presumably
this may be related to the refactoring of the workqueue core code.
[ 56.900223] workqueue: output_poll_execute [drm_kms_helper] hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
[ 56.923226] workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
[ 97.860430] workqueue: output_poll_execute [drm_kms_helper] hogged CPU for >10000us 8 times, consider switching to WQ_UNBOUND
[ 97.884453] workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >10000us 8 times, consider switching to WQ_UNBOUND
Adding WQ_UNBOUND to these queues didn't change the behavior.
Maybe relevant: I run the affected system headless.
next reply other threads:[~2023-08-30 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 14:57 Heiner Kallweit [this message]
2023-08-30 17:51 ` [Intel-gfx] WQ_UNBOUND warning since recent workqueue refactoring Tejun Heo
2023-08-30 17:51 ` Tejun Heo
2023-08-30 18:56 ` [Intel-gfx] " Imre Deak
2023-08-30 19:47 ` Heiner Kallweit
2023-08-30 19:54 ` Heiner Kallweit
2023-09-01 2:25 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-09-01 2:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-01 8:05 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=f7e21caa-e98d-e5b5-932a-fe12d27fde9b@gmail.com \
--to=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 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.