Re: Warning at drivers/gpu/drm/drm_atomic_helper.c

Am Mittwoch, den 25.01.2017, 09:47 -0200 schrieb Fabio Estevam: > On Wed, Jan 25, 2017 at 9:30 AM, Lucas Stach wrote: > > > Kernel 4.10 just moves the fence attach to the plane state. It has > > nothing to do with the used commit function. The issue going away if you > >

Re: Warning at drivers/gpu/drm/drm_atomic_helper.c

On Wed, Jan 25, 2017 at 9:30 AM, Lucas Stach wrote: > Kernel 4.10 just moves the fence attach to the plane state. It has > nothing to do with the used commit function. The issue going away if you > change that on kernel 4.9 is a red herring. > > In any case, can you try

Re: Warning at drivers/gpu/drm/drm_atomic_helper.c

Am Mittwoch, den 25.01.2017, 09:20 -0200 schrieb Fabio Estevam: > Hi Lucas, > > On Wed, Jan 25, 2017 at 8:43 AM, Lucas Stach wrote: > > > This only fixes the issue, as with this change we never attach fences to > > the plane state. I've looked into this issue a bit and

Re: Warning at drivers/gpu/drm/drm_atomic_helper.c

Hi Lucas, On Wed, Jan 25, 2017 at 8:43 AM, Lucas Stach wrote: > This only fixes the issue, as with this change we never attach fences to > the plane state. I've looked into this issue a bit and if I'm not > mistaken, this should still be reproducible with 4.10-rc.

Re: Warning at drivers/gpu/drm/drm_atomic_helper.c

Am Sonntag, den 22.01.2017, 23:10 -0200 schrieb Fabio Estevam: > On Sun, Jan 22, 2017 at 12:26 PM, Fabio Estevam wrote: > > On Sat, Jan 21, 2017 at 2:40 PM, Fabio Estevam wrote: > >> Hi, > >> > >> Stopping kmscube application on mx6q through CTRL + C

Re: Warning at drivers/gpu/drm/drm_atomic_helper.c

On 01/23/2017 02:10 AM, Fabio Estevam wrote: > On Sun, Jan 22, 2017 at 12:26 PM, Fabio Estevam wrote: >> On Sat, Jan 21, 2017 at 2:40 PM, Fabio Estevam wrote: >>> Hi, >>> >>> Stopping kmscube application on mx6q through CTRL + C sometimes leads >>> to the

Re: Warning at drivers/gpu/drm/drm_atomic_helper.c

On Mon, Jan 23, 2017 at 09:51:55AM -0200, Fabio Estevam wrote: > On Mon, Jan 23, 2017 at 1:15 AM, Marek Vasut wrote: > > > IMHO this will no longer handle the fences correctly and you'll see > > rendering artifacts sometimes. > > Ok, for 4.9.x stable we cannot apply your

Re: Warning at drivers/gpu/drm/drm_atomic_helper.c

On Mon, Jan 23, 2017 at 1:15 AM, Marek Vasut wrote: > IMHO this will no longer handle the fences correctly and you'll see > rendering artifacts sometimes. Ok, for 4.9.x stable we cannot apply your 782ea2a493ba90800 ("drm/imx: Switch to drm_fb_cma_prepare_fb() helper") as it

Re: Warning at drivers/gpu/drm/drm_atomic_helper.c

On Sun, Jan 22, 2017 at 11:10:06PM -0200, Fabio Estevam wrote: > On Sun, Jan 22, 2017 at 12:26 PM, Fabio Estevam wrote: > > On Sat, Jan 21, 2017 at 2:40 PM, Fabio Estevam wrote: > >> Hi, > >> > >> Stopping kmscube application on mx6q through CTRL + C

Re: Warning at drivers/gpu/drm/drm_atomic_helper.c

On Sun, Jan 22, 2017 at 12:26 PM, Fabio Estevam wrote: > On Sat, Jan 21, 2017 at 2:40 PM, Fabio Estevam wrote: >> Hi, >> >> Stopping kmscube application on mx6q through CTRL + C sometimes leads >> to the following kernel warning: >> >> ^C[ 3939.785516]

Re: Warning at drivers/gpu/drm/drm_atomic_helper.c

On Sat, Jan 21, 2017 at 2:40 PM, Fabio Estevam wrote: > Hi, > > Stopping kmscube application on mx6q through CTRL + C sometimes leads > to the following kernel warning: > > ^C[ 3939.785516] [ cut here ] > [ 3939.790313] WARNING: CPU: 1 PID: 67 at >

Warning at drivers/gpu/drm/drm_atomic_helper.c

Hi, Stopping kmscube application on mx6q through CTRL + C sometimes leads to the following kernel warning: ^C[ 3939.785516] [ cut here ] [ 3939.790313] WARNING: CPU: 1 PID: 67 at drivers/gpu/drm/drm_atomic_helper.c:1032 drm_atomic_helper_wait_for_fences+0xe4/0x104 [