<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#c41">Comment # 41</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:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> Christian König</a> <pre>(In reply to <a href="show_bug.cgi?id=55692#c37">comment #37</a>) > Created <a href="attachment.cgi?id=68728" name="attach_68728" title="dmesg.3.7-rc1 with testpatch with mesa-git">attachment 68728</a> <a href="attachment.cgi?id=68728&action=edit" title="dmesg.3.7-rc1 with testpatch with mesa-git">[details]</a> > dmesg.3.7-rc1 with testpatch with mesa-git > > I removed gdm and installed slim as login manager. Also installed cinnamon > as a replacement for gnome and it works fine the first round with linus git > with the test patch and mesa git. Restarted slim and logged in again and > there were some font corruptions, i restarted cinnamon and they were gone. I > tried google maps with webgl enabled and it was working fine. > > After that i edited my .xinitrc to startup gnome, restarted slim and logged > in but it failed and got the error window saying oh no something has gone > wrong and a log out button. I checked dmesg at that point and saw the ttm > gart memory error. i switched back to cinnamon logged in and got the same > font corruptions, restarting cinnamon fixed them. Thanks allot for your additional testing, as I suspected we are really facing two problems here: 1. The new gnome/gdm versions seem to trigger an out of memory situation in the GART memory area. That's probably because some miscalculation or memory leak or something like this and should be handled as a separate bug. BTW: You can take a look at the current memory allocations with: sudo cat /sys/kernel/debug/dri/0/radeon_gtt_mm and sudo cat /sys/kernel/debug/dri/0/radeon_vram_mm 2. Properly updating the page table asynchronously somehow fails under high memory pressure. I will try to look into problem 2 first, since that got added with my patch. But problem number 1 is as equally as bad. I don't think we just spool up allot of drawing operations like Jerome suspected, cause in this case TTM would just block on previous render operations to complete. It looks more like we are submitting a single draw operation with multiple ~16MB chunks of memory that is so big that it just won't fit into the GART memory altogether.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>