> Setting the governor to performance 'fixes' it.
> I don't know if this is *this* issue or another one, so happy to open a new
> issue if you prefer.
we will be changing the built-in 'ondemand' systemd service (set-cpufreq
script, technically) to allow end-user configuration instead of using
onl
The last outstanding open task for sysvinit/xenial is also invalid, to
my understanding. Both /etc/init.d/ondemand in <= xenial and
/lib/systemd/set-cpufreq in >= bionic implement the intended default
policy of interactive/ondemand/powersave, not performance.
** Changed in: sysvinit (Ubuntu Xenia
NOTE: That these are systems using the pcc-cpufreq and acpi-cpufreq
drivers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1579278
Title:
Keep powersave CPU frequency sc
** Attachment added: "load 15m 2017-08-23 02-10-53"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278/+attachment/4969406/+files/load%2015m%202017-08-23%2002-10-53.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
@dsmythies, sorry, missed your question. We're actually seeing
performance issues/load on a couple of our Ubuntu Archive servers
(archive.ubuntu.com). They're high traffic servers with 10GbE NICs with
just apache2 serving .deb packages from disk. We've recently upgraded a
few to 4.11.0-14-generic f
@fish : Yes your issue does not belong here.
To figure out where your issue actually belongs, some details are
missing:
If your stuck at low frequency issue only occurs after a suspend and on
battery power, then your issue is covered by:
https://bugzilla.kernel.org/show_bug.cgi?id=90041 (and it i
On my Dell XPS 13 (i7-6500U) the only governors available are
performance and powersave. Ubuntu 16.04 seems to set this always to
'powersave' for me. This causes the CPU to clock down to 300-400Mhz when
idle. Unfortunately it's not clocking up again when under load
sometimes. Setting the governor t
This bug was fixed in the package systemd - 231-6git1
---
systemd (231-6git1) yakkety; urgency=medium
Upload current Debian packaging git.
[ Michael Biebl ]
* fsckd: Do not exit on idle timeout if there are still clients connected
systemd-fsckd's event loop terminates if no
@Haw Loeung: In addition to what I wrote earlier:
> With the new Ubuntu archive servers, we saw constantly high load
> and after some tinkering, we found that it was mostly CPUs
> being woken up to see if they should enter idle states.
> Changing the CPU frequency scaling governor to "performance"
@Haw Loeung: It would be good to understand in more detail your
findings. As far as I know (and I am not an expert in this area), great
care has been taken to avoid things like wakeups just to decide to go
idle.
I did a test on my computer (Ubuntu 16.04 server, no GUI), but to avoid
extra overhead
> I'll make it dynamically enabled
https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=19e67c70
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
With https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=94a70093 it uses powersave on
intel_pstate again, like in xenial.
> pitti, can we please have a config option to disable "ondemand"?
Indeed, right now it is statically enabled, so it can only be disabled
with "systemctl mask
pitti, can we please have a config option to disable "ondemand"?
As originally reported, one some workloads, it seems setting to
powersave/ondemand causes high load with CPUs checking to see if they
need to enter powersave state.
While the original report included perf report for the acpi-cpufreq
Thanks Doug! Ack, I'll change it to use "powersave" again then.
** Changed in: systemd (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launc
The table formatting got messed up, trying again:
Load: idle0.5XX 2X 3X 4X 5X 100%
powersave 570811037 16075 29147 45913 61165 76650 81695
3.817.3610.72 19.43 30.61 40.78 51.10 54.46
performance
Using kernel 4.8-rc5 I did some energy tests, using a SpecPower simulator that
I made one time. I reused intel_pstate powersave data from a previous test.
Reference:
http://marc.info/?l=linux-kernel&m=147326197513427&w=2
Big numbers are Joules (package Joules from turbostat)
Smaller numbers are
>> The preferred governor with the intel_pstate driver is powersave.
> Do you have some references/proof for that? This is contrary to what
> kernel developers say, see comment 1.
In my opinion, that reference is obsolete.
While I don't work for Intel, the intel_pstate CPU frequency driver is
pr
> The preferred governor with the intel_pstate driver is powersave.
Do you have some references/proof for that? This is contrary to what
kernel developers say, see comment 1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sy
What has been done here is incorrect.
The old "ondemand" script was modified so that if the intel_pstate
driver was being used, and therefore "ondemand" did not exist, it would
fall through to setting the "powersave" governor (refer to bug
#1314643). Note that "powersave" with the intel_pstate CPU
This bug was fixed in the package systemd - 230-3git1
---
systemd (230-3git1) yakkety; urgency=medium
Upload current Debian packaging git to fix tests.
[ Martin Pitt ]
* tmp.mount: Add nosuid and nodev mount options. This restores compatibility
with the original SysV int RA
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=2558ca88
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https
21 matches
Mail list logo