<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Framebuffer corruption when a fb which is not being scanned out gets removed"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111588#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Framebuffer corruption when a fb which is not being scanned out gets removed"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111588">bug 111588</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to Hans de Goede from <a href="show_bug.cgi?id=111588#c0">comment #0</a>)
<span class="quote">> 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</span >
Would be interesting if you could further narrow down which step (or even
sub-step of 5) exactly triggers the problem.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>