From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107867] The game The Evil Within Demo lead to GPU hang when played first cut scene.
Date: Sat, 08 Sep 2018 16:32:55 +0000 [thread overview]
Message-ID: <bug-107867-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3328 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107867
Bug ID: 107867
Summary: The game The Evil Within Demo lead to GPU hang when
played first cut scene.
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: mikhail.v.gavrilov@gmail.com
Created attachment 141490
--> https://bugs.freedesktop.org/attachment.cgi?id=141490&action=edit
dmesg
1. Install steam
2. Enable steam play
3. Launch game under Fedora 30 (Rawhide)
4. Not skip first cut scene
[ 246.521518] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=27174, emitted seq=27176
[ 246.521534] [drm] GPU recovery disabled.
[ 332.537451] kworker/dying (23) used greatest stack depth: 11392 bytes left
[ 369.399369] INFO: task kworker/u32:8:204 blocked for more than 120 seconds.
[ 369.399384] Tainted: G C
4.19.0-0.rc2.git2.1.fc30.x86_64 #1
[ 369.399386] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 369.399389] kworker/u32:8 D10560 204 2 0x80000000
[ 369.399406] Workqueue: events_unbound commit_work [drm_kms_helper]
[ 369.399410] Call Trace:
[ 369.399420] ? __schedule+0x2e2/0xa70
[ 369.399424] ? native_sched_clock+0x3e/0xa0
[ 369.399432] ? dma_fence_default_wait+0x242/0x330
[ 369.399437] schedule+0x2f/0x90
[ 369.399441] schedule_timeout+0x31c/0x4f0
[ 369.399516] ? mark_held_locks+0x57/0x80
[ 369.399520] ? _raw_spin_unlock_irqrestore+0x4b/0x60
[ 369.399527] ? dma_fence_default_wait+0x242/0x330
[ 369.399530] dma_fence_default_wait+0x26e/0x330
[ 369.399535] ? dma_fence_release+0x120/0x120
[ 369.399541] dma_fence_wait_timeout+0x182/0x200
[ 369.399547] reservation_object_wait_timeout_rcu+0x236/0x4e0
[ 369.399619] amdgpu_dm_do_flip+0x112/0x340 [amdgpu]
[ 369.399722] amdgpu_dm_atomic_commit_tail+0x72b/0xd90 [amdgpu]
[ 369.399730] ? wait_for_completion_timeout+0x73/0x1a0
[ 369.399748] commit_tail+0x3d/0x70 [drm_kms_helper]
[ 369.399753] process_one_work+0x27d/0x5c0
[ 369.399764] worker_thread+0x3c/0x390
[ 369.399770] ? process_one_work+0x5c0/0x5c0
[ 369.399774] kthread+0x120/0x140
[ 369.399778] ? kthread_create_worker_on_cpu+0x70/0x70
[ 369.399783] ret_from_fork+0x27/0x50
[ 369.399927]
Showing all locks held in the system:
[ 369.399936] 1 lock held by khungtaskd/94:
[ 369.399937] #0: 000000007b8e38cf (rcu_read_lock){....}, at:
debug_show_all_locks+0x15/0x183
[ 369.399954] 3 locks held by kworker/u32:8/204:
[ 369.399956] #0: 00000000265972fd ((wq_completion)"events_unbound"){+.+.},
at: process_one_work+0x1f3/0x5c0
[ 369.399967] #1: 0000000005b55269
((work_completion)(&state->commit_work)){+.+.}, at:
process_one_work+0x1f3/0x5c0
[ 369.399977] #2: 00000000857176ee (reservation_ww_class_mutex){+.+.}, at:
amdgpu_dm_do_flip+0xd6/0x340 [amdgpu]
[ 369.400157] 1 lock held by EvilWithinDemo./3714:
[ 369.400171] =============================================
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4762 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-09-08 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 16:32 bugzilla-daemon [this message]
2018-09-08 16:34 ` [Bug 107867] The game The Evil Within Demo lead to GPU hang when played first cut scene bugzilla-daemon
2018-09-08 16:35 ` bugzilla-daemon
2019-11-19 8:54 ` 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-107867-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 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.