dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105819] Window system hang due to GPU Fault
Date: Sat, 30 Jun 2018 17:42:44 +0000	[thread overview]
Message-ID: <bug-105819-502-bdyAdFmw5q@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105819-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2608 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105819

--- Comment #5 from Kertesz Laszlo <laszlo.kertesz@gmail.com> ---
I have this issue too. 
Debian testing, kernel compiled from mainline git

It begun with the 4.18 kernels (mainline), now i am on 4.18 rc2+ and still
happens. I did not see this with the 4.17 kernels.

For me it happened a few times, most times i was clicking around in Firefox and
once when i let the computer idle (Firefox was still in the foreground though).
I logged in via ssh and captured these from dmesg:

One instance (i think i reset the system with the magic key combination so it
didn't get to the hung timeout:
[ 3459.767019] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
last signaled seq=92850, last emitted seq=92853
[ 3459.767028] amdgpu 0000:06:00.0: GPU reset begin!

Another one:

[275981.536711] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
last signaled seq=5720217, last emitted seq=5720220
[275981.536720] amdgpu 0000:06:00.0: GPU reset begin!
[276099.291632] INFO: task kworker/u32:3:15729 blocked for more than 120
seconds.
[276099.291639]       Tainted: G        W   E     4.18.0-rc1 #1
[276099.291641] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[276099.291643] kworker/u32:3   D    0 15729      2 0x80000000
[276099.291661] Workqueue: events_unbound commit_work [drm_kms_helper]
[276099.291664] Call Trace:
[276099.291674]  ? __schedule+0x2b7/0x890
[276099.291680]  ? __update_load_avg_se.isra.38+0x1cf/0x1e0
[276099.291684]  schedule+0x28/0x80
[276099.291688]  schedule_timeout+0x1ee/0x380
[276099.291754]  ? generic_reg_get+0x20/0x30 [amdgpu]
[276099.291815]  ? optc1_get_crtc_scanoutpos+0x68/0xa0 [amdgpu]
[276099.291820]  dma_fence_default_wait+0x1fd/0x280
[276099.291823]  ? dma_fence_release+0x90/0x90
[276099.291826]  dma_fence_wait_timeout+0x39/0xf0
[276099.291830]  reservation_object_wait_timeout_rcu+0x17b/0x370
[276099.291892]  amdgpu_dm_do_flip+0x112/0x350 [amdgpu]
[276099.291898]  ? __wake_up_common+0x76/0x170
[276099.291955]  amdgpu_dm_atomic_commit_tail+0xb91/0xd90 [amdgpu]
[276099.291961]  ? __switch_to+0x16f/0x440
[276099.291970]  commit_tail+0x3d/0x70 [drm_kms_helper]
[276099.291974]  process_one_work+0x195/0x370
[276099.291978]  worker_thread+0x30/0x390
[276099.291981]  ? process_one_work+0x370/0x370
[276099.291984]  kthread+0x113/0x130
[276099.291987]  ? kthread_create_worker_on_cpu+0x70/0x70
[276099.291990]  ret_from_fork+0x22/0x40

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3383 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

  parent reply	other threads:[~2018-06-30 17:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-30 17:59 [Bug 105819] Window system hang due to GPU Fault bugzilla-daemon
2018-03-31 22:34 ` bugzilla-daemon
2018-04-12 10:52 ` bugzilla-daemon
2018-04-30  2:44 ` bugzilla-daemon
2018-05-20  6:28 ` bugzilla-daemon
2018-06-30 17:42 ` bugzilla-daemon [this message]
2018-07-01 16:08 ` bugzilla-daemon
2018-07-04 12:29 ` bugzilla-daemon
2018-09-15 22:22 ` bugzilla-daemon
2018-09-18  2:11 ` bugzilla-daemon
2019-01-12 17:22 ` bugzilla-daemon
2019-04-26  1:54 ` bugzilla-daemon
2019-05-07 12:19 ` bugzilla-daemon
2019-11-17  5:11 ` bugzilla-daemon
2019-11-19  8:33 ` 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-105819-502-bdyAdFmw5q@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