[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]
Sedat Dilek
sedat.dilek at gmail.com
Fri Jul 26 10:27:03 CEST 2013
On Fri, Jul 26, 2013 at 10:25 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote:
> On Fri, Jul 26, 2013 at 9:26 AM, Chris Wilson <chris at chris-wilson.co.uk> wrote:
>> On Fri, Jul 26, 2013 at 09:15:14AM +0200, Sedat Dilek wrote:
>>> For example: I could start my X with even doing ugly hacks like this...
>>>
>>> [ intel-ddx (git) ]
>>> ...
>>> Bool intel_uxa_create_screen_resources(ScreenPtr screen)
>>> ...
>>> #if 0
>>> if (drm_intel_gem_bo_map_gtt(bo))
>>> return FALSE;
>>> #endif
>>> ...
>>>
>>> ...with any other kernel.
>>
>> Yes. Acquiring the map there is just a bit of paranoia to ensure we
>> having the mapping into the scanout already in place in case of
>> emergencies (and so don't fail along failure paths due to resource
>> conflicts).
>>
>> Hmm, though we only started checking for map failures in 2.20.10 - which
>> would explain why going back to the older ddx masks the issue. And yes,
>> this means we do require a kernel bisect - or some passing inspiron.
>
> First confirmation...
> OK, next-20130726 shows the same symptoms!
>
> I tried diverse intel-ddx release and went back to v2.21.9... and
> searched for a version like v2.20.0 which has no checking for map
> failures...
>
> [ intel-ddx (v2.20.0) ]
> ...
> Bool intel_uxa_create_screen_resources(ScreenPtr screen)
> {
> ScrnInfoPtr scrn = xf86ScreenToScrn(screen);
> intel_screen_private *intel = intel_get_screen_private(scrn);
> dri_bo *bo = intel->front_buffer;
>
> if (!uxa_resources_init(screen))
> return FALSE;
>
> drm_intel_gem_bo_map_gtt(bo);
>
> if (intel->use_shadow) {
> intel_shadow_create(intel);
> } else {
> PixmapPtr pixmap = screen->GetScreenPixmap(screen);
> intel_set_pixmap_bo(pixmap, bo);
> intel_get_pixmap_private(pixmap)->pinned = 1;
> screen->ModifyPixmapHeader(pixmap,
> scrn->virtualX,
> scrn->virtualY,
> -1, -1,
> intel->front_pitch,
> NULL);
> scrn->displayWidth = intel->front_pitch / intel->cpp;
> }
> ...
> ... but does not start as well, so it seems to be a kernel-issue as
> assumed (2nd confirmation).
>
> X.log attached.
>
Now, really w/ promised attachment.
- S.
> - Sedat -
>
>> -Chris
>>
>> --
>> Chris Wilson, Intel Open Source Technology Centre
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Xorg.0.log
Type: application/octet-stream
Size: 96333 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/intel-gfx/attachments/20130726/11ea7863/attachment.obj>
More information about the Intel-gfx
mailing list