<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - SIGSEGV "get_fb: failed to add fb" / sna_block_handler" href="https://bugs.freedesktop.org/show_bug.cgi?id=91467#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - SIGSEGV "get_fb: failed to add fb" / sna_block_handler" href="https://bugs.freedesktop.org/show_bug.cgi?id=91467">bug 91467</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>errno=22 is EINVAL, so the kernel thought the handle was unsuitable for a framebuffer. get_fb: failed to add fb: 1920x1080 depth=24, bpp=32, pitch=7680: 22 Looks superficially fine. Y-tiling should have been filtered out before this point, and you would have to use drm.debug=7 to find out why the kernel rejected it. The really odd part is that the error messages seem to be from the sna_present_unflip() path - that is the only path that I think can trigger that pattern of error messages - and it should be nigh impossible to fail there given the ScreenPixmap was previously attached.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>