<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - Using 2 screens impossible again with gen3" href="https://bugs.freedesktop.org/show_bug.cgi?id=67846#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - Using 2 screens impossible again with gen3" href="https://bugs.freedesktop.org/show_bug.cgi?id=67846">bug 67846</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>Unity can only create a fbo as large as GL supports, for gen2/3 this is 2048x2048. In theory, GL was hacked to allow 4096x4096 fbo by forcing software fallbacks. That however has been broken for a few years, and even when it supposedly worked it always resulted in rendering corruption. The current breakage has been reported to hard lock the machine in some cases. ENOSPC is reported when the command buffer submitted by userspace requires more video memory than is currently available. (The available memory is reduced by control structures and pinned surfaces such as the scanout which cannot be moved, and so the request must fit in around them.) INTEL_DEBUG=all will give a break down of what exactly failed. This is a bug in the GL driver.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>