AMD Linux
It is definitely an option, and it is supported on older GPUs with a dedicated 2D acceleration block, we just didn't write any R600 code for that option
The 3D engine is not a particularly good match for the common XAA functions, and modern apps seem to make more use of the operations offered by EXA. Since we already use the 3D engine for most of the EXA functions, and since 6xx/7xx only have a 3D engine, we only implemented EXA and not XAA for those GPU generations. There was some discussion about whether we should implement XAA later, but I don't know what the right answer is there.
Alex mentioned that turning off Composite (Option "NoEXAComposite" in the Device section of your conf file) frequently eliminated the corruption.
monraaf, could you try that option if you have not already done so ?
Senior Member
Ok with:Originally Posted by bridgman
I get normal readable fonts, however on some places there are lines above them. Adding this option gets rid of these lines.Code:Option "EXANoComposite" "true"
And it looks like the X server is stable now.Code:Option "MigrationHeuristic" "greedy"
Last edited by monraaf; 01-08-2009 at 11:17 PM. Reason: found the right option and another.
AMD Linux
Great. It's possible that the MigrationHeuristic option is completely disabling acceleration, but I'm not sure about the current code. Do you see a big performance drop when you set it to "greedy" ?
Senior Member
Whoops, I spoke to soon. I just had another lock-up, well It's not completely stable yet but definitively more stable. One guaranteed way to lock-up the system seems to play a movie with mplayer (Xv output) and then enter and leave full screen mode.
Regarding the MigrationHeuristic option I don't see any performance differences.
AMD Linux
Interesting; so the option is affecting stability but not totally disabling acceleration. That's probably useful -- thanks !
Senior Member
Just an update for those using Ubuntu Jaunty's stock kernel. This bug was fixed for both i386 and amd64 kernels in a recent update: https://bugs.launchpad.net/ubuntu/+s...ux/+bug/312721So I found that the drm.ko kernel module I built isn't loading properly. It might have something to do with drm being built statically into stock 2.6.28 kernels:
There was also an X server update for Jaunty today (1.5.99.3 -> 1.5.99.901). I'm going to rebuild DRM, Mesa, and radeonhd and see if anything's improved for the RS780. Will report back.
Senior Member
The updated X server didn't help :\
The system still locks up if I move a simple terminal window around too much, even with the EXANoComposite and MigrationHeuristics options. (I also have AIGLX and the composite extension disabled)
/var/log/messages shows:
And drm just goes on and on generating the last two messages with different numbers every few seconds. Xorg.log doesn't have anything out of the ordinary in it.Code:Jan 19 20:54:39 somehost kernel: [ 23.908796] [drm] Initialized drm 1.1.0 20060810 Jan 19 20:54:39 somehost kernel: [ 23.955318] pci 0000:01:05.0: BAR 0: can't reserve mem region [0xd0000000-0xdfffffff] Jan 19 20:54:39 somehost kernel: [ 23.956215] pci 0000:01:05.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 Jan 19 20:54:39 somehost kernel: [ 23.956429] [drm] Initialized radeon 1.29.0 20080613 on minor 0 Jan 19 20:54:39 somehost kernel: [ 23.956536] [drm] Used old pci detect: framebuffer loaded Jan 19 20:54:39 somehost kernel: [ 24.151804] [drm] Setting GART location based on new memory map Jan 19 20:54:39 somehost kernel: [ 24.167188] [drm] Loading RS780 CP Microcode Jan 19 20:54:39 somehost kernel: [ 24.168187] [drm] Loading RS780 PFP Microcode Jan 19 20:54:39 somehost kernel: [ 24.183350] [drm] Resetting GPU Jan 19 20:54:39 somehost kernel: [ 24.183408] [drm] writeback test succeeded in 1 usecs Jan 19 20:54:40 somehost kernel: [ 24.476944] [drm] dwords:3632 Jan 19 20:54:40 somehost kernel: [ 24.476950] [drm] offset 0xe0222000
If I can do anything else to generate a more useful "bug report", let me know.
Last edited by DanL; 01-20-2009 at 11:18 AM.
AMD Linux
Just to be sure, is it only the "dwords" and "offset" messages which are repeating ?
Senior Member
Yes, although occassionally strange "garbage" shows up
Code:Jan 19 20:55:26 somehost kernel: [ 70.496037] [drm] offset 0xe0272000 Jan 19 20:55:26 somehost kernel: [ 70.496092] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: [ 70.496044444444444 444444444444444 444444444444444455555 5505555555 5555 5555 555555555555555555555555555555550504816] [drm] offset 0xe0372000 Jan 19 20:55:26 somehost kernel: [ 70.504870] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: [ 70.504872] [drm] offset 0xe0382000 Jan 19 20:55:26 somehost kernel: [ 70.504928] [drm] 55555 55555555 555555555555555555507555555555085555 5555555 555555555555555555555555 5555 555555555555555555555 5555555555555555555515555555555555 555555555555555555555555555555555555555555 555555555555 5555555555555555555555555555255555555555 5555 5555 555555555 555555 555555555 5 55555555555555555555555555555555555555 5555 553555 5555 5555553536901] [drm] offset 0xe0252000 Jan 19 20:55:26 somehost kernel: [ 70.536955] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: [ 70.536958] [drm] offset 0xe0262000 Jan 19 20:55:26 somehost kernel: [ 70.537012] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: [ 5555555555555 555555555555555555555 55555555 555555555415555555555555555 555555555555555555555555555555555555 5555555555555555555555 55555555555555555555555555555 55555555555555555555555555555 55555 555555 555 55555555555555555555555555555555555555555 56555555555555555555555555555555 55555555555555555555555555 5555555 5555 555555 5555555 5575321] [drm] offset 0xe0342000 Jan 19 20:55:26 somehost kernel: [ 70.575377] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: [ 70.575379] [drm] offset 0xe0352000 Jan 19 20:55:26 somehost kernel: [ 70.5754345557565555555555555555 55555555555555555555555555 5555 55555555555555555555555555555555555555 555555585555555555555555555555555555 55555555555 5555 5555 5 555555555555555555 5555555555555 55555555 555555555555556666666666666 6666666666666066 66666666666666666 66666 66666666666 666666666666666606 66666666666666666666666616666 6666 66661613109] [drm] offset 0xe0242000 Jan 19 20:55:26 somehost kernel: [ 70.613190] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: [ 70.613193] [drm] offset 0xe0252000 Jan 19 20:55:26 somehost kernel: [ 666 6666666166666666666666666666666666 6666666666666666617666666666666666666666666666 6666 666666 6666666666666666666666666666666666666666666666666666666626 66666666666666666 666666666666666666666666666666666666666666666666666 6666 6666666666666 666666466666666666666666666666666666666 666666666 6666666 666666666666666 66666664666666 665650592] [drm] offset 0xe0332000 Jan 19 20:55:26 somehost kernel: [ 70.650647] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: [ 70.650650] [drm] offset 0xe03466666666666666666 6665266666 666666656666666666 66666666666666666666666666666 666666 66666666666666666666666666666 66666 666666666 666666666666666666666666 66 666666 6666666666666666666 6666 66666666666 666666666666676666666 6666666 66666666866 666666666 666666666666666666666666 6666666 666666666 6666666666666686666666666666666666666668688662] [drm] offset 0xe0232000 Jan 19 20:55:26 somehost kernel: [ 70.688714] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: [ 70.688717666886666 66666666666 6666 66666666666666 6666 6666666666666666666666666 6666666666666666666666666666 696666666 6666666 6666666666666666666777 777777 777707777777 77777777777777777777777777777777777770777777 7777 77777777777777777777777 777777777777777777777777 777777777777777 777777 7 7777777721 77 7777777777777777777 77777777777777772724904] [drm] offset 0xe0312000 Jan 19 20:55:26 somehost kernel: [ 70.724958] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: [ 77777 7 7777777777777777777777777777777777777777777777777777777777777777777777777777777777327777 7777 77777777777777777777777 7777777777777777 777777 7777 77777 77777777777777 777 77477777777777777 7777777777777777777777777 777777 7777777777777777777 7777777777777777777777 777775777777 77777777777 7777 777777777777777 77777777776760565] [drm] offset 0xe0202000 Jan 19 20:55:26 somehost kernel: [ 70.760620] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: 7607777777777777 7777777777777777 777777777 7777777777777 777777 77777777777777777 7677777 7777777777777 777777 7777777777777 7777 7777 7777777777777777777777777 7777777777 7777777777777777 7 777777777777777777 77 777777777777777777777 777777777777777 7777 7 777777 7777777 77777777777777777777777777777777777 77 77777777777777777779795502] [drm] offset 0xe02f2000 Jan 19 20:55:26 somehost kernel: [ 70.795555] [drm] dwords:364777777777777 7777777777777777777 77 77777777777777 77777 88888888888888888 88888888888888888888888888888888888888 8888 888 8888888888888888888 888888888888888888888888888888888888888888888888888888888 888888888888888888888 8888888888288888 888888 888888888 8888 88888888888 8888888888888888888888 8 888888888 8888888888888888888882828894] [drm] offset 0xe03e2000 Jan 19 20:55:26 somehost kernel: [ 70.828947] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: [ 70.828950] [drm] offset 0xe03f2000 Jan 19 20:55:26 somehost kernel: [ 70.829004] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: [ 70.829007] [drm] offset 0xe0202000 Jan 19 20:55:26 somehost kernel: [ 70.829062] [drm] dwords:3648 Jan 19 20:55:26 somehost kernel: [ 70.829064] [drm] offset 0xe0222000
Senior Member
Did you use NoEXAComposite or EXANoComposite? I think only the latter is a valid option. You should check out your Xorg log file if the options you use are accepted. Also EXA has a man page with some more options you can try out. Just type man exa.
Posting Permissions
Reply With Quote