Op 08-09-15 om 09:31 schreef Bjørn Mork:
> Just for the record: I still get these quite often on resuming from
> suspend-to-ram. But I can't reliably provoke them for some reason, so
> the exact trigger mechanism is unknown. Related to timing issues caused
> by other devices, maybe? Or some odd
Just for the record: I still get these quite often on resuming from
suspend-to-ram. But I can't reliably provoke them for some reason, so
the exact trigger mechanism is unknown. Related to timing issues caused
by other devices, maybe? Or some odd Lenovo firmware thingy?
Does of course not
Maarten Lankhorst writes:
> Op 08-09-15 om 09:31 schreef Bjørn Mork:
>> Just for the record: I still get these quite often on resuming from
>> suspend-to-ram. But I can't reliably provoke them for some reason, so
>> the exact trigger mechanism is unknown.
Hello, I see that I consistently get the warning below on v4.2-rc8. I
believe you already fixed this a long time ago by commit c0165304e10f
(drm/i915: Only enable cursor if it can be enabled.), which I assume is
a stable candidate for v4.2.y.
But wouldn't it look better if you managed to squeeze
Hey,
Op 25-08-15 om 09:45 schreef Bjørn Mork:
Hello, I see that I consistently get the warning below on v4.2-rc8. I
believe you already fixed this a long time ago by commit c0165304e10f
(drm/i915: Only enable cursor if it can be enabled.), which I assume is
a stable candidate for v4.2.y.
Maarten Lankhorst maarten.lankho...@linux.intel.com writes:
Hey,
Op 25-08-15 om 09:45 schreef Bjørn Mork:
Hello, I see that I consistently get the warning below on v4.2-rc8. I
believe you already fixed this a long time ago by commit c0165304e10f
(drm/i915: Only enable cursor if it can be