@Khurshid: In which case it's a different bug which should be reported
as a new one separately. This one is about AMD/ATI cards/drivers, not
Intel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
This bug has returned for me on Xenial for Intel 965 GMA and many other
older intel video drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns
... unfortunately I realized that my problem begins NOT with screensaver
activation, but screen LOCK activation.
During test I switched off the LOCK, this is why my problem seemed to be solved.
I found another bug report which describes my problem:
I faced with exactly the same problem with different hardware:
Data:
- Fresh install of Ubuntu 15.10 (plus some other non-desktop or gnome related
packages)
- All energy consumption related settings are default (I have not changed them
till now).
- Laptop: ACER Aspire V3-371-51
- CPU: Intel
I am using Dell latitude e7440, Ubuntu trusty, having the same problem.
Every time I lock my screen using -L, after a few seconds my
vent goes crazy and the temperature rises to 80+ Celsius.
I could not run the `dstack` file properly. The output of `sh ./dstack compiz >
compizstack.txt` was
I've just upgraded to the Catalyst 13.11 Beta Drivers linked in #104 and
my CPU utilization issue has gone away. When the monitor shuts off, the
CPU usage goes down instead of to 100%
I'm going to say fixed for me with latest 13.11 drivers
--
You received this bug notification because you are
OK then. I haven't retested myself but trust both comment #105 and the
upstream bug info. Therefore fix released somewhere around:
fglrx-installer (2:13.101-0ubuntu1) saucy; urgency=low
fglrx-installer-updates (2:13.101-0ubuntu1) saucy; urgency=low
** Changed in: fglrx-installer (Ubuntu)
** Tags added: battery-power-consumption quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
glXWaitVideoSyncSGI or
Just to check, Can anyone confirm that this is still a problem with the
Catalyst 13.11 Beta drivers?
http://support.amd.com/en-us/kb-articles/Pages/Latest-LINUX-Beta-
Driver.aspx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Either the upstream bug was re-introduced or never really fixed because
I'm running the amd-catalyst-13.8 beta2 version (fglrx 13.2000). As
soon as the screen shuts off, the CPU usages spikes to 100%. Neither of
the workarounds work for me. I've been forced to just turn off X at
night.
I've
No issues with amd-catalyst-13.8 beta2 (since 12.12 for that matter) in
combination with GNOME Shell (3.8) on Ubuntu GNOME 13.04 for me.
@David: Are you using Unity or GNOME Shell and which version of Ubuntu
are you running?
--
You received this bug notification because you are a member of
I'm running Ubuntu 12.10 quantal with the amd-catalyst-13.8 beta2
drivers downloaded from the AMD website and compiled/installed on the
system. I've not tried GNOME but I've seen this in the other xsession
environments. The primary use of this box is running a standalone xbmc
instance though.
WORKAROUND (2):
1. Run ccsm (from package compizconfig-settings-manager)
2. In OpenGL Sync To VBlank = OFF
worked for me in Ubuntu 12.04
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Patrick, is this the bug you are experiencing?:
http://ati.cchtml.com/show_bug.cgi?id=553
This is what I'm currently experiencing using KDE + fglrx drivers,
unless I use the xrender backend or disable compositing altogether.
Unfortunately, using xrender causes issues with windowed OpenGL apps not
I'm running Kubuntu 12.10 and this bug continues to affect me with 13.1,
using .deb packages I built automatically from their 13.1 installer.
It looks like this is just as ‘fixed’ as their ‘Konsole resize causes X
crash’ bug.
--
You received this bug notification because you are a member of
Patrick, does using Xrender as kwin's compositing backend work as a
workaround? That's how I resolved my blank screen freezes using previous
versions of the fglrx driver. I haven't been able to get a freeze using
13.1 + kwin OpenGL backend yet, but we'll see...
--
You received this bug
Bug affects me as well.
** Changed in: compiz (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off
This is an upstream bug, and it's been fixed in 13.1 so please either
install 13.1 or wait until Ubuntu updates fglrx in the repository (even
though they are practically the same -- minus a few differences -- if
you build them.)
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
blablack: I'm not aware of AMD sharing their release schedule with us.
When it is available from AMD, you should keep an eye on:
https://launchpad.net/ubuntu/+source/fglrx-installer
https://launchpad.net/ubuntu/+source/fglrx-installer-updates
Our package maintainer might have more info:
Alberto
Quick questions - Once the driver is released by AMD:
- Will it be available in Ubuntu 12.10?
- Which version of the driver will be updated: fglrx or fglrx-updates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Daniel: That does not explain why Gnome Shell users had the same issue
earlier. For the record, I have vsync enabled in CCC and no high CPU
issue to be seen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Regardless of what is affected and what is not... AMD have confirmed
their driver is to blame and they have a fix.
If Gnome is not affected, that's awesome. But we don't need to worry
about why.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I can confirm Forage's comment: Ubuntu 12.10 Gnome Remix does not have this
problem.
I switched from Ubuntu 12.10 to the Gnome Remix and the problem seemed to solve
itself. And I will note that I am running the exact same
drivers/programs/extensions that I was when I was experiencing the
Oops.. Sorry, I mean.. disagree.
I experience High CPU usage in Gnome Remix, too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
I agree with Kellen Hawley.
Gnome Remix couldn't solve this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
Gnome probably does not suffer from this bug if it doesn't have any
vsync enabled by default. That's equivalent to WORKAROUND (2) listed
at the top of the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I forgot all about that until you had mentioned the 12.12 driver, for
those of you who cannot wait you can get the 12.11 beta (which of course
is the 12.12) and install it:
http://support.amd.com/us/kbarticles/Pages/AMDCatalyst1211betadriver.aspx
--
You received this bug notification because you
And for those who can't wait: Ubuntu 12.10 GNOME remix still works like
a charm. No compiz, no CPU issues, with tear-free enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx
** Changed in: fglrx
Status: Unknown = Confirmed
** Changed in: fglrx
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when
I agree it's critical and I would love to have time to work on it.
Hopefully this week.
Please stop complaining about status changes. So many people complain
about status changes that I mostly don't bother changing bug status's
even when I should, just so no one will complain.
--
You received
P.S. Compiz is open source. Canonical is not to blame for things not
getting fixed, but everyone is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen
...@gmail.com
Reply-To: Bug 969860 969...@bugs.launchpad.net
Subject: [Bug 969860] Re: fglrx uses 100% CPU when screen turns off (spinning
in glXWaitVideoSyncSGI or glXSwapBuffers)
Why is this constantly being pushed? And being pushed at all, this is a
pretty critical issue that breaks quite
** Also affects: fglrx via
http://ati.cchtml.com/show_bug.cgi?id=535
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU
OK, I've spent hours testing various options. The bug is much harder to
reproduce in Ubuntu 12.10 because the default rendering method in Compiz 0.9.8
is the same as the workaround (1) listed at the top of the bug. To reproduce
the bug I had to force the rendering method that Compiz 0.9.7 uses:
Crap, I had a strong suspicion this was the case because I too didn't
experience this bug in 12.10 but 12.10 did not really appeal to my
tastes (because of some personal reasons that aren't necessary to this
bug.) I don't remember if I ever mentioned that in another bug or not.
Just as a side
With the fglrx driver on my laptop using Kubuntu, I have to turn off
screen blanking, because every once in a while it causes my system to
hang when the screen blanks. I am able to reset gracefully using
ALT+PrintScrn+REISUB. I wonder if this is related to the same fglrx bug.
I will try running my
Jordan: I have already mentioned all the settings I've changed in
comment #80.
However if you want an optimal tear-free experience then you should not
change the compiz settings. The default compiz settings in 12.10 give
the optimal tear-free experience, unless it's disabled in your driver
AMD tell me the fix is complete and will appear in Catalyst 12.12 (which
I think means the December release?).
I'm still confused about the relationship between the Catalyst version
number (year.month?) and the fglrx version number that comes from it.
But AMD also tell me that it will be made
** Changed in: compiz-core
Milestone: 0.9.7.10 = 0.9.7.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
Why is this constantly being pushed? And being pushed at all, this is a
pretty critical issue that breaks quite a few laptops, I don't even
understand why you would ignore an issue like this and push it instead
of making it a top priority issue...
--
You received this bug notification because
While we're at it, can anyone update us on the status of this bug in
Precise? When I tested it on Quantal it was working exactly as intended
with no side-affects like this so I'm wondering if there are plans to
fix this soon? Since it seems like it didn't make it into the point.
--
You received
What version is the fixed one?
I have updated my comiz to 0.9.8.4-bzr3407, but the problem still
exists.
What can I do?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses
** Changed in: compiz
Status: Triaged = Fix Released
** Changed in: compiz/0.9.8
Status: Triaged = Fix Released
** Changed in: compiz-core
Status: Triaged = Fix Released
** Changed in: ubuntu-power-consumption
Status: Confirmed = Fix Released
** Changed in: compiz
** Changed in: compiz
Status: Fix Released = Triaged
** Changed in: compiz/0.9.8
Status: Fix Released = Triaged
** Changed in: compiz-core
Status: Fix Released = Triaged
** Changed in: compiz (Ubuntu)
Status: Fix Released = Triaged
** Changed in: fglrx-installer
** Also affects: compiz-core
Importance: Undecided
Status: New
** Changed in: compiz-core
Status: New = Triaged
** Changed in: compiz-core
Importance: Undecided = High
** Changed in: compiz-core
Milestone: None = 0.9.7.10
--
You received this bug notification because
I had the same problem using a Ubuntu 12.10/Gnome 3.6/Radeon HD 6650M
/fglrx-updates set up. None of the workarounds worked for gnome-shell
(although they worked when using Unity).
My workaround was to uninstall gnome-screensaver and replace it with
xscreensaver.
--
You received this bug
still affects me on 12.10 Gnome Remix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
glXWaitVideoSyncSGI or glXSwapBuffers)
To
I had the same problem for a while now, until recently I found a
solution which I'm going to share with you. I know it's not the ideal
approach, but I hope it will be useful for you guys until someone fixes
the issue.
Investigating I found that installing Caffeine in my Ubuntu 12.04.1 and
As of Ubuntu 12.10 GNOME remix in combination with AMD CCC 12.11 beta
(fglrx 9.010) the issue has disappeared! Note that I did a complete
fresh install (not perserving the home folder either) and I have yet to
test it with tear free and vsync on, but so far so good.
--
You received this bug
Is this bug solved in Ubuntu 12.10 ?? I cant't test beta2 by myself
right now, sorry.
@DanielVanVugt, if you need some test, logs or alternative workarounds,
I can help (if you want, of course)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
no it was not with beta 1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
glXWaitVideoSyncSGI or glXSwapBuffers)
To manage
** Changed in: compiz
Milestone: 0.9.8.4 = 0.9.9.0
** Changed in: compiz
Assignee: Daniel van Vugt (vanvugt) = (unassigned)
** Also affects: compiz/0.9.8
Importance: Undecided
Status: New
** Changed in: compiz/0.9.8
Status: New = Triaged
** Changed in: compiz/0.9.8
** Changed in: compiz
Milestone: 0.9.8.2 = 0.9.8.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
glXWaitVideoSyncSGI or
Just a small heads-up:
Activating Force full screen redraw (buffer swap) on repaint caused a
significant increase in CPU load with regular usage on my system. That's
why I had to go back to deactivating the automatic screen switch
entirely.
In the course of doing so I discovered another bug in
compiz 0.9.8.1 doesn't solve the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
glXWaitVideoSyncSGI or glXSwapBuffers)
** Changed in: compiz
Milestone: 0.9.8.0 = 0.9.8.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
glXWaitVideoSyncSGI or
Well, this is a little bit embarrasing.
The workaroung porposed in #48 have another error, sorry.
I prefer to detail it again.
This is the only workaround that works for me:
### ATI Privative
capiporra, please see bug 880707 about Ubuntu 11.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
glXWaitVideoSyncSGI or
Sorry but I forgot some info in the workaround proposed in #48
I disabled Sync to VBlankin ccsm-OpenGL.
Since 1 August no more compiz overloaded in standby mode
If I enable Sync to VBlank, when I close the lid of my notebook, compiz
raise to 100% inmediately, with Sync to VBlank disabled never
** Description changed:
- WORKAROUND:
+ WORKAROUND (1):
1. Open Catalyst Control Center.
2. Go to 3D More Settings.
3. Set Wait for vertical refresh to On, unless application specifies.
And if that doesn't work, then also do:
4. Run ccsm
5. In Workarounds, enable Force full screen
@Daniel, what do you think this bug needs fixing? If its fglrx we could
ask Canonical-Xorg team to talk to AMD maybe?
** No longer affects: compiz-core
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Omer,
How and what needs fixing depends on the outcome of more testing on
fglrx that I have not had time to do yet.
It really depends if the spin is always below
glXWaitVideoSyncSGI/glXSwapBuffers, or if the functions are returning
back to compiz on each iteration (too quickly).
If anyone else
I just wanted to add that I had the same problem for a while so I
started checking the temp every 10 mins or so and it was solid at 62-65C
with a full load. I deduced the only time I had issues with it
overheating was when the screensaver was on. I turned it off and set
the display to turn off
Forget my previous comment, it's failing again :(
Yesterday it was working but today, after shutdown at night, cpu up to
100% when the screen turns off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am sorry, I'll have to revoke my statement. After restarting the
system everything works fine again thanks to the workarounds posted in
the OP. Thank you for saving my notebook from an untimely heat death.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I updated my kernel to 3.4.6 , disabled all the workarounds and know
it's working right (fixed).
I used the last quantal(12.10) kernel packages (Linux envy
3.4.6-030406-generic #201207191609 SMP Thu Jul 19 20:11:13 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux version) in my ubuntu 12.04
--
You
Confirmed. Workarounds don't work. I would love to supply the stack info
as requested in posts #4 and #5. But when I enter the command I get the
following error message:
~$ sudo sh ./dstack compiz compizstack.txt
sh: 0: Can't open ./dstack
Also, how can I enter the command when the problem
Here's some additional adata on my machine:
lspci | grep VGA
02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Madison
[Radeon HD 5000M Series]
(Mobility Radeon HD 5650 on Acer 3820TG)
uname -a
Linux AcerUBN 3.2.0-27-generic #43-Ubuntu SMP Fri Jul 6 14:25:57 UTC 2012
@knowhow91:
~$ sudo sh ./dstack compiz compizstack.txt
sh: 0: Can't open ./dstack
About the Can't open ./dstack error: you need to download the script
first. It's attached on comment #4.
Also, how can I enter the command when the problem disappears as soon
as I unlock my machine?
Try this:
I just installed Ubuntu 12.04 to a desktop machine with Radeon HD 5870
and compiz is using 100% when the screen is off. I didnt try any of the
workarounds on this machine. There are so many workarounds mentioned and
half of them seem to work only for half of the people. I dont know where
to
Regarding high CPU usage when screen turns off.
I might have had a real casualty of this bug. An 18 day old HP Pavilion
g6 failed after being left unattended for about 1 hour while running
Ubuntu. The laptop was on a hard smooth surface in an air conditioned
environment. It was found fan
I'm a bit surprised to hear that disabling Tear Free solves the issue.
I've tried that in the past, in combination with vsync, and today again,
but to no avail.
I'm using GNOME Shell, are you perhaps using Unity?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Yes I am using Unity. Not sure if you disabled Tear Free in normal or
admin mode? I had to disable it in admin mode and set the vsync setting
to On, unless application specifies also in admin mode for this
workaround to take effect.
--
You received this bug notification because you are a member
I'm always using admin mode when making changes in CCC. I gave it
another go, followed by a reboot as well, but the issue remains.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx
OK, thanks to George's tip I finally solved the problem just disabling
tear-free in catalyst center (admin mode) and the configuration
proposed in the workaround:
(obviously with the proprietary ATI fglrx)
1. Open Catalyst Control Center (admin mode).
2. Display Options - Tear Free- disabled
3.
For the workaround to work I had to run catalyst control centre as
administrator and disable tearfree. I forgot that I had that enabled and
made all the changes in the workaround to no avail. As soon as I
disabled tearfree and set vsync as per the workaround in admin mode it
worked :)
--
You
Followed the advice of #21 and disabled vsync in ccsm. It's already off
in ccc.
This helped against the spin, and I experience no noticable tearing. The
other workarounds didn't help.
Running on AMD E-450, Ubuntu 12.04, Unity, fglrx-updates 8.860 (12.4)
--
You received this bug notification
Weirdly, this bug does not happen if I turn the screen off using:
xset dpms force off
But it does still happen if I let the gnome screensaver kick in and turn the
monitor off.
Does that mean it's a problem specifically with ACPI? It doesn't happen
with DPMS.
--
You received this bug
For me changing from the gnome-screensaver to the xscreensaver worked.
I still have around 7% of CPU usage from compiz while the screen is locked,
which in my opinion is still a lot for displaying nothing, but at least it
consumes less battery on my laptop.
I am running Ubuntu 12.04 on a HP
I've disabled screensavers and I can replicate the issue only closing
the lid of my laptop (configured to do nothing in power settings)
*My stacktrace is posted above
ACPI problem has sense. ¿maybe passing acpi=off at boot options does the
trick?
I can't do it myself at this moment. I'm out of
Here's my stack trace. dstack kept hanging, so I just ran gdb manually.
This appears to be the same bug, but the workarounds don't help. This is
a:
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
Manhattan [Mobility Radeon HD 5430 Series]
And the ioctl that loops is
Affects me too, both workarounds do not solve problem.
Running Ubuntu 12.04 with ATI 5850HD.
Attached compiz stack traces.
** Attachment added: Compiz stack trace
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/969860/+attachment/3207779/+files/compizstack.txt
--
You received this bug
Please check this question in Super User
http://superuser.com/questions/439904/windows-7-ati-graphics-gpu-fan-
speeds-up-when-display-goes-into-sleep-mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I figured this was driver behaviour unique to fglrx so it's not
surprising it happens on Windows too. However we might yet be able to
work around it in Compiz.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In Ubuntu 11.10 with catalyst 11.8 or fglrx this bug isn't present. At
least I can't replicate it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns
The set Wait for vertical refresh to On, unless application
specifies workaround does not fix the issue when running gnome-shell.
Compiz is not being used when using gnome-shell. Therefore I expect
there will be no point in installing ccsm to try the alternative
workaround. Is this assumption
Also, updating the driver to AMD CCC 12.6 beta (fglrx 8.980) does not
solve the issue either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off
I reported the issue upstream at
http://ati.cchtml.com/show_bug.cgi?id=535
** Bug watch added: ATi Linux Platform Bugs #535
http://ati.cchtml.com/show_bug.cgi?id=535
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marked as affecting gnome-shell, as reported by multiple people. Also
affects fglrx, obviously.
** Summary changed:
- [fglrx] compiz uses 100% CPU when screen turns off (spinning in
glXWaitVideoSyncSGI or glXSwapBuffers)
+ fglrx uses 100% CPU when screen turns off (spinning in
89 matches
Mail list logo
