From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104345] Playing video hangs X-Server with showing scrambled picture, sound still playing.
Date: Wed, 20 Dec 2017 10:05:22 +0000 [thread overview]
Message-ID: <bug-104345-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4423 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104345
Bug ID: 104345
Summary: Playing video hangs X-Server with showing scrambled
picture, sound still playing.
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: bernhardu@mailbox.org
Created attachment 136312
--> https://bugs.freedesktop.org/attachment.cgi?id=136312&action=edit
kernel output captured from the serial line.
Playing video hangs X-Server with showing scrambled picture, sound still
playing.
System hangs after some time playing mostly when playing a recorded DVB-S-SD
stream via VLC. Happened also with other videos and players.
This left the system showing a distorted version of the last shown frame from
the video. Most of the time it is a chess board like pattern.
Sound is still playing regularly.
A ssh connection is still possible.
Playing the exact same video again later works without problem.
Kernel output shows at this time following:
[ 4353.316286] amdgpu 0000:08:00.0: GPU fault detected: 146 0x0570480c
[ 4353.328836] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x001004AE
[ 4353.343791] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A04800C
[ 4353.358755] amdgpu 0000:08:00.0: VM fault (0x0c, vmid 5) at page 1049774,
read from 'TC0' (0x54433000) (72)
[ 4353.378234] amdgpu 0000:08:00.0: GPU fault detected: 146 0x0570440c
[ 4353.390777] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x0010049C
[ 4353.405735] amdgpu 0000:08:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0A04400C
[ 4353.420692] amdgpu 0000:08:00.0: VM fault (0x0c, vmid 5) at page 1049756,
read from 'TC1' (0x54433100) (68)
Followed by this:
[ 4592.681352] INFO: task amdgpu_cs:0:1007 blocked for more than 120 seconds.
[ 4592.695116] Tainted: G O 4.13.0-1-amd64 #1 Debian
4.13.13-1
[ 4592.709587] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 4592.725255] amdgpu_cs:0 D 0 1007 1000 0x00400000
[ 4592.736245] Call Trace:
[ 4592.741145] ? __schedule+0x3c8/0x860
[ 4592.748486] ? schedule+0x32/0x80
[ 4592.755120] ? schedule_timeout+0x1da/0x350
[ 4592.763537] ? amdgpu_vm_validate_level.isra.9+0x80/0x80 [amdgpu]
[ 4592.775725] ? dma_fence_default_wait+0x239/0x260
[ 4592.785138] ? dma_fence_default_wait+0x239/0x260
[ 4592.794548] ? dma_fence_free+0x20/0x20
[ 4592.802220] ? dma_fence_wait_timeout+0x33/0xe0
[ 4592.811317] ? amdgpu_ctx_add_fence+0x61/0xf0 [amdgpu]
[ 4592.821632] ? amdgpu_cs_ioctl+0x156b/0x1920 [amdgpu]
[ 4592.831784] ? amdgpu_cs_find_mapping+0x90/0x90 [amdgpu]
[ 4592.842432] ? drm_ioctl_kernel+0x65/0xb0 [drm]
[ 4592.851510] ? drm_ioctl+0x2e3/0x3a0 [drm]
[ 4592.859737] ? amdgpu_cs_find_mapping+0x90/0x90 [amdgpu]
[ 4592.870373] ? do_futex+0x2df/0xa90
[ 4592.877376] ? amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
[ 4592.886971] ? do_vfs_ioctl+0x9f/0x600
[ 4592.894471] ? SyS_futex+0x7a/0x170
[ 4592.901453] ? SyS_ioctl+0x74/0x80
[ 4592.908264] ? system_call_fast_compare_end+0xc/0x97
Attached is a log captured on the serial port from boot to the
crash follwed by a Magic-Sys-Req-T.
This are the system specs:
Graphics: Card: Advanced Micro Devices [AMD/ATI] Baffin [Radeon RX 460] (XFX)
Display Server: x11 (X.Org 1.19.5 ) drivers: amdgpu (unloaded:
modesetting,fbdev,vesa)
Resolution: 1920x1080@60.00hz
OpenGL: renderer: AMD Radeon RX 460 Graphics (AMD POLARIS11 / DRM
3.18.0 / 4.13.0-1-amd64, LLVM 5.0.0)
version: 4.5 Mesa 17.2.5
System: Kernel: 4.13.0-1-amd64 x86_64 bits: 64
Desktop: KDE Plasma 5.10.5
Machine: Device: desktop Mobo: ASUSTeK model: PRIME B350M-A v: Rev X.0x
serial: N/A
UEFI: American Megatrends v: 3203 date: 11/09/2017
CPU: Octa core AMD Ryzen 7 1700 Eight-Core (-HT-MCP-) speed/max:
1550/3000 MHz
Error happened with Debian Stretch with linux 4.9 and later.
Currently it is running a Debian testing.
Is this the right product/component for this report?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5971 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 reply other threads:[~2017-12-20 10:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 10:05 bugzilla-daemon [this message]
2017-12-20 10:10 ` [Bug 104345] Playing video hangs X-Server with showing scrambled picture, sound still playing 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
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@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.