<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)" href="https://bugs.freedesktop.org/show_bug.cgi?id=55692#c40">Comment # 40</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)" href="https://bugs.freedesktop.org/show_bug.cgi?id=55692">bug 55692</a> from <a class="email" href="mailto:alexandre.f.demers@gmail.com" title="Alexandre Demers <alexandre.f.demers@gmail.com>"> Alexandre Demers</a> <pre>(In reply to <a href="show_bug.cgi?id=55692#c36">comment #36</a>) > (In reply to <a href="show_bug.cgi?id=55692#c35">comment #35</a>) > > I've been playing a bit (booting and restarting with kernel 3.7-rc1) and > > strangely, what I see is very similar to what I was observing in <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Latest radeon dri driver on HD6950 with GRUB set gfxpayload=$linux_gfx_mode put the display in a flickering state" href="show_bug.cgi?id=43655">bug 43655</a>. > > It was then merged with <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - Radeon HD 6450 (NI CAICOS) screen corruption on boot" href="show_bug.cgi?id=42373">bug 42373</a>. At the time, <a href="attachment.cgi?id=64759" name="attach_64759" title="Fixup mc programing">attachment 64759</a> <a href="attachment.cgi?id=64759&action=edit" title="Fixup mc programing">[details]</a> <a href='page.cgi?id=splinter.html&bug=55692&attachment=64759'>[review]</a> [review] > > [review] was proposed and a similar patch ended up being commited that fixed > > <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Latest radeon dri driver on HD6950 with GRUB set gfxpayload=$linux_gfx_mode put the display in a flickering state" href="show_bug.cgi?id=43655">bug 43655</a> for me (but it never fixed <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - Radeon HD 6450 (NI CAICOS) screen corruption on boot" href="show_bug.cgi?id=42373">bug 42373</a> on NI CAICOS). > > > > I'll try the workaround used at the time to see if it is really related to > > <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Latest radeon dri driver on HD6950 with GRUB set gfxpayload=$linux_gfx_mode put the display in a flickering state" href="show_bug.cgi?id=43655">bug 43655</a> (comments 8 and 10) and I'll begin bisecting kernel right after. > > I think what you really want for your caicos is this patch: > <a href="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit">http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit</a>; > h=62444b7462a2b98bc78d68736c03a7c4e66ba7e2 kernel bisected. Here is the culprit commit from what I see here: 62444b7462a2b98bc78d68736c03a7c4e66ba7e2 is the first bad commit commit 62444b7462a2b98bc78d68736c03a7c4e66ba7e2 Author: Alex Deucher <<a href="mailto:alexander.deucher@amd.com">alexander.deucher@amd.com</a>> Date: Wed Aug 15 17:18:42 2012 -0400 drm/radeon: properly handle mc_stop/mc_resume on evergreen+ (v2) - Stop the displays from accessing the FB - Block CPU access - Turn off MC client access This should fix issues some users have seen, especially with UEFI, when changing the MC FB location that result in hangs or display corruption. v2: fix crtc enabled check noticed by Luca Tettamanti Signed-off-by: Alex Deucher <<a href="mailto:alexander.deucher@amd.com">alexander.deucher@amd.com</a>> :040000 040000 3e0d33c9b4eda29ced814fe9a863efe63e53f14c 4932561607b160734ec1eade927a9fe18c9f3f1b M drivers So it may not be the same bug I'm hitting as Serkan is. Where should I track this faulty commit/bug? In the NI CAICOS bug or in a new one?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>