From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111803] Annoying GPU stucks are continued on Vega 20 with Kernel 5.4 + mesa 9.3.0 + llvm 9.0.0 [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
Date: Tue, 24 Sep 2019 17:54:40 +0000 [thread overview]
Message-ID: <bug-111803-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4977 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111803
Bug ID: 111803
Summary: Annoying GPU stucks are continued on Vega 20 with
Kernel 5.4 + mesa 9.3.0 + llvm 9.0.0
[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR*
Waiting for fences timed out!
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: not set
Priority: not set
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: mikhail.v.gavrilov@gmail.com
Created attachment 145490
--> https://bugs.freedesktop.org/attachment.cgi?id=145490&action=edit
dmesg
Annoying GPU stucks are continued on Vega 20 with Kernel 5.4 + mesa 9.3.0 +
llvm 9.0.0
For reproducing is enough on the machine when happened memory pressing launch
the game Supraland from steam store.
[48662.086736] INFO: task OnlineA-nstance:153979 blocked for more than 122
seconds.
[48662.086740] Not tainted 5.4.0-0.rc0.git4.1a.fc32.x86_64 #1
[48662.086743] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[48662.086746] OnlineA-nstance D12600 153979 153907 0x80004002
[48662.086753] Call Trace:
[48662.086760] ? __schedule+0x307/0x950
[48662.086770] schedule+0x40/0xc0
[48662.086775] schedule_timeout+0x289/0x3c0
[48662.086782] ? mark_held_locks+0x50/0x80
[48662.086787] ? _raw_spin_unlock_irqrestore+0x4b/0x60
[48662.086792] ? lockdep_hardirqs_on+0xf0/0x180
[48662.086803] dma_fence_wait_any_timeout+0x208/0x275
[48662.086881] amdgpu_sa_bo_new+0x44b/0x510 [amdgpu]
[48662.086982] amdgpu_ib_get+0x31/0x80 [amdgpu]
[48662.087075] amdgpu_job_alloc_with_ib+0x46/0x70 [amdgpu]
[48662.087081] ? find_held_lock+0x32/0x90
[48662.087154] amdgpu_vm_sdma_prepare+0x30/0x90 [amdgpu]
[48662.087243] amdgpu_vm_bo_update_mapping+0x7b/0xe0 [amdgpu]
[48662.087318] amdgpu_vm_clear_freed+0xd5/0x1d0 [amdgpu]
[48662.087395] amdgpu_gem_object_close+0x159/0x1b0 [amdgpu]
[48662.087407] ? lockdep_hardirqs_on+0xf0/0x180
[48662.087432] drm_gem_object_release_handle+0x30/0x90 [drm]
[48662.087447] ? drm_gem_object_handle_put_unlocked+0xa0/0xa0 [drm]
[48662.087453] idr_for_each+0x5e/0xd0
[48662.087459] ? mark_held_locks+0x50/0x80
[48662.087477] drm_gem_release+0x1c/0x30 [drm]
[48662.087492] drm_file_free.part.0+0x22e/0x270 [drm]
[48662.087509] drm_release+0xab/0xe0 [drm]
[48662.087517] __fput+0xdd/0x270
[48662.087525] task_work_run+0x93/0xd0
[48662.087533] do_exit+0x349/0xcd0
[48662.087539] ? find_held_lock+0x32/0x90
[48662.087548] do_group_exit+0x47/0xb0
[48662.087554] get_signal+0x17e/0xcb0
[48662.087565] do_signal+0x36/0x680
[48662.087580] exit_to_usermode_loop+0x8d/0x120
[48662.087588] syscall_return_slowpath+0x205/0x330
[48662.087594] entry_SYSCALL_64_after_hwframe+0x49/0xbe
[48662.087599] RIP: 0033:0x7f0b10b4ffaa
[48662.087606] Code: Bad RIP value.
[48662.087610] RSP: 002b:00007f0ae77fdc40 EFLAGS: 00000246 ORIG_RAX:
00000000000000ca
[48662.087615] RAX: fffffffffffffdfc RBX: 00000000000051ac RCX:
00007f0b10b4ffaa
[48662.087619] RDX: 0000000000000000 RSI: 0000000000000189 RDI:
00007f0b0ebf1170
[48662.087622] RBP: 00007f0b0ebf1148 R08: 0000000000000000 R09:
00000000ffffffff
[48662.087626] R10: 00007f0ae77fdd48 R11: 0000000000000246 R12:
0000000000000000
[48662.087629] R13: 00007f0b0ebf1120 R14: 00007f0b0ebf1170 R15:
00007f0ae77fdc80
[48662.087646]
Showing all locks held in the system:
[48662.087662] 1 lock held by khungtaskd/96:
[48662.087665] #0: ffffffff8d693760 (rcu_read_lock){....}, at:
debug_show_all_locks+0x15/0x174
[48662.087738] 1 lock held by CPU 0/KVM/3098:
[48662.087833] 2 locks held by dnf/104312:
[48662.087836] #0: ffff8d88dacc80a0 (&tty->ldisc_sem){++++}, at:
tty_ldisc_ref_wait+0x24/0x50
[48662.087844] #1: ffffa1088052a2f0 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0xe3/0x980
[48662.088002] 3 locks held by kworker/15:0/152888:
[48662.088005] #0: ffff8d8936c21548 ((wq_completion)events){+.+.}, at:
process_one_work+0x1e9/0x5a0
[48662.088012] #1: ffffa1088d61fe50
((work_completion)(&(&bdev->wq)->work)){+.+.}, at: process_one_work+0x1e9/0x5a0
[48662.088018] #2: ffff8d892bf5c9f8 (reservation_ww_class_mutex){+.+.}, at:
ttm_bo_delayed_delete+0x8d/0x200 [ttm]
[48662.088032] 3 locks held by OnlineA-nstance/153979:
[48662.088035] #0: ffffffffc0303070 (drm_global_mutex){+.+.}, at:
drm_release+0x2c/0xe0 [drm]
[48662.088054] #1: ffffa1088d457b30 (reservation_ww_class_acquire){+.+.}, at:
amdgpu_gem_object_close+0xce/0x1b0 [amdgpu]
[48662.088126] #2: ffff8d892bf5c9f8 (reservation_ww_class_mutex){+.+.}, at:
ttm_eu_reserve_buffers+0x349/0x620 [ttm]
[48662.088146] =============================================
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-09-24 17:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 17:54 bugzilla-daemon [this message]
2019-09-24 17:56 ` [Bug 111803] Annoying GPU stucks are continued on Vega 20 with Kernel 5.4 + mesa 9.3.0 + llvm 9.0.0 [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! bugzilla-daemon
2019-09-24 17:56 ` bugzilla-daemon
2019-09-24 17:57 ` bugzilla-daemon
2019-09-24 19:04 ` bugzilla-daemon
2019-09-24 19:05 ` bugzilla-daemon
2019-09-24 19:05 ` bugzilla-daemon
2019-09-24 19:06 ` bugzilla-daemon
2019-09-26 18:48 ` bugzilla-daemon
2019-09-26 18:48 ` bugzilla-daemon
2019-09-26 18:49 ` bugzilla-daemon
2019-09-26 18:49 ` bugzilla-daemon
2019-09-26 18:50 ` bugzilla-daemon
2019-09-26 18:50 ` bugzilla-daemon
2019-09-26 18:51 ` bugzilla-daemon
2019-09-26 18:51 ` bugzilla-daemon
2019-09-26 18:52 ` bugzilla-daemon
2019-09-26 18:52 ` bugzilla-daemon
2019-09-26 18:53 ` bugzilla-daemon
2019-09-27 16:54 ` bugzilla-daemon
2019-09-27 16:54 ` bugzilla-daemon
2019-09-27 16:54 ` bugzilla-daemon
2019-09-27 16:55 ` bugzilla-daemon
2019-09-27 16:55 ` bugzilla-daemon
2019-09-27 16:55 ` bugzilla-daemon
2019-09-27 16:56 ` bugzilla-daemon
2019-09-27 16:56 ` bugzilla-daemon
2019-09-30 4:18 ` bugzilla-daemon
2019-09-30 6:43 ` bugzilla-daemon
2019-09-30 6:43 ` bugzilla-daemon
2019-10-05 9:17 ` bugzilla-daemon
2019-10-05 9:18 ` bugzilla-daemon
2019-10-05 9:18 ` bugzilla-daemon
2019-10-05 9:19 ` bugzilla-daemon
2019-10-05 9:20 ` bugzilla-daemon
2019-10-05 9:20 ` bugzilla-daemon
2019-10-05 9:21 ` bugzilla-daemon
2019-11-19 9:53 ` 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-111803-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.