On 08/29/2012 10:11 AM, Hausensteiner Keg wrote: > On 27/08/12 21:04, Hausensteiner Keg wrote: >> On 27/08/12 20:29, Jerome Glisse wrote: >>> On Sun, Aug 26, 2012 at 8:34 PM, Hausensteiner Keg <skitch...@apache.org> >>> wrote: >>>> ... >>> Does patch >>> >>> http://people.freedesktop.org/~glisse/0001-drm-radeon-extra-type-safe-for-fence-emission.patch >>> >>> Helps ? >> >> Thanks Jerome. Will try patch tonight or tomorrow morning. >> >> How do I check whether the radeon is on an AGP bus? >> The lspci output does not mention AGP; line for video controller is: >> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI >> M56P [Radeon Mobility >> X1600] >> The "lshw" output also shows no signs of AGP. >> >> The dmesg output contains "[0.909546] Linux agpgart interface v0.103" but >> otherwise no mention of >> "agp" or "AGP". >> >> By the way: tested the 3.5.3 release made today : still corrupt graphics. >> And the v3.5 release >> (which was oddly working) also showed the same corrupt graphics as soon as I >> forced a rebuild of >> the initrd - maybe an older radeon module somehow ended up in the initrd >> built by "make-kpkg >> --initrd". >> > > Patch 0001-drm-radeon-extra-type-safe-for-fence-emission applies cleanly to > both 3.5.3 and > 3.6.0-rc3, but makes no difference in either case. > > I've done some more bisecting, and the full sequence is: > > * Prior to commit bb635567 ("convert fence to uint64_t v4") all works fine. > * Commit bb635567 causes system to freeze on Plymouth startup. > * The following commit (3b7a2b24, "rework fence handling, drop fence list > v7") causes Plymouth to > work again, but causes graphics corruption on greeter screen. Pressing > ctrl-alt-f2 immediately > displays a virtual console correctly, and the system is useable. However any > attempt to use the > mouse on the greeter screen triggers further graphics corruption, and system > appears to hang. > > This situation continues up to and including 3.5.3. > > In the 3.6 dev cycle, the corruption issue continues up to 9c19415c. However > the following commit, > 876dc9f3 "remove radeon_fence_create" instead causes the screen to go black > immediately after > plymouth completes (ie when greeter screen is expected), and ctrl-alt-f2 has > no effect. > > FWIW, looks like two separate issues to me, with 876dc9f3 masking the earlier > one..
Hi, we are having the some issue with other radeon cards. you can check bug 54129 (and the one linked there). I have no hangs (yet), just big screen corruptions. I have not found the 2nd issue at 876dc9f3. but I will check as soon as I can. For me v3.6-rc3 is the same as 3b7a2b24. I my case switching off KMS, makes the corruption disappear (but I loose XV). To begin with, it would be nice if we could sort out if the problem comes from bb635567 or 3b7a2b24, but I have the same black screen after the penguin logo (with Ctrl-Alt-Del working). Andrea _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
