> -Original Message-
> From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf
> Of Christian König
> Sent: Monday, October 30, 2017 10:00 AM
> To: dri-de...@lists.freedesktop.org; amd-gfx@lists.freedesktop.org
> Subject: [PATCH] drm/ttm: once more fix ttm_buffer_object_trans
Hi Dieter, Tom,
I'm not sure I'll be able to send a DC commit to fix this today. We should
probably revert the offending commit for now.
Harry
On 2017-10-30 10:16 AM, Christian König wrote:
> Hi Dieter,
>
> yes Tom is right that the display team is going to take care of it.
>
> If Harry hasn'
Hi Dieter,
yes Tom is right that the display team is going to take care of it.
If Harry hasn't come up with a patch by the evening we should probably
revert the offending commit for now.
The problem the ttm patch is about is really hard to trigger and only
occurs very occasionally.
Regards
Hi Dieter,
This is due to:
commit aa7187c5c640559ebc02caa0191c0db46b55b4a6
Author: Christian König
Date: Thu Oct 26 12:00:36 2017 +0200
drm/amd/display: enable GPU VM support
Just set the bit so that DC does the hardware programming.
Signed-off-by: Christian König
Reviewed
Hello Christian,
is this for these warnings flooding my dmesg-log or do I have to open a
new ticket:
Current amd-staging-drm-next commit #7781a8c68a6a from you ;-)
[ 6588.429302] WARNING: CPU: 5 PID: 2957 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dm_services.h:132
generic_reg_update_ex+0x
