Bug#628080: xserver-xorg-video-radeon: Low performance after a period of inactivity

Michel Dänzer daenzer at debian.org
Fri Jun 17 02:15:58 PDT 2011


On Sam, 2011-06-04 at 17:34 +0200, dayer wrote: 
> El mié, 01-06-2011 a las 09:14 +0200, Michel Dänzer escribió: 
> > On Fre, 2011-05-27 at 01:30 +0200, dayer wrote:
> 
> > When the problem occurs, do the radeon numbers in /proc/interrupts increase?
> 
> Yes. "/proc/interrupts" contains:
> 
>            CPU0       
>   0:         44   IO-APIC-edge      timer
>   1:          4   IO-APIC-edge      i8042
>   6:          3   IO-APIC-edge      floppy
>   7:          1   IO-APIC-edge      parport0
>   8:          0   IO-APIC-edge      rtc0
>   9:          0   IO-APIC-fasteoi   acpi
>  12:          6   IO-APIC-edge      i8042
>  14:      13995   IO-APIC-edge      pata_via
>  15:          0   IO-APIC-edge      pata_via
>  16:     400001   IO-APIC-fasteoi   radeon
>  17:  556661064   IO-APIC-fasteoi   skge at pci:0000:00:0a.0, hda_intel

[...]

> The radeon numbers are increasing and the end this causes these lines in
> dmesg (and the system begins to run slow):

Do the radeon numbers stop increasing after the messages about IRQ 16?


> [ 1679.754669] irq 16: nobody cared (try booting with the "irqpoll"
> option)

[...]

> [ 1679.754896] Disabling IRQ #16
> 
> And another messages appear later also in dmesg:
> 
> [ 4984.745387] irq 17: nobody cared (try booting with the "irqpoll"
> option)

[...]

> [ 4984.745479] Disabling IRQ #17
> 
> I'm thinking about try booting with the "irqpoll". What do you think?

Probably can't hurt to try. Note that as IRQ 17 is also affected, this
may not be a radeon specific problem at all but a more general IRQ
problem on your system.


> > Does booting with radeon.agpmode=-1 on the kernel command line help?
> > 
> Yes, it helps! The performance doesn't fall already, although...
> 
> With it in /var/log/Xorg.0.log appears a new warning in addition to previous:
> 
> (WW) RADEON(0): Direct rendering disabled

Something's going wrong with that option, resulting in the DRI being
disabled completely. As you've experienced with empathy, this is not
desirable for various reasons.


-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer





More information about the xorg-driver-ati mailing list