as the merge request for this was rejected as not needed, i'm marking
this bug as wontfix.
** Changed in: systemd (Ubuntu Disco)
Status: In Progress => Won't Fix
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Won't Fix
** Changed in: systemd (Ubuntu Xenial)
** Tags removed: sts sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1806012
Title:
set-cpufreq: 'powersave' governor configuration sanity on ubuntu
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1806012
Title:
set-cpufreq: 'powersave' governor configuration sanity on ubuntu
server
Anyone with any opinions on whether the 'ondemand' service should be
end-user configurable should please comment in the merge proposal.
https://code.launchpad.net/~joalif/ubuntu/+source/systemd/+git/systemd/+merge/367469
--
You received this bug notification because you are a member of Ubuntu
Just opened a MP against systemd to make the 'ondemand' service configurable
through
/etc/default/cpufrequtils file.
This change has two purposes :
1) Make 'onedmand' service configurable.
It is important for the 'ondemand' service to be configurable because depending
on the use case
and the
** Merge proposal linked:
https://code.launchpad.net/~joalif/ubuntu/+source/systemd/+git/systemd/+merge/367469
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1806012
> > Reassigning to the kernel
>
> please don't. This is a bug in systemd
with that said - that we believe this should stay open against systemd
so end users can configure ondemand - there certainly may also be a bug
in the kernel causing the slowness; if anyone (@lathiat?) has found
that's the
It is normally always preferable to use the intel-pstate driver compared
to pcc-cpufreq or acpi-cpufreq on modern Intel hardware.
Some HP ProLiant platforms implement the PCC interface [1] which can be
disabled by a BIOS setting in which case the PCC driver will not load
and the acpi-cpufreq
> Reassigning to the kernel
please don't. This is a bug in systemd because its set-cpufreq script
provides no way for the user to override its hardcoded values of what
governor it select. We will be providing a systemd patch to add user
configurability.
** Package changed: linux (Ubuntu) =>
Based on the analysis in the log, there does not appear to be a bug in
systemd - which is behaving as intended, and defaulting to the best
available cpufreq governor for low power consumption - but there may be
a bug in the kernel resulting in the wrong scaling driver being used on
the hardware in
On the previously mentioned HP server today I was able to get closer to
reproducing the situation by testing with bionic (4.15.0-47-generic)
instead of xenial (4.4)
On bionic, unlike xenial, even with the BIOS set to "BIOS controlled
dynamic" mode, the intel_pstate driver is loaded instead of
@lathiat:
> - Is there some specific hardware where scaling-driver=pcc-cpufreq
> and scaling-governor=ondemand performs poorly. I have yet to run a
> benchmark on my example hardware to find out.
Yes, we first started seeing this when deploying new Ubuntu Archive
servers where we had two
TBH it was probably whatever the default mode was in the BIOS - we saw
the same issue on Dell and HP servers.
This one >> "You mean that you let systemd ondemand service do whatever
it does by default"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@james-page
What was the the BIOS setting before setting it to "OS control"?
Also what do you mean by "we've just stuck with the default ondmand behaviour" ?
You mean that you let systemd ondemand service do whatever it does by default or
that you use the ondemand governor ?
--
You received this
I tried to get the ondemand script dropped in 2015 #1503773, Got Nacked.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1806012
Title:
set-cpufreq: 'powersave' governor
Confirmed that pcc-cpufreq *can* be used in preference to intel_pstate
even on a CPU that supports intel_pstate if the firmware tables are
setup to request such. One such server is an E5-2630 v3 HP DL360 G9
(shuckle).
On the default "dynamic" firmware setting you get driver=pcc-cpufreq +
Something I was not previously aware of that informs this a bit more, is
that in some BIOS modes (apparently HP uses this extensively, unsure
about Dell and others) you get a "Collaborative Power Control" mode,
which sets the scaling_driver to pcc-cpufreq (as opposed to cpufreq) and
is some weird
(as context to this information, apparently this particularly bad
performance experienced with 'powersave' happens when the BIOS power
control is set to the default, and goes away when in the BIOS you set
power management to 'os control' - so there is some additional
information needed to
See also LP: #1732696 and LP: #1579278.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1806012
Title:
set-cpufreq: 'powersave' governor configuration sanity on ubuntu
Just to add some more detail to this bug; for the impacted deployment we
actually ended up re-configuring the power regulator settings via the
BIOS to delegate to the OS for control; after a reboot we've just stuck
with the default ondemand behaviour and performance has been
consistent/better than
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
** Tags added: sts sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1806012
Title:
set-cpufreq: 'powersave' governor configuration sanity on ubuntu
22 matches
Mail list logo
