<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [bisected] Console garbled on MacBookPro's" href="https://bugs.freedesktop.org/show_bug.cgi?id=108264#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [bisected] Console garbled on MacBookPro's" href="https://bugs.freedesktop.org/show_bug.cgi?id=108264">bug 108264</a> from <a class="email" href="mailto:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> Imre Deak</a> <pre>(In reply to Imre Deak from <a href="show_bug.cgi?id=108264#c2">comment #2</a>) > Looks really like an FB corruption problem reported by Mika Westerberg. He > bisected it to > > commit 011f22eb545a35f972036bb6a245c95c2e7e15a0 > Author: Hans de Goede <<a href="mailto:j.w.r.degoede@gmail.com">j.w.r.degoede@gmail.com</a>> > Date: Fri Apr 20 11:59:33 2018 +0200 > > drm/i915: Do NOT skip the first 4k of stolen memory for pre-allocated > buffers v2 > > Later Ville spotted in dmesg that it's caused by an incorrect assumption by > the initial FB allocation code that an active FB during booting is always in > stolen memory. In this case it's not and as a result the driver won't > reserve the actual backing pages which will be later corrupted by whatever > happens to allocate these pages. > > Solution is to throw away the active FB in this case and allocate a new one. > I'm planning to follow up with a patch for that. ronald, oops, sorry didn't notice that you already bisected the same commit. So this is definitely the same problem then.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>