On 11 May 2015 at 12:35, Daniel Vetter <daniel@xxxxxxxx> wrote:
> On Mon, May 11, 2015 at 10:19:58AM +0200, Daniel Martin wrote:
>> Just tested
>> b5a0fd0 drm-intel-nightly: 2015y-05m-11d-06h-03m-04s UTC
>> integration manifest
>>
>> The problem still exists.
>
> Yeah that one is busted unfortunately. I've just pushed out a new -nightly
> with an updated patch from Maarten:
>
> commit c363376d3d5586c1e99f92969a7a7baf179206d7
> Author: Maarten Lankhorst <maarten.lankhorst@xxxxxxxxxxxxxxx>
> Date: Mon May 11 10:45:15 2015 +0200
>
> drm/i915: Always keep crtc_state->active in sync with enable
>
> How does that one fare?
21331f4 drm-intel-nightly: 2015y-05m-11d-13h-27m-46s UTC
And no changes:
- at boot:
WARNING: CPU: 0 PID: 48 at drivers/gpu/drm/drm_irq.c:1159
drm_wait_one_vblank+0x168/0x180 [drm]()
vblank not available on crtc 0, ret=-22
- when plugging the connector:
WARNING: CPU: 0 PID: 40 at
drivers/gpu/drm/i915/intel_display.c:12011
intel_modeset_check_state+0x238/0xda0 [i915]()
active encoder's pipe doesn't match(expected 1, found 0)
(... 3 times, followed by ...)
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [<ffffffffa02c2ac5>] drm_crtc_index+0x5/0x50 [drm]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
