Bug 34123

Summary: Radeon with KMS enabled causes X to start flickering ('GPU losing synchronisation')
Product: xorg Reporter: gijs.hillenius <gijs.hillenius>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: major    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg log,
none
Dmesg
none
attached is a copy of my vbios
none
possible fix none

Description gijs.hillenius@gmail.com 2011-02-10 00:40:30 UTC
Created attachment 43190 [details]
Xorg log, 

A Thinkpad Z61m has a Radeon Mobility X1400 on board. Up until this weekend, when Debian 6.0 was released, it was fine to use Debian 'testing & unstable' on this laptop, as long as KMS was disabled, by adding "options radeon modeset=0" to "/etc/modprobe.d/radeon-kms.conf".

Enabling KMS makes X not very useable, for after a while the screen will start to flicker, sometimes very fast, making everything a blur, and sometimes slower. In all cases, closing & opening the lid of the laptop helps restore X.

After Debian 6, newer Xorg related packages came into testing, and disabling KMS was no longer an option, for in that case X simply would not start.

I don't know what the issue is, but on the linux-thinkpad mailing list it was described this week as: "The GPU loses somehow its synchronization over time."

Attaching the X log

output from lspci -v 

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400 (prog-if 00 [VGA controller])
        Subsystem: Lenovo Device 202a
        Flags: bus master, fast devsel, latency 0, IRQ 30
        Memory at d8000000 (32-bit, prefetchable) [size=128M]
        I/O ports at 2000 [size=256]
        Memory at ee000000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at ee020000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: radeon

Debian Linux, linux-image 2.6.32-5-686
Comment 1 gijs.hillenius@gmail.com 2011-02-10 00:53:05 UTC
Created attachment 43191 [details]
Dmesg
Comment 2 Alex Deucher 2011-02-10 09:11:35 UTC
Please attach a copy of your vbios:
(as root)
(use lspci to get the bus id)
cd /sys/bus/pci/devices/<pci bus id>
echo 1 > rom
cat rom > /tmp/vbios.rom
echo 0 > rom

Also, can you try a vanilla kernel?  2.6.36 or 2.6.37 or 2.6.38 from Linus git tree?
Comment 3 gijs.hillenius@gmail.com 2011-02-10 22:42:21 UTC
Created attachment 43226 [details]
attached is  a copy of my vbios
Comment 4 gijs.hillenius@gmail.com 2011-02-10 22:43:03 UTC
will also try a newer kernel and report back. Will take a day or two....
Comment 5 Alex Deucher 2011-02-10 23:46:49 UTC
Created attachment 43233 [details] [review]
possible fix

Can you please try the attached patch on top of 2.6.38-rc4 or newer?
Comment 6 gijs.hillenius@gmail.com 2011-02-10 23:51:48 UTC
Just tried it with Linux-image 2.6.37 from Debian Experimental, but that does
not fix the screen flickering..

Will look at that patch you just added (thanks!).
Comment 7 gijs.hillenius@gmail.com 2011-02-22 01:54:06 UTC
I confirm, running 2.6.38-rc6 fixes the problem.

Thanks

Gijs
Comment 8 Alex Deucher 2011-02-22 08:33:16 UTC
Fixed in 2.6.38rc6.  Most likely this patch:
5b40ddf888398ce4cccbf3b9d0a18d90149ed7ff

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.