From: Udo Steinberg <udo@hypervisor.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Linux 5.10.5 hung task
Date: Thu, 7 Jan 2021 22:35:41 +0100 [thread overview]
Message-ID: <20210107223541.2d03619c@X220.hypervisor.org> (raw)
Hi all,
(Please CC: me as I'm not subscribed to LKML)
I'm getting frequent hangs under X11 with Linux 5.10.5 on a Lenovo X1 Carbon
6th Gen laptop with Intel KBL graphics.
Below is a trace of what hangs.
Any pointers for how to debug this further or any patches are appreciated.
Thanks,
Udo
[ 2602.016651] INFO: task kworker/3:1H:373 blocked for more than 20 seconds.
[ 2602.016653] Not tainted 5.10.5 #1
[ 2602.016653] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2602.016654] task:kworker/3:1H state:D stack: 0 pid: 373 ppid: 2 flags:0x00004000
[ 2602.016659] Workqueue: events_highpri intel_atomic_cleanup_work
[ 2602.016660] Call Trace:
[ 2602.016663] __schedule+0x1d7/0x520
[ 2602.016665] schedule+0x40/0xe0
[ 2602.016666] schedule_preempt_disabled+0xf/0x20
[ 2602.016667] __ww_mutex_lock.constprop.0+0x4a3/0x830
[ 2602.016668] ? acpi_idle_do_entry+0x50/0x50
[ 2602.016669] intel_unpin_fb_vma+0x20/0xa0
[ 2602.016672] drm_atomic_helper_cleanup_planes+0x4a/0x60
[ 2602.016673] intel_atomic_cleanup_work+0x54/0x100
[ 2602.016675] process_one_work+0x1a8/0x2f0
[ 2602.016676] ? rescuer_thread+0x410/0x410
[ 2602.016677] worker_thread+0x48/0x3d0
[ 2602.016678] ? rescuer_thread+0x410/0x410
[ 2602.016679] kthread+0x136/0x160
[ 2602.016681] ? __kthread_bind_mask+0x60/0x60
[ 2602.016682] ret_from_fork+0x1f/0x30
[ 2622.496742] INFO: task kworker/3:1H:373 blocked for more than 40 seconds.
[ 2622.496744] Not tainted 5.10.5 #1
[ 2622.496744] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2622.496745] task:kworker/3:1H state:D stack: 0 pid: 373 ppid: 2 flags:0x00004000
[ 2622.496750] Workqueue: events_highpri intel_atomic_cleanup_work
[ 2622.496751] Call Trace:
[ 2622.496754] __schedule+0x1d7/0x520
[ 2622.496756] schedule+0x40/0xe0
[ 2622.496757] schedule_preempt_disabled+0xf/0x20
[ 2622.496758] __ww_mutex_lock.constprop.0+0x4a3/0x830
[ 2622.496759] ? acpi_idle_do_entry+0x50/0x50
[ 2622.496760] intel_unpin_fb_vma+0x20/0xa0
[ 2622.496763] drm_atomic_helper_cleanup_planes+0x4a/0x60
[ 2622.496764] intel_atomic_cleanup_work+0x54/0x100
[ 2622.496766] process_one_work+0x1a8/0x2f0
[ 2622.496767] ? rescuer_thread+0x410/0x410
[ 2622.496768] worker_thread+0x48/0x3d0
[ 2622.496769] ? rescuer_thread+0x410/0x410
[ 2622.496771] kthread+0x136/0x160
[ 2622.496772] ? __kthread_bind_mask+0x60/0x60
[ 2622.496773] ret_from_fork+0x1f/0x30
reply other threads:[~2021-01-07 21:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210107223541.2d03619c@X220.hypervisor.org \
--to=udo@hypervisor.org \
--cc=linux-kernel@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 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.