On Tue, 2008-10-21 at 00:11 +0200, Rémi Cardona wrote: > Jesse Barnes a écrit : > >> And if I start a GEM kernel, X doesn't even start. See my previous post > >> on intel-gfx. > > > > This is the "failed to pin back buffer" error? > > I would say yes. dmesg says : > > [drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty > [drm:i915_gem_object_pin] *ERROR* Failure to bind: > -12<3>[drm:i915_gem_idle] *ERROR* hardware wedged > [drm:i915_gem_entervt_ioctl] *ERROR* Reenabling wedged hardware, good luck > [drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty > [drm:i915_gem_object_pin] *ERROR* Failure to bind: > -12<3>[drm:i915_gem_idle] *ERROR* hardware wedged > [drm:i915_gem_entervt_ioctl] *ERROR* Reenabling wedged hardware, good luck > [drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty > [drm:i915_gem_object_pin] *ERROR* Failure to bind: > -12<3>[drm:i915_gem_idle] *ERROR* hardware wedged > > while Xorg.0.log says : > > (II) intel(0): xf86BindGARTMemory: bind key 5 at 0x03bff000 (pgoffset 15359) > (EE) intel(0): Failed to pin back buffer: Cannot allocate memory > > Fatal server error: > Couldn't bind memory for BO back buffer
The Legacy3D FALSE option may help you bring the GEM environment up in a limited-aperture-space situation. On our end, we should also cut back the EXA offscreen space in the presence of limited aperture to increase the chance of success. Also, we could use Legacy3D as a signal that it's safe to resize the framebuffer, and actually do that. -- Eric Anholt [EMAIL PROTECTED] [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
_______________________________________________ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
