After constant regressions, I thought I would post this.
Good is kernel 22.214.171.124 where I get glxgears frame rates of ~300fps. This is all I can expect from a slow PCI bus.
Bad is kenel 126.96.36.199 where the glxgears frame rates are a little slower, maybe 250fps and quitting X fails. Logging out of my desktop environment, Ctrl+Alt+F2, Ctrl+Alt+Backspace, chvt commands, all of these freeze my system.
Reallybad is kernel 188.8.131.52 where glxgears has no consistent frame rate. It jumps around between 5fps and 60fps and all graphical programs are incredibly slow. This is in addition to the zapping issue described above.
I am not sure why 184.108.40.206 is sometimes bad and sometimes reallybad. It might have to do with what USB devices are connected when it boots up.
Please do not tell me to upgrade my userspace programs. I have tried every combination of xorg-server, mesa, xf86-video-ati and libdrm and none of them have any effect. The kernel is the ONLY package that changes how bad this bug is. Also please do not tell me to upgrade the kernel unless you are very sure that the version you are suggesting fixes this bug and you can tell me why it fixes it.
I am not looking for a kernel that works. I KNOW which kernel works. I am trying to understand WHY it is the only one that works and hopefully help you fix this. Thank-you very much.
Created attachment 36383 [details]
Created attachment 36384 [details]
Created attachment 36385 [details]
Created attachment 36386 [details]
Created attachment 36387 [details]
Created attachment 36388 [details]
Created attachment 36389 [details]
Created attachment 36390 [details]
Created attachment 36391 [details]
Created attachment 36392 [details]
Created attachment 36393 [details]
Comment on attachment 36393 [details]
2.6.34 is even worse. I will continue to add pastes for new kernels as they come out. I would prefer not to go back and do 2.6.32 because I remember that being just like 220.127.116.11 and compiling it would be a huge pain.
Replacing these will not change a thing but in case you're wondering:
Also my distro patches ONLY the following directories:
Any chance you can use git to bisect what kernel commit is the problematic one?
That's a good idea, if a lengthy one.
Is there a way to see a sequential list of commits in one of the "main" branches? And is there a way to compile only the radeon module if I'm moving from one kernel to a very similar one?
You can browse commits in via the git web interface:
You can also narrow the bisect range by just bisecting drm commits, e.g.,
git bisect start -- drivers/gpu/drm
Although this won't help if the problematic commit is not drm related.
Created attachment 38032 [details]
Created attachment 38033 [details]
Created attachment 38034 [details]
18.104.22.168 is acting the way 2.6.33 did. Slow graphical apps, inconsistent glxgears frame rate and having to use Alt + SysRq + REISUB every time I log out of X.
This bug largely goes away if I use kernels 2.6.37 and 2.6.38 with the Gallium Radeon/DRI driver. In fact the glxgears framerates I get that way are slightly better. Some things to note are that the framerates become awful again if I turn "EXAPixmaps" "off" and that I still have trouble logging out of X. This is surely a topic for another bug.
Thanks for all the work you've been doing!