[Bug 111588] Framebuffer corruption when a fb which is not being scanned out gets removed

2019-11-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111588 Martin Peres changed: What|Removed |Added Resolution|--- |MOVED Status|NEW

[Bug 111588] Framebuffer corruption when a fb which is not being scanned out gets removed

2019-09-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111588 --- Comment #2 from Michel Dänzer --- (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_add

[Bug 111588] Framebuffer corruption when a fb which is not being scanned out gets removed

2019-09-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111588 --- Comment #1 from Hans de Goede --- I just realized I left out one bit of info which might be useful, to debug this I added the following change to the kernel: diff --git a/drivers/gpu/drm/drm_framebuffer.c b/drivers/gpu/drm/drm_framebuffer.c

[Bug 111588] Framebuffer corruption when a fb which is not being scanned out gets removed

2019-09-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111588 Bug ID: 111588 Summary: Framebuffer corruption when a fb which is not being scanned out gets removed Product: DRI Version: DRI git Hardware: Other OS: All