dri-devel.lists.freedesktop.org archive mirror
 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: Tue, 15 Jan 2019 13:13:52 +0000	[thread overview]
Message-ID: <bug-104345-502-2XGCiKb7wt@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104345-502@http.bugs.freedesktop.org/>


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

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

--- Comment #13 from bernhardu <bernhardu@mailbox.org> ---
Happened again.
A way to avoid that crash may be to not stay int first cold boot.
I am not sure but I think I never saw this when system was
running from a rebooted state (warm boot).


[    0.000000] Linux version 4.19.0-1-amd64 (debian-kernel@lists.debian.org)
(gcc version 8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22)
...
[32345.334084] amdgpu 0000:08:00.0: GPU fault detected: 146 0x06407704 for
process plasmashell pid 1422 thread plasmashel:cs0 pid 1720
[32345.334092] amdgpu 0000:08:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x001002C8
[32345.334096] amdgpu 0000:08:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x02077004
[32345.334101] amdgpu 0000:08:00.0: VM fault (0x04, vmid 1, pasid 32775) at
page 1049288, read from 'SDM0' (0x53444d30) (119)
[32345.334114] amdgpu 0000:08:00.0: GPU fault detected: 146 0x06407704 for
process plasmashell pid 1422 thread plasmashel:cs0 pid 1720
[32345.334118] amdgpu 0000:08:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x001002C8
[32345.334121] amdgpu 0000:08:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x02077004
[32345.334125] amdgpu 0000:08:00.0: VM fault (0x04, vmid 1, pasid 32775) at
page 1049288, read from 'SDM0' (0x53444d30) (119)
[32345.334523] amdgpu 0000:08:00.0: GPU fault detected: 146 0x06d8770c for
process plasmashell pid 1422 thread plasmashel:cs0 pid 1720
[32345.334528] amdgpu 0000:08:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x001002DB
[32345.334532] amdgpu 0000:08:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0207700C
[32345.334538] amdgpu 0000:08:00.0: VM fault (0x0c, vmid 1, pasid 32775) at
page 1049307, read from 'SDM0' (0x53444d30) (119)
[32355.357958] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=947938, emitted seq=947940
[32355.357965] [drm] GPU recovery disabled.
[32505.119425] INFO: task kworker/u32:2:12454 blocked for more than 120
seconds.
[32505.119433]       Tainted: G           OE     4.19.0-1-amd64 #1 Debian
4.19.12-1
[32505.119435] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[32505.119438] kworker/u32:2   D    0 12454      2 0x80000000
[32505.119460] Workqueue: events_unbound commit_work [drm_kms_helper]
[32505.119464] Call Trace:
[32505.119474]  ? __schedule+0x2a2/0x870
[32505.119480]  ? __switch_to_asm+0x40/0x70
[32505.119484]  schedule+0x28/0x80
[32505.119488]  schedule_timeout+0x26d/0x390
[32505.119586]  ? dce110_timing_generator_get_position+0x5b/0x70 [amdgpu]
[32505.119682]  ? dce110_timing_generator_get_crtc_scanoutpos+0x70/0xb0
[amdgpu]
[32505.119687]  dma_fence_default_wait+0x238/0x2a0
[32505.119691]  ? dma_fence_release+0x90/0x90
[32505.119695]  dma_fence_wait_timeout+0xdd/0x100
[32505.119699]  reservation_object_wait_timeout_rcu+0x173/0x280
[32505.119800]  amdgpu_dm_do_flip+0x112/0x340 [amdgpu]
[32505.119903]  amdgpu_dm_atomic_commit_tail+0x750/0xdb0 [amdgpu]
[32505.119909]  ? wait_for_completion_timeout+0x3b/0x1a0
[32505.119913]  ? __switch_to_asm+0x34/0x70
[32505.119917]  ? __switch_to_asm+0x40/0x70
[32505.119921]  ? __switch_to_asm+0x34/0x70
[32505.119924]  ? __switch_to_asm+0x40/0x70
[32505.119938]  commit_tail+0x3d/0x70 [drm_kms_helper]
[32505.119946]  process_one_work+0x1a7/0x3a0
[32505.119951]  worker_thread+0x30/0x390
[32505.119955]  ? pwq_unbound_release_workfn+0xd0/0xd0
[32505.119959]  kthread+0x112/0x130
[32505.119963]  ? kthread_bind+0x30/0x30
[32505.119967]  ret_from_fork+0x22/0x40
[32528.537326] sysrq: SysRq : Keyboard mode set to system default

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

[-- Attachment #1.2: Type: text/html, Size: 4628 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:[~2019-01-15 13:13 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 [this message]
2019-04-29 14:54 ` bugzilla-daemon
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-2XGCiKb7wt@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;
as well as URLs for NNTP newsgroup(s).