Bug 648128

Summary: Enabling desktop effects makes kwin extremely sluggish (intel driver)
Product: [Fedora] Fedora Reporter: Robin Green <greenrd>
Component: mesaAssignee: Adam Jackson <ajax>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: ajax, fedora, jreznik, kevin, ltinkl, rdieter, rnovacek, ry, smparrish, than, thomasj, xgl-maint
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-31 13:17:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg output
none
Xorg.0.log
none
output of opreport -agdwfl% -t5 none

Description Robin Green 2010-10-31 07:40:23 UTC
Created attachment 456697 [details]
dmesg output

Description of problem:
I tried to enable desktop effects in KDE and KDE instantly disabled them, saying they were too slow. I turned off functionality checks and re-enabled them. kwin then becomes extremely slow (and so do desktop effects).

I think desktop effects should work, because 3D hardware acceleration seems to be enabled.

Version-Release number of selected component (if applicable):
kdebase-workspace-4.5.2-3.fc14.i686

How reproducible:
Always

Steps to Reproduce:
1. Fedora menu -> Computer -> System settings -> Desktop effects
2. Enable desktop effects and disable functionality checks in Advanced (leave all other options at their defaults)
  
Actual results:
kwin very slow (uses 20-99% CPU)

Expected results:
kwin not very slow

Additional info:

Comment 1 Robin Green 2010-10-31 07:41:20 UTC
Created attachment 456698 [details]
Xorg.0.log

Comment 2 Robin Green 2010-10-31 08:46:34 UTC
Created attachment 456705 [details]
output of opreport -agdwfl% -t5

I used oprofile to get a profile of what was consuming the most CPU cycles - I ran oprofile for a short time and just let the machine "sit idle" (although it wasn't actually idle at all, as the results show).

Comment 3 Robin Green 2010-10-31 08:48:42 UTC
Also, I was using the oprofile GUI oprof_start, and it reported what seemed to me like a very large number of interrupts taking place initially, although that settled down a bit after a few seconds. There was no hard drive activity which could have caused that.

Comment 4 Robin Green 2010-10-31 11:41:05 UTC
Workaround: Downgrade to the following packages (I got them from koji)

glx-utils-7.8.1-8.fc13.i686
mesa-dri-drivers-7.8.1-8.fc13.i686
mesa-libGL-7.8.1-8.fc13.i686
mesa-libGLU-7.8.1-8.fc13.i686
mesa-libOSMesa-7.8.1-8.fc13.i686
xorg-x11-drv-evdev-2.4.0-2.fc13.i686
xorg-x11-drv-intel-2.11.0-3.fc13.i686
xorg-x11-drv-synaptics-1.2.2-6.fc13.i686
xorg-x11-server-Xorg-1.8.0-17.fc13.i686
xorg-x11-server-common-1.8.0-17.fc13.i686

Comment 5 Kevin Kofler 2010-10-31 13:17:01 UTC
Thank you for your bug report. Your issue is already known, therefore I'm closing this bug as a duplicate. However, your additional logs might help debugging the issue, so thank you for attaching those.

*** This bug has been marked as a duplicate of bug 640375 ***