From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104001] GPU driver hung when start steam client while playback video on Youtube (it occurs on latest staging kernel)
Date: Fri, 02 Mar 2018 20:21:07 +0000 [thread overview]
Message-ID: <bug-104001-502-Db1rxa3eAx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104001-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 5280 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104001
Dennis Schridde <devurandom@gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |devurandom@gmx.net
--- Comment #27 from Dennis Schridde <devurandom@gmx.net> ---
I run into this issue regularly with an AMD Ryzen 5 2400G (primary display,
connected via DP to the monitor) and an AMD Radeon RX 560 (not connected to a
monitor, secondary display according to mainboard firmware configuration).
After using my computer for some time, the graphics suddenly freezes and I see
lines like the following in dmesg (after logging in via SSH):
[Fri Mar 2 21:05:33 2018] amdgpu: [powerplay] pp_dpm_get_temperature was not
implemented.
[Fri Mar 2 21:06:03 2018] INFO: task X:898 blocked for more than 120 seconds.
[Fri Mar 2 21:06:03 2018] Tainted: G W 4.15.7-gentoo-r1 #2
[Fri Mar 2 21:06:03 2018] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[Fri Mar 2 21:06:03 2018] X D 0 898 881 0x00000004
[Fri Mar 2 21:06:03 2018] Call Trace:
[Fri Mar 2 21:06:03 2018] ? __schedule+0x2a7/0x8b0
[Fri Mar 2 21:06:03 2018] schedule+0x28/0x80
[Fri Mar 2 21:06:03 2018] schedule_preempt_disabled+0xa/0x10
[Fri Mar 2 21:06:03 2018] __ww_mutex_lock.isra.3+0x224/0x690
[Fri Mar 2 21:06:03 2018] ? drm_modeset_backoff+0x3e/0xb0 [drm]
[Fri Mar 2 21:06:03 2018] drm_modeset_backoff+0x3e/0xb0 [drm]
[Fri Mar 2 21:06:03 2018] drm_mode_gamma_set_ioctl+0xb4/0x200 [drm]
[Fri Mar 2 21:06:03 2018] ? drm_mode_crtc_set_gamma_size+0xa0/0xa0 [drm]
[Fri Mar 2 21:06:03 2018] drm_ioctl_kernel+0x5b/0xb0 [drm]
[Fri Mar 2 21:06:03 2018] drm_ioctl+0x2d5/0x370 [drm]
[Fri Mar 2 21:06:03 2018] ? drm_mode_crtc_set_gamma_size+0xa0/0xa0 [drm]
[Fri Mar 2 21:06:03 2018] amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
[Fri Mar 2 21:06:03 2018] do_vfs_ioctl+0xa4/0x670
[Fri Mar 2 21:06:03 2018] ? __sys_recvmsg+0x64/0xa0
[Fri Mar 2 21:06:03 2018] ? __sys_recvmsg+0x95/0xa0
[Fri Mar 2 21:06:03 2018] SyS_ioctl+0x74/0x80
[Fri Mar 2 21:06:03 2018] do_syscall_64+0x6e/0x120
[Fri Mar 2 21:06:03 2018] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[Fri Mar 2 21:06:03 2018] RIP: 0033:0x7fd8924c0467
[Fri Mar 2 21:06:03 2018] RSP: 002b:00007ffcb17d7b08 EFLAGS: 00000246
ORIG_RAX: 0000000000000010
[Fri Mar 2 21:06:03 2018] RAX: ffffffffffffffda RBX: 0000560ddb4480e0 RCX:
00007fd8924c0467
[Fri Mar 2 21:06:03 2018] RDX: 00007ffcb17d7b40 RSI: 00000000c02064a5 RDI:
0000000000000016
[Fri Mar 2 21:06:03 2018] RBP: 00007ffcb17d7b40 R08: 0000560ddb4487a0 R09:
0000560ddb4489a0
[Fri Mar 2 21:06:03 2018] R10: 0000000000000001 R11: 0000000000000246 R12:
00000000c02064a5
[Fri Mar 2 21:06:03 2018] R13: 0000000000000016 R14: 0000560ddb448bb0 R15:
0000560ddb4485a0
[Fri Mar 2 21:06:03 2018] INFO: task kworker/u32:2:32344 blocked for more than
120 seconds.
[Fri Mar 2 21:06:03 2018] Tainted: G W 4.15.7-gentoo-r1 #2
[Fri Mar 2 21:06:03 2018] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[Fri Mar 2 21:06:03 2018] kworker/u32:2 D 0 32344 2 0x80000000
[Fri Mar 2 21:06:03 2018] Workqueue: events_unbound commit_work
[drm_kms_helper]
[Fri Mar 2 21:06:03 2018] Call Trace:
[Fri Mar 2 21:06:03 2018] ? __schedule+0x2a7/0x8b0
[Fri Mar 2 21:06:03 2018] schedule+0x28/0x80
[Fri Mar 2 21:06:03 2018] schedule_timeout+0x1e7/0x370
[Fri Mar 2 21:06:03 2018] ? generic_reg_get+0x21/0x30 [amdgpu]
[Fri Mar 2 21:06:03 2018] dma_fence_default_wait+0x1f0/0x280
[Fri Mar 2 21:06:03 2018] ? dma_fence_release+0x90/0x90
[Fri Mar 2 21:06:03 2018] dma_fence_wait_timeout+0x39/0xf0
[Fri Mar 2 21:06:03 2018] reservation_object_wait_timeout_rcu+0x17b/0x370
[Fri Mar 2 21:06:03 2018] amdgpu_dm_do_flip+0x11f/0x360 [amdgpu]
[Fri Mar 2 21:06:03 2018] amdgpu_dm_atomic_commit_tail+0x8a1/0x9a0 [amdgpu]
[Fri Mar 2 21:06:03 2018] ? _cond_resched+0x15/0x40
[Fri Mar 2 21:06:03 2018] ? wait_for_completion_timeout+0x35/0x180
[Fri Mar 2 21:06:03 2018] commit_tail+0x3d/0x70 [drm_kms_helper]
[Fri Mar 2 21:06:03 2018] process_one_work+0x1da/0x3d0
[Fri Mar 2 21:06:03 2018] worker_thread+0x2b/0x3f0
[Fri Mar 2 21:06:03 2018] ? process_one_work+0x3d0/0x3d0
[Fri Mar 2 21:06:03 2018] kthread+0x113/0x130
[Fri Mar 2 21:06:03 2018] ? kthread_create_worker_on_cpu+0x70/0x70
[Fri Mar 2 21:06:03 2018] ? SyS_exit_group+0x10/0x10
[Fri Mar 2 21:06:03 2018] ret_from_fork+0x22/0x40
[Fri Mar 2 21:06:33 2018] i2c /dev entries driver
Everything apart from the graphics appears to continue to run fine, except any
application (e.g. started on the command line) that tries to talk to the X
server: They will hang. Most applications that hang can be killed with
SIGKILL, except the X server and a few others, which will be zombies forever.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6817 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 prev parent reply other threads:[~2018-03-02 20:21 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 20:53 [Bug 104001] GPU driver hung when start steam client while playback video on Youtube (it occurs on latest staging kernel) bugzilla-daemon
2017-12-01 9:06 ` bugzilla-daemon
2017-12-01 9:18 ` bugzilla-daemon
2017-12-05 16:56 ` bugzilla-daemon
2017-12-06 20:13 ` bugzilla-daemon
2017-12-07 17:08 ` bugzilla-daemon
2017-12-15 17:43 ` bugzilla-daemon
2017-12-21 18:27 ` bugzilla-daemon
2017-12-21 18:28 ` bugzilla-daemon
2018-01-03 9:58 ` [Bug 104001] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=6582, last emitted seq=6584 bugzilla-daemon
2018-01-03 9:58 ` bugzilla-daemon
2018-01-03 10:00 ` [Bug 104001] GPU driver hung when start steam client while playback video on Youtube (it occurs on latest staging kernel) bugzilla-daemon
2018-01-03 10:07 ` bugzilla-daemon
2018-01-05 12:14 ` bugzilla-daemon
2018-01-06 1:18 ` bugzilla-daemon
2018-01-06 1:20 ` bugzilla-daemon
2018-01-06 3:44 ` bugzilla-daemon
2018-01-07 17:00 ` bugzilla-daemon
2018-01-17 17:51 ` bugzilla-daemon
2018-01-18 21:05 ` bugzilla-daemon
2018-01-19 8:47 ` bugzilla-daemon
2018-01-19 18:00 ` bugzilla-daemon
2018-02-04 15:34 ` bugzilla-daemon
2018-02-28 3:43 ` bugzilla-daemon
2018-02-28 3:44 ` bugzilla-daemon
2018-03-01 4:19 ` bugzilla-daemon
2018-03-01 4:21 ` bugzilla-daemon
2018-03-01 9:06 ` bugzilla-daemon
2018-03-01 18:42 ` bugzilla-daemon
2018-03-02 20:21 ` bugzilla-daemon [this message]
2018-03-02 20:22 ` bugzilla-daemon
2018-03-24 14:28 ` bugzilla-daemon
2018-04-21 0:36 ` bugzilla-daemon
2018-04-21 16:31 ` bugzilla-daemon
2018-04-27 21:57 ` bugzilla-daemon
2018-05-05 8:56 ` bugzilla-daemon
2018-05-05 8:58 ` bugzilla-daemon
2018-05-05 9:14 ` bugzilla-daemon
2018-05-05 9:17 ` bugzilla-daemon
2018-05-06 4:19 ` bugzilla-daemon
2018-05-06 17:50 ` bugzilla-daemon
2018-05-06 20:23 ` bugzilla-daemon
2018-05-07 18:04 ` 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-104001-502-Db1rxa3eAx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox