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 110140] Green bottom half of video frame when using JPEG acceleration (vcn_v1_0_jpeg_ring_emit_fence() WARNING)
Date: Sat, 16 Mar 2019 23:51:13 +0000	[thread overview]
Message-ID: <bug-110140-502-7fYiF7M9aP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110140-502@http.bugs.freedesktop.org/>


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

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

--- Comment #4 from Rafał Miłecki <zajec5@gmail.com> ---
Another problem caused by the above commit 36258308a794 is re-introducing
corrupted colors in YouTube playbacks when using Chromium with "Use hardware
acceleration when available" enabled. That was originally reported by me in the
bug 109080.

Playing YouTube video using kernel 5.0.1 and Mesa 18.3.4 results in corrupted
colors and following errors:

[ 6376.312717] gmc_v9_0_process_interrupt: 38 callbacks suppressed
[ 6376.312726] amdgpu 0000:04:00.0: [mmhub] VMC page fault (src_id:0 ring:40
vmid:3 pasid:32775, for process chromium pid 21146 thread chromium -:cs0 pid
21208)
[ 6376.312730] amdgpu 0000:04:00.0:   in page starting at address
0x0000800106198000 from 18
[ 6376.312733] amdgpu 0000:04:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00340451
[ 6376.312746] amdgpu 0000:04:00.0: [mmhub] VMC page fault (src_id:0 ring:40
vmid:3 pasid:32775, for process chromium pid 21146 thread chromium -:cs0 pid
21208)
[ 6376.312748] amdgpu 0000:04:00.0:   in page starting at address
0x0000800106199000 from 18
[ 6376.312750] amdgpu 0000:04:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 6376.312762] amdgpu 0000:04:00.0: [mmhub] VMC page fault (src_id:0 ring:174
vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[ 6376.312764] amdgpu 0000:04:00.0:   in page starting at address
0x0000000000000000 from 18
[ 6376.312766] amdgpu 0000:04:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0000073C
[ 6376.312781] amdgpu 0000:04:00.0: [mmhub] VMC page fault (src_id:0 ring:158
vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[ 6376.312783] amdgpu 0000:04:00.0:   in page starting at address
0x0000000000000000 from 18
[ 6376.312785] amdgpu 0000:04:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 6386.301258] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_dec timeout,
signaled seq=192, emitted seq=194
[ 6386.301398] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process  pid 0 thread  pid 0
[ 6386.301414] [drm] GPU recovery disabled.
[ 6396.541548] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_dec timeout,
signaled seq=192, emitted seq=194
[ 6396.541636] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process  pid 0 thread  pid 0
[ 6396.541639] [drm] GPU recovery disabled.
[ 6406.782141] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_dec timeout,
signaled seq=192, emitted seq=194
[ 6406.782241] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process  pid 0 thread  pid 0
[ 6406.782244] [drm] GPU recovery disabled.
[ 6417.022165] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_dec timeout,
signaled seq=192, emitted seq=194
[ 6417.022268] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process  pid 0 thread  pid 0
[ 6417.022271] [drm] GPU recovery disabled.

my screen freezes shortly after that.

I've verified that reverting 36258308a794 from the top of 18.3.4 release fixes
both issues.

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

[-- Attachment #1.2: Type: text/html, Size: 4209 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-03-16 23:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-16 17:42 [Bug 110140] Green bottom half of video frame when using JPEG acceleration (vcn_v1_0_jpeg_ring_emit_fence() WARNING) bugzilla-daemon
2019-03-16 17:48 ` bugzilla-daemon
2019-03-16 17:48 ` bugzilla-daemon
2019-03-16 23:20 ` bugzilla-daemon
2019-03-16 23:51 ` bugzilla-daemon [this message]
2019-03-17  2:24 ` bugzilla-daemon
2019-03-17  2:42 ` bugzilla-daemon
2019-03-17 22:16 ` bugzilla-daemon
2019-03-17 22:19 ` bugzilla-daemon
2019-03-18 13:12 ` bugzilla-daemon
2019-09-25 18:49 ` 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-110140-502-7fYiF7M9aP@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