Created attachment 42316 [details] GPU Lockup log System: various kernel from 2.6.33 to 2.6.38-pre1 Driver: xf86-video-ati-6.13.2 X-Server: xorg-server-1.9.3 GPU: Radeon 9000 mobility on a GoBook 3 With EXA acceleration enabled (radeon kernel module loaded, irrespectively of the modeset options) there are multiple issues, like: - xvideo is slow, often skips a frame and shows the previous one - GPU lockups on heavy activity (like flash based sited) - -vo gl_nosw in mplayer works fine but often locks up on exit I already have agp_mode=-1 in the kernel modeline. Using "AccelMethod" "XAA" with modeset=0 works fine with everything except xvideo with 16bpp, it only shows a blue screen (24bpp is OK) Attached is a typical lockup log (it repeats and I need to reboot with SysRq). Of course I can give any other log or information needed to solve the issue
(In reply to comment #1) > Driver: xf86-video-ati-6.13.2 Does a newer Git snapshot work better by any chance? > I already have agp_mode=-1 in the kernel modeline. That only has an effect with KMS (and is known to seriously degrade performance then). Are you using the corresponding option in xorg.conf for UMS? Maybe attach the full xorg.conf file and Xorg.0.log files for KMS and UMS to clarify this and other potential questions.
Created attachment 42359 [details] Working Xorg.conf (only without kms) This works putting X in XAA mode, and it works fine, no signs of instability. The AGPMode=1 is needed because this machine is known to need it! In fact in 4x AGP mode there is severe display corruption
Created attachment 42360 [details] Log for working configuration (XAA in ums) Log for working configuration (see conf above)
Created attachment 42361 [details] Configuration using EXA (unstable with both kms and ums) In fact the only difference is the acceleration mode option missing
Created attachment 42362 [details] Log for EXA using ums (unstable!)
Created attachment 42363 [details] Log for EXA using kms (unstable!)
I posted the relevant configurations and logs as requested. There is apparently no difference in stability between ums and kms. The gobook iii is known to require limiting the AGP rate to 1x (the module option was set trying to stabilize the thing), btw, and the input devices need to be manually configurated (because there is a semtech touch in there and it confuses things...) I tried with the driver git head just before submitting the bug, nothing seemed to change.
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.