From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203033] nouveau hung task
Date: Fri, 28 Aug 2020 15:23:25 +0000 [thread overview]
Message-ID: <bug-203033-2300-3DmOQ755HX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203033-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203033
James O'Beirne (james.obeirne@pm.me) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |james.obeirne@pm.me
--- Comment #5 from James O'Beirne (james.obeirne@pm.me) ---
Having the same issue.
# lspci | grep VGA
1f:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 710B]
(rev a1)
# uname -a
Linux slug 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64
GNU/Linux
Aug 28 02:34:11 slug kernel: [38304.923718] INFO: task kworker/u32:0:5123
blocked for more than 120 seconds.
Aug 28 02:34:11 slug kernel: [38304.923725] Tainted: G E
4.19.0-10-amd64 #1 Debian 4.19.132-1
Aug 28 02:34:11 slug kernel: [38304.923727] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 28 02:34:11 slug kernel: [38304.923729] kworker/u32:0 D 0 5123 2
0x80000000
Aug 28 02:34:11 slug kernel: [38304.923798] Workqueue: events_unbound
nv50_disp_atomic_commit_work [nouveau]
Aug 28 02:34:11 slug kernel: [38304.923799] Call Trace:
Aug 28 02:34:11 slug kernel: [38304.923808] __schedule+0x2a2/0x870
Aug 28 02:34:11 slug kernel: [38304.923812] schedule+0x28/0x80
Aug 28 02:34:11 slug kernel: [38304.923814] schedule_timeout+0x26d/0x390
Aug 28 02:34:11 slug kernel: [38304.923875] ? nvkm_client_map+0x10/0x10
[nouveau]
Aug 28 02:34:11 slug kernel: [38304.923880] dma_fence_default_wait+0x238/0x2a0
Aug 28 02:34:11 slug kernel: [38304.923882] ? dma_fence_release+0x90/0x90
Aug 28 02:34:11 slug kernel: [38304.923884] dma_fence_wait_timeout+0x42/0xf0
Aug 28 02:34:11 slug kernel: [38304.923897]
drm_atomic_helper_wait_for_fences+0x63/0xc0 [drm_kms_helper]
Aug 28 02:34:11 slug kernel: [38304.923957]
nv50_disp_atomic_commit_tail+0x7c/0x880 [nouveau]
Aug 28 02:34:11 slug kernel: [38304.923963] ? __switch_to+0x15b/0x440
Aug 28 02:34:11 slug kernel: [38304.923966] ? __switch_to_asm+0x35/0x70
Aug 28 02:34:11 slug kernel: [38304.923971] process_one_work+0x1a7/0x3a0
Aug 28 02:34:11 slug kernel: [38304.923975] worker_thread+0x30/0x390
Aug 28 02:34:11 slug kernel: [38304.923978] ? create_worker+0x1a0/0x1a0
Aug 28 02:34:11 slug kernel: [38304.923981] kthread+0x112/0x130
Aug 28 02:34:11 slug kernel: [38304.923983] ? kthread_bind+0x30/0x30
Aug 28 02:34:11 slug kernel: [38304.923985] ret_from_fork+0x22/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-08-28 15:23 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
2020-05-11 15:02 ` bugzilla-daemon
2020-05-11 15:03 ` bugzilla-daemon
2020-08-28 15:23 ` bugzilla-daemon [this message]
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-3DmOQ755HX@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).