From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203033] nouveau hung task
Date: Mon, 11 May 2020 15:01:21 +0000 [thread overview]
Message-ID: <bug-203033-2300-C0x92sr4h7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203033-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203033
--- Comment #2 from Mathieu Malaterre (mathieu.malaterre@gmail.com) ---
Same here:
May 11 16:54:31 vostrodell kernel: [ 605.330992] INFO: task kworker/u8:3:162
blocked for more than 120 seconds.
May 11 16:54:31 vostrodell kernel: [ 605.330997] Not tainted
5.4.0-0.bpo.4-amd64 #1 Debian 5.4.19-1~bpo10+1
May 11 16:54:31 vostrodell kernel: [ 605.330999] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 11 16:54:31 vostrodell kernel: [ 605.331001] kworker/u8:3 D 0 162
2 0x80004000
May 11 16:54:31 vostrodell kernel: [ 605.331083] Workqueue: events_unbound
nv50_disp_atomic_commit_work [nouveau]
May 11 16:54:31 vostrodell kernel: [ 605.331095] Call Trace:
May 11 16:54:31 vostrodell kernel: [ 605.331108] ? __schedule+0x2e6/0x6f0
May 11 16:54:31 vostrodell kernel: [ 605.331111] schedule+0x2f/0xa0
May 11 16:54:31 vostrodell kernel: [ 605.331114] schedule_timeout+0x20d/0x310
May 11 16:54:31 vostrodell kernel: [ 605.331155] ? nvif_notify_get+0x94/0xa0
[nouveau]
May 11 16:54:31 vostrodell kernel: [ 605.331224] ? nv84_fence_sync+0x40/0x40
[nouveau]
May 11 16:54:31 vostrodell kernel: [ 605.331234]
dma_fence_default_wait+0x22f/0x290
May 11 16:54:31 vostrodell kernel: [ 605.331241] ?
dma_fence_release+0x140/0x140
May 11 16:54:31 vostrodell kernel: [ 605.331245]
dma_fence_wait_timeout+0xdd/0x100
May 11 16:54:31 vostrodell kernel: [ 605.331264]
drm_atomic_helper_wait_for_fences+0x3c/0xd0 [drm_kms_helper]
May 11 16:54:31 vostrodell kernel: [ 605.331332]
nv50_disp_atomic_commit_tail+0x72/0x710 [nouveau]
May 11 16:54:31 vostrodell kernel: [ 605.331340] ? __switch_to_asm+0x40/0x70
May 11 16:54:31 vostrodell kernel: [ 605.331357] ? __switch_to_asm+0x34/0x70
May 11 16:54:31 vostrodell kernel: [ 605.331360] ? __switch_to+0x7a/0x3e0
May 11 16:54:31 vostrodell kernel: [ 605.331365] ? __switch_to_asm+0x34/0x70
May 11 16:54:31 vostrodell kernel: [ 605.331370] process_one_work+0x1a7/0x360
May 11 16:54:31 vostrodell kernel: [ 605.331377] worker_thread+0x30/0x390
May 11 16:54:31 vostrodell kernel: [ 605.331383] ? create_worker+0x1a0/0x1a0
May 11 16:54:31 vostrodell kernel: [ 605.331388] kthread+0x112/0x130
May 11 16:54:31 vostrodell kernel: [ 605.331394] ? kthread_park+0x80/0x80
May 11 16:54:31 vostrodell kernel: [ 605.331400] ret_from_fork+0x35/0x40
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-05-11 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 14:45 [Bug 203033] New: nouveau hung task bugzilla-daemon
2019-10-20 20:11 ` [Bug 203033] " bugzilla-daemon
2020-05-11 15:01 ` bugzilla-daemon [this message]
2020-05-11 15:02 ` bugzilla-daemon
2020-05-11 15:03 ` bugzilla-daemon
2020-08-28 15:23 ` bugzilla-daemon
2022-11-08 18:23 ` bugzilla-daemon
2024-10-02 9:27 ` bugzilla-daemon
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=bug-203033-2300-C0x92sr4h7@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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).