Created attachment 33192 [details] package with all debug information With Kernel 2.6.33-rc7 and xf86-video-ati GIT d9af6d, everything works perfectly - unless I try to start mozilla thunderbird or filezilla. At the moment the applications creates its window the GPU stalls (recognizable by "fade to white" effect on the screen). Attached files are dmesg (shows nothing), Xorg.0.log (shows nothing) and all files in /sys/kernel/debug/dri, machine is fully usable except for gfx card/keyboard/mouse.
More tested kernels with the same impact: 2.6.32.4, 2.6.32.8, 2.6.33-rc1, 2.6.33-rc4, 2.6.33-rc6
New tests: Kernel 2.6.33-gb979b2c (from git://git.kernel.org/pub/scm/linux/kernel/git/glisse/drm-radeon.git), ddx 6.12.191 (GIT as of 2010-03-12). No errors or warnings in dmesg, only (possibly) interesting messages in Xorg.0.log are failed to get auxch 0030 40 30 02 failed to get auxch 0031 40 30 02 failed to get auxch 0037 40 30 02 failed to get auxch 0050 40 30 02 failed to get auxch 0050 40 30 02 failed to get auxch 0050 40 30 02 failed to get auxch 0050 40 30 02
New tests: Kernel 2.6.33-gb979b2c (from git://git.kernel.org/pub/scm/linux/kernel/git/glisse/drm-radeon.git), ddx 6.12.191 (GIT as of 2010-03-12). No errors or warnings in dmesg, only (possibly) interesting messages in Xorg.0.log are failed to get auxch 0030 40 30 02 failed to get auxch 0031 40 30 02 failed to get auxch 0037 40 30 02 failed to get auxch 0050 40 30 02 failed to get auxch 0050 40 30 02 failed to get auxch 0050 40 30 02 failed to get auxch 0050 40 30 02 Procedure to get KMS: rmmod radeon; modprobe radeon modeset=1 dynpm=0 dynclks=0 Radeon module is initially loaded with modeset=0.
Created attachment 33992 [details] DRM-related kernel messages (from 2.6.33-gb979b2c)
Created attachment 33993 [details] current Xorg.0.log
The machine in question here is a Lenovo ThinkPad T500, Type 2082-7SG.
Is this still an issue with a newer version of the kernel or driver?
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.