From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 104345] Playing video hangs X-Server with showing scrambled picture, sound still playing. Date: Thu, 20 Dec 2018 14:09:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0023723870==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 7B7176E3A2 for ; Thu, 20 Dec 2018 14:09:23 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0023723870== Content-Type: multipart/alternative; boundary="15453149630.bbeC8e.7066" Content-Transfer-Encoding: 7bit --15453149630.bbeC8e.7066 Date: Thu, 20 Dec 2018 14:09:23 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D104345 --- Comment #12 from bernhardu --- Created attachment 142867 --> https://bugs.freedesktop.org/attachment.cgi?id=3D142867&action=3Dedit 2018-12-20-crash.txt The last months I observed this less. But in December it started to get more visible again. (I am following debian testing closely.) It shows now nearly always when e.g. browsing with firefox - even in simple sites e.g. bugtrackers. The chess board like pattern is still the same. The blocked kernel threads stack changed with some kernel upgrade to: Call Trace: ? __schedule+0x2b7/0x880 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 schedule+0x28/0x80 schedule_timeout+0x1ee/0x380 ? dce110_timing_generator_get_position+0x5b/0x70 [amdgpu] ? dce110_timing_generator_get_crtc_scanoutpos+0x70/0xb0 [amdgpu] dma_fence_default_wait+0x1fd/0x280 ? dma_fence_release+0x90/0x90 dma_fence_wait_timeout+0x39/0xf0 reservation_object_wait_timeout_rcu+0x10a/0x290 amdgpu_dm_do_flip+0x112/0x340 [amdgpu] amdgpu_dm_atomic_commit_tail+0xbac/0xdb0 [amdgpu] ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to+0x16f/0x450 commit_tail+0x3d/0x70 [drm_kms_helper] process_one_work+0x195/0x380 worker_thread+0x30/0x390 ? process_one_work+0x380/0x380 kthread+0x113/0x130 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x22/0x40 What can I do to get this bug forward? --=20 You are receiving this mail because: You are the assignee for the bug.= --15453149630.bbeC8e.7066 Date: Thu, 20 Dec 2018 14:09:23 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 12 on bug 10434= 5 from bernhardu 
Created attachment 142867 [details]
2018-12-20-crash.txt

The last months I observed this less.
But in December it started to get more visible again.
(I am following debian testing closely.)

It shows now nearly always when e.g. browsing with firefox -
even in simple sites e.g. bugtrackers.

The chess board like pattern is still the same.

The blocked kernel threads stack changed with some kernel upgrade to:

Call Trace:
 ? __schedule+0x2b7/0x880
 ? __switch_to_asm+0x40/0x70
 ? __switch_to_asm+0x34/0x70
 schedule+0x28/0x80
 schedule_timeout+0x1ee/0x380
 ? dce110_timing_generator_get_position+0x5b/0x70 [amdgpu]
 ? dce110_timing_generator_get_crtc_scanoutpos+0x70/0xb0 [amdgpu]
 dma_fence_default_wait+0x1fd/0x280
 ? dma_fence_release+0x90/0x90
 dma_fence_wait_timeout+0x39/0xf0
 reservation_object_wait_timeout_rcu+0x10a/0x290
 amdgpu_dm_do_flip+0x112/0x340 [amdgpu]
 amdgpu_dm_atomic_commit_tail+0xbac/0xdb0 [amdgpu]
 ? __switch_to_asm+0x34/0x70
 ? __switch_to_asm+0x40/0x70
 ? __switch_to+0x16f/0x450
 commit_tail+0x3d/0x70 [drm_kms_helper]
 process_one_work+0x195/0x380
 worker_thread+0x30/0x390
 ? process_one_work+0x380/0x380
 kthread+0x113/0x130
 ? kthread_create_worker_on_cpu+0x70/0x70
 ret_from_fork+0x22/0x40

What can I do to get this bug forward?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15453149630.bbeC8e.7066-- --===============0023723870== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0023723870==--