From: "Liu, Leo" <Leo.Liu-5C7GfCeVMHo@public.gmane.org>
To: "S, Shirish" <Shirish.S-5C7GfCeVMHo@public.gmane.org>,
"Grodzovsky,
Andrey" <Andrey.Grodzovsky-5C7GfCeVMHo@public.gmane.org>,
"Zhang, Jerry" <Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>,
"Deng, Emily" <Emily.Deng-5C7GfCeVMHo@public.gmane.org>,
"Deucher,
Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>
Cc: "amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"Li,
Ching-shih (Louis)" <Ching-shih.Li-5C7GfCeVMHo@public.gmane.org>
Subject: Re: [PATCH] drm/amdgpu: fix ring test failure issue during s3 in vce 3.0
Date: Mon, 27 May 2019 13:00:50 +0000 [thread overview]
Message-ID: <c2e96ff1-522f-4d1d-f312-9209a63e58ce@amd.com> (raw)
In-Reply-To: <1558942936-16519-1-git-send-email-shirish.s-5C7GfCeVMHo@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1647 bytes --]
On 5/27/19 3:42 AM, S, Shirish wrote:
From: Louis Li <Ching-shih.Li@amd.com><mailto:Ching-shih.Li@amd.com>
[What]
vce ring test fails consistently during resume in s3 cycle, due to
mismatch read & write pointers.
On debug/analysis its found that rptr to be compared is not being
correctly updated/read, which leads to this failure.
Below is the failure signature:
[drm:amdgpu_vce_ring_test_ring] *ERROR* amdgpu: ring 12 test failed
[drm:amdgpu_device_ip_resume_phase2] *ERROR* resume of IP block <vce_v3_0> failed -110
[drm:amdgpu_device_resume] *ERROR* amdgpu_device_ip_resume failed (-110).
[How]
fetch rptr appropriately, meaning move its read location further down
in the code flow.
With this patch applied the s3 failure is no more seen for >5k s3 cycles,
which otherwise is pretty consistent.
Signed-off-by: Louis Li <Ching-shih.Li@amd.com><mailto:Ching-shih.Li@amd.com>
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c
index c021b11..92f9d46 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c
@@ -1084,6 +1084,8 @@ int amdgpu_vce_ring_test_ring(struct amdgpu_ring *ring)
if (r)
return r;
+ rptr = amdgpu_ring_get_rptr(ring);
+
The rptr update is there:
uint32_t rptr = amdgpu_ring_get_rptr(ring);
Are you sure this is the root cause?
Regards,
Leo
amdgpu_ring_write(ring, VCE_CMD_END);
amdgpu_ring_commit(ring);
[-- Attachment #1.2: Type: text/html, Size: 2270 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2019-05-27 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 7:42 [PATCH] drm/amdgpu: fix ring test failure issue during s3 in vce 3.0 S, Shirish
[not found] ` <1558942936-16519-1-git-send-email-shirish.s-5C7GfCeVMHo@public.gmane.org>
2019-05-27 13:00 ` Liu, Leo [this message]
[not found] ` <c2e96ff1-522f-4d1d-f312-9209a63e58ce-5C7GfCeVMHo@public.gmane.org>
2019-05-27 16:22 ` Li, Ching-shih (Louis)
[not found] ` <MN2PR12MB34398CEE701707E25781E9A2AA1D0-rweVpJHSKTpimzxKl6w4wgdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-05-27 16:39 ` Liu, Leo
[not found] ` <70c3ff3e-1f14-fcd6-e533-8e224fe0b976-5C7GfCeVMHo@public.gmane.org>
2019-05-27 17:20 ` Li, Ching-shih (Louis)
[not found] ` <MN2PR12MB3439645C85B84D0382352D04AA1D0-rweVpJHSKTpimzxKl6w4wgdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-05-28 7:23 ` Christian König
[not found] ` <3763ca45-b90e-dac9-f2a7-35aee4dc2548-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-05-29 1:14 ` Li, Ching-shih (Louis)
[not found] ` <MN2PR12MB34393B9022F9CF06D2F7D6FDAA1F0-rweVpJHSKTpimzxKl6w4wgdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-05-29 7:52 ` Koenig, Christian
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=c2e96ff1-522f-4d1d-f312-9209a63e58ce@amd.com \
--to=leo.liu-5c7gfcevmho@public.gmane.org \
--cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
--cc=Andrey.Grodzovsky-5C7GfCeVMHo@public.gmane.org \
--cc=Ching-shih.Li-5C7GfCeVMHo@public.gmane.org \
--cc=Emily.Deng-5C7GfCeVMHo@public.gmane.org \
--cc=Jerry.Zhang-5C7GfCeVMHo@public.gmane.org \
--cc=Shirish.S-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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