[Bug 111588] Framebuffer corruption when a fb which is not being scanned out gets removed
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Sep 9 16:14:58 UTC 2019
https://bugs.freedesktop.org/show_bug.cgi?id=111588
--- Comment #2 from Michel Dänzer <michel at daenzer.net> ---
(In reply to Hans de Goede from comment #0)
> 5) Plymouth internally calls src/plugins/renderers/drm/plugin.c:
> ply_renderer_buffer_free() this does:
> drmModeRmFB(...);
> munmap (buffer->map_address, buffer->map_size);
> destroy_dumb_buffer_request.handle = buffer->handle;
> drmIoctl (fd, DRM_IOCTL_MODE_DESTROY_DUMB, &destroy_dumb_buffer_request);
> Followed by calling close() on the fd.
> 6) Plymouth exits
> 7) 5 and/or 6 cause the gdm framebuffer being all messed up, it looks like a
> wrong pitch or tiling setting
Would be interesting if you could further narrow down which step (or even
sub-step of 5) exactly triggers the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20190909/54329936/attachment.html>
More information about the dri-devel
mailing list