Just a note for other people that read this. I had the same problem
described here on Ubuntu 10.10 beta, and also thought it must be some
CPU scaling problem, but like Oliver it turned out to be a GPU scaling
issue (running glxgears made it go away).
I have found the easiest way to fix this is to
The cpufreq folder under apps-ghome-power-manager has been removed in
Lucid. I can not change my up_threshold value from 95 which virtually
never upscales any of my 8 i7 cores
--
CPU Scaling too aggressive
https://bugs.launchpad.net/bugs/107545
You received this bug notification because you are
Please note that this bug is in state Fix Released and was about the
opposite! Before Jaunty up_threshold was 31, which wastes power and
forces loud fans while playing movies or even mp3.
Now the default is 95 which causes jitter on some systems. There is a new bug
about this problem in Jaunty
Nice to hear that! If compiz and glxgears influences your frame rate and
burnP6 with lower prio does not, then it is most likely a problem with
3D graphics. It's strange that changing up_threshold does make a
difference. But IMHO this points to a race condition in the video
driver.
In Jaunty the
I noticed that up_threshold on my computer was 95 (is it default) which
caused HD movies to play like on slow computer. I changed it to 60 to
correct the problem. Maybe 95 is to high for a default value in
ondemand?
--
CPU Scaling too aggressive
https://bugs.launchpad.net/bugs/107545
You
Thanks, Oliver. I tried this and the performance was the same running
burnP6 and running it with a nice level of -1. Strangely, with
up_threshold set to 40, there was never a drop in performance: as soon
as I changed it back to 95, the drop in fps was immediate. Running
glxgears actually
No, nice level 0 is default for user processes. A *negative* value gives
more priority to a process (see man nice).
You were right! In Jaunty my sampling_rate_min is also 4 (was 1
in Hardy). But as expected, I am still able to set sampling_rate down to
4. Nevertheless 4 against
To verify if CPU scheduling is your problem you could try cpuburn.
Commands in this package are: burnP6, burnK7, ect. (optimized for
different CPU types) and they just waste CPU cycles. Run your test-app
with higher prio together with burnXY:
$ burnP6
$ sudo nice -1 wine CoD4
If your test app
My test-app (wine CoD4) isn't running with a nice level above zero. But
perhaps there's a problem with the kernel incorrectly recognising nice
levels. Shouldn't I set it to one rather than zero though? The default
setting is currently zero.
--
CPU Scaling too aggressive
Could it be that your test-app runs with a nice value above zero? You can check
this with command top (column NI). If so, then you can make you cpu
accelerate by executing the two commands:
$ sudo su
$ echo 0 /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load
I've no experience
@Oliver: I tried setting the sampling rate to 4 as suggested, but it
stays set to 8 (I am using kernel 2.6.30-rc7 in case that makes a
difference). sampling_rate_min is set to 4. Why alter the sampling
rate instead of the up threshold, though?
--
CPU Scaling too aggressive
Stange, on my working system (8.04.2, Pentium M 2GHz) the
sampling_rate_min is 1 and setting sampling_rate to this value is
possible. Did you try the 2 commands sudo su; echo ... or only sudo
echo ...? The first one works here.
As I understand it: lowering the sampling_rate makes the
Sorry for the typo: 4 means 4 us (microseconds), not ms.
--
CPU Scaling too aggressive
https://bugs.launchpad.net/bugs/107545
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can change sampling_rate to 4 with the 2.6.28-12 kernel, but not
the 2.6.30-rc7 kernel. Values equal to or above 8 are fine.
This behaviour looks to be deliberate in 2.6.30 - cpufreq_ondemand.c has
this in it:
/* Above MIN_SAMPLING_RATE will vanish with its sysfs file soon
* Define
@Owen and @draft:
If you can reproduce the bad performance of flash videos, please try if
lowering the sampling_rate would help. Minimum is 1 us, try 4 us (= 25
fps):
$ sudo su
$ echo 4 /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
If the peaks of CPU demand are too
That setting doesn't seem to help much, if at all. the cpu is still
mostly staying on the lowest setting and I'm still dropping frames.
Right now I'm using this video as a test, because it has a lot of pans
which make dropped frames more obvious:
I have a good, fast machine, a Dell XPS M1330 (800MHz-2.4Ghz), and I've
seen this problem too with flash videos. The new default threshold is
too high. I find a value of 35 or lower is needed to properly scale the
CPU while playing back video.
--
CPU Scaling too aggressive
I'm also seeing bad interactivity and erratic performance on an Atom-based
netbook here. This is especially evident with bursty loads, as caused by the
Flash plugin when watching videos, for example.
If I remember correctly, the former default was 80%, and this seems to work a
lot better than
I'm using an Aspire One netbook and have a really bad performance with
Jaunty. The problem is that the ondemand governor does not react by
increaing clock speed e.g., when watching a flash movie. The flash movie
works find if I change to the performance governor, but with ondemand
its unwatchable.
Jaunty cpu_freq is defaulted to
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
** Also affects: linux (Ubuntu Jaunty)
Importance: Low
Assignee: Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi)
Status: Triaged
** Changed in: linux (Ubuntu Jaunty)
Status: Triaged = Fix Released
**
This can be changed with gconf-editor under appsgnome-power-manager-cpufreq
setting performance_ac or performance_battery to 100 gives a up_threshold of 11
setting to 0 gives up_threshold of 99
37=85,
25=90
--
CPU Scaling too aggressive
https://bugs.launchpad.net/bugs/107545
You received this
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Interesting, as I am having the opposite problem. While off of battery
power, my cpu *never* goes to full throttle. I also have up_threshold at
31. amd64, hardy heron here.
--
CPU Scaling too aggressive
https://bugs.launchpad.net/bugs/107545
You received this bug notification because you are a
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold is set to
11 by default in Ubuntu 8.04, although it is possible to change the
value but I was unable to make it permanent.
--
CPU Scaling too aggressive
https://bugs.launchpad.net/bugs/107545
You received this bug notification because
I can confirm this too, in the newly installed Final Ubuntu 8.04, just
running Deluge BitTorrent Client alone will trigger it to maximum.
--
CPU Scaling too aggressive
https://bugs.launchpad.net/bugs/107545
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
--
CPU Scaling too aggressive
https://bugs.launchpad.net/bugs/107545
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
In Gutsy, I find that setting up_threshold in sysfs.conf does not have
effect after boot (I need to call /etc/init.d/sysfs restart manually).
--
CPU Scaling too aggressive
https://bugs.launchpad.net/bugs/107545
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I tested it with a fully updated Hardy Heron 8.04 Alpha: up_threshold
is still 31
uname -a
Linux oliverhp 2.6.24-11-generic #1 SMP Fri Feb 29 22:08:31 UTC 2008 i686
GNU/Linux
The bad thing is, that the default of 31 is not only set at boot time.
It is set again upon standbyresume,
Would it be possible for you to test the Hardy Heron 8.04 Alpha series
which is currently under development and contains an updated version of
the kernel: http://www.ubuntu.com/testing . Thanks.
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
CPU Scaling too aggressive
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
CPU Scaling too aggressive
https://bugs.launchpad.net/bugs/107545
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm this issue!
On my Laptop totem or xine use approx. 60% of 800MHz. By default
up_threshold is 31, so the CPU goes up to 2GHz, which makes the fan spin
quite loud.
The only work-around is to setup a cronjob for root that changes
up_threshold to 90 every 15 mins - not very nice. But I
** Changed in: linux (Ubuntu)
Sourcepackagename: None = linux
Importance: Undecided = Low
Assignee: Brian Murray (brian-murray) = Ubuntu Kernel ACPI Team
(ubuntu-kernel-acpi)
Status: Incomplete = Confirmed
--
CPU Scaling too aggressive
https://bugs.launchpad.net/bugs/107545
You
[EMAIL PROTECTED]:~$ cat
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
31
Yes it's still an issue. My laptop stays at 1.6 or 2.0GHz just because
I'm typing in Firefox or someone sent me a gmail message and the title
in the tab is flashing. Setting the above keeps me low, except
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in recently. We were wondering if this is still and issue
for you? Thanks in advance.
** Changed in: ubuntu
Assignee: (unassigned) =
34 matches
Mail list logo
