All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104345] X-Server hangs with showing scrambled picture, sound still playing.
Date: Mon, 29 Apr 2019 14:54:40 +0000	[thread overview]
Message-ID: <bug-104345-502-CwHowcLSq0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104345-502@http.bugs.freedesktop.org/>


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

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

--- Comment #14 from bernhardu <bernhardu@mailbox.org> ---
This sample happend while just browsing in firefox inside a plasma desktop,
running in amd64 debian buster.


[138335.303379] amdgpu 0000:08:00.0: GPU fault detected: 147 0x0a704402 for
process Xorg pid 1129 thread Xorg:cs0 pid 1161
[138335.303387] amdgpu 0000:08:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x0012014E
[138335.303391] amdgpu 0000:08:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0E044002
[138335.303396] amdgpu 0000:08:00.0: VM fault (0x02, vmid 7, pasid 32768) at
page 1179982, read from 'TC1' (0x54433100) (68)
[138335.313378] amdgpu 0000:08:00.0: GPU fault detected: 147 0x08904802 for
process kwin_x11 pid 1350 thread kwin_x11:cs0 pid 1568
[138335.313384] amdgpu 0000:08:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00120712
[138335.313388] amdgpu 0000:08:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x02048002
[138335.313393] amdgpu 0000:08:00.0: VM fault (0x02, vmid 1, pasid 32773) at
page 1181458, read from 'TC0' (0x54433000) (72)
[139983.820484] amdgpu 0000:08:00.0: GPU fault detected: 147 0x00004802 for
process Xorg pid 1129 thread Xorg:cs0 pid 1161
[139983.820491] amdgpu 0000:08:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00000800
[139983.820495] amdgpu 0000:08:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0C048002
[139983.820500] amdgpu 0000:08:00.0: VM fault (0x02, vmid 6, pasid 32768) at
page 2048, read from 'TC0' (0x54433000) (72)
[139994.156833] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=14610386, emitted seq=14610389
[139994.156840] [drm] GPU recovery disabled.
[140167.215046] INFO: task kworker/u32:3:15564 blocked for more than 120
seconds.
[140167.215053]       Tainted: G           OE     4.19.0-4-amd64 #1 Debian
4.19.28-2
[140167.215055] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[140167.215058] kworker/u32:3   D    0 15564      2 0x80000000
[140167.215080] Workqueue: events_unbound commit_work [drm_kms_helper]
[140167.215083] Call Trace:
[140167.215093]  ? __schedule+0x2a2/0x870
[140167.215098]  ? __switch_to_asm+0x40/0x70
[140167.215102]  schedule+0x28/0x80
[140167.215106]  schedule_timeout+0x26d/0x390
[140167.215204]  ? dce110_timing_generator_get_position+0x5b/0x70 [amdgpu]
[140167.215300]  ? dce110_timing_generator_get_crtc_scanoutpos+0x70/0xb0
[amdgpu]
[140167.215305]  dma_fence_default_wait+0x238/0x2a0
[140167.215310]  ? dma_fence_release+0x90/0x90
[140167.215314]  dma_fence_wait_timeout+0xdd/0x100
[140167.215319]  reservation_object_wait_timeout_rcu+0x173/0x280
[140167.215420]  amdgpu_dm_do_flip+0x112/0x340 [amdgpu]
[140167.215523]  amdgpu_dm_atomic_commit_tail+0x750/0xdb0 [amdgpu]
[140167.215528]  ? wait_for_completion_timeout+0x3b/0x1a0
[140167.215531]  ? __switch_to_asm+0x34/0x70
[140167.215535]  ? __switch_to_asm+0x40/0x70
[140167.215538]  ? __switch_to_asm+0x34/0x70
[140167.215541]  ? __switch_to_asm+0x40/0x70
[140167.215555]  commit_tail+0x3d/0x70 [drm_kms_helper]
[140167.215562]  process_one_work+0x1a7/0x3a0
[140167.215566]  worker_thread+0x30/0x390
[140167.215571]  ? create_worker+0x1a0/0x1a0
[140167.215573]  kthread+0x112/0x130
[140167.215577]  ? kthread_bind+0x30/0x30
[140167.215581]  ret_from_fork+0x22/0x40
[140241.805748] sysrq: SysRq : Keyboard mode set to system default


What can I do to get this bug forward?

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

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

  parent reply	other threads:[~2019-04-29 14:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20 10:05 [Bug 104345] Playing video hangs X-Server with showing scrambled picture, sound still playing bugzilla-daemon
2017-12-20 10:10 ` bugzilla-daemon
2017-12-20 10:35 ` bugzilla-daemon
2017-12-20 10:38 ` bugzilla-daemon
2017-12-20 21:25 ` bugzilla-daemon
2017-12-20 21:25 ` bugzilla-daemon
2018-01-13 14:33 ` bugzilla-daemon
2018-02-04 10:07 ` bugzilla-daemon
2018-02-04 10:09 ` bugzilla-daemon
2018-02-04 10:26 ` bugzilla-daemon
2018-02-19 12:47 ` bugzilla-daemon
2018-05-22 20:11 ` bugzilla-daemon
2018-12-20 14:09 ` bugzilla-daemon
2018-12-20 14:13 ` [Bug 104345] X-Server hangs " bugzilla-daemon
2019-01-15 13:13 ` bugzilla-daemon
2019-04-29 14:54 ` bugzilla-daemon [this message]
2019-09-25 18:01 ` 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-104345-502-CwHowcLSq0@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.