2017-04-05 12:05 GMT+02:00 Philipp Zabel :
> On Tue, 2017-04-04 at 14:50 +0200, Christian Gmeiner wrote:
> [...]
>> > Is this on a non-plus i.MX6? Maybe are missing the LDB DI clock glitch
>> > fixes (commits 5d283b083800, 03d576f202e8, and f13abeff2cde)?
>>
>> Yes it is a non-plus i.MX6D and all t
On Tue, 2017-04-04 at 14:50 +0200, Christian Gmeiner wrote:
[...]
> > Is this on a non-plus i.MX6? Maybe are missing the LDB DI clock glitch
> > fixes (commits 5d283b083800, 03d576f202e8, and f13abeff2cde)?
>
> Yes it is a non-plus i.MX6D and all those three patches are included in
> 4.9.20 (which
2017-04-04 10:14 GMT+02:00 Philipp Zabel :
> Hi Christian,
>
> On Mon, 2017-04-03 at 17:16 +0200, Christian Gmeiner wrote:
>> 2017-03-31 14:57 GMT+02:00 Philipp Zabel :
>> > Hi Christian,
>> >
>> > On Fri, 2017-03-31 at 12:44 +0200, Christian Gmeiner wrote:
>> >> Hi
>> >>
>> >> I get this from time
Hi Christian,
On Mon, 2017-04-03 at 17:16 +0200, Christian Gmeiner wrote:
> 2017-03-31 14:57 GMT+02:00 Philipp Zabel :
> > Hi Christian,
> >
> > On Fri, 2017-03-31 at 12:44 +0200, Christian Gmeiner wrote:
> >> Hi
> >>
> >> I get this from time to time on a 4.9.17 kernel:
> >>
> >> [3.353387] -
2017-03-31 14:57 GMT+02:00 Philipp Zabel :
> Hi Christian,
>
> On Fri, 2017-03-31 at 12:44 +0200, Christian Gmeiner wrote:
>> Hi
>>
>> I get this from time to time on a 4.9.17 kernel:
>>
>> [3.353387] [ cut here ]
>> [3.353408] WARNING: CPU: 0 PID: 1 at
>> drivers/gp
Hi Christian,
On Fri, 2017-03-31 at 12:44 +0200, Christian Gmeiner wrote:
> Hi
>
> I get this from time to time on a 4.9.17 kernel:
>
> [3.353387] [ cut here ]
> [3.353408] WARNING: CPU: 0 PID: 1 at
> drivers/gpu/drm/drm_atomic_helper.c:1140
> drm_atomic_helper_wa
Hi
I get this from time to time on a 4.9.17 kernel:
[3.353387] [ cut here ]
[3.353408] WARNING: CPU: 0 PID: 1 at
drivers/gpu/drm/drm_atomic_helper.c:1140
drm_atomic_helper_wait_for_vblanks+0x240/0x244
[3.353412] [CRTC:24] vblank wait timed out
[3.353420] Mo