<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Console screen corruption" href="https://bugs.freedesktop.org/show_bug.cgi?id=107951#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Console screen corruption" href="https://bugs.freedesktop.org/show_bug.cgi?id=107951">bug 107951</a> from <a class="email" href="mailto:vadym.shovkoplias@globallogic.com" title="vadym <vadym.shovkoplias@globallogic.com>"> vadym</a> <pre>(In reply to Hans de Goede from <a href="show_bug.cgi?id=107951#c10">comment #10</a>) > Can someone who is seeing this try to revert > 011f22eb545a35f972036bb6a245c95c2e7e15a0 (drm/i915: Do NOT skip the first 4k > of stolen memory for pre-allocated buffers v2) ? > > That will likely fix this. If that indeed fixes it then we should really > only use the Video BIOS / GOP driver framebuffer when taking over the > initial mode and, *if it starts within the first 4k*, use a new framebuffer > for fbdev emulation instead of inheriting the BIOS / GOP driver framebuffer > there. > > This will allow us to keep the initial framebuffer for flickerfree boot, > while selecting another framebuffer which honors the > WaSkipStolenMemoryFirstPage:bdw+ > workaround for fbcon, which should fix the fbcon corruption. Hi Hans, I'm able to reproduce this issue. I've just rebuild kernel with 011f22eb545a35f972036bb6a245c95c2e7e15a0 patch reverted but it didn't help. Issue is still reproducible.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>