** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503773
Title:
Drop ondemand init script
To manage notifications about this bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503773
Title:
Dr
This continues to cause breakage - https://bugs.launchpad.net/charm-
sysconfig/+bug/1873028
I'm still looking for a modern justification for it to exist -
considering AFAIK no other distro does this.
** Description changed:
Ondemand init script is not inherited from Debian, it's an Ubuntu
sp
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503773
Title:
Drop ondemand init script
To manage notifications about th
And it actually got added as a systemd job.. so this is not actually
fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503773
Title:
Drop ondemand init script
To manage notifications about this
and by merge I meant sync..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503773
Title:
Drop ondemand init script
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
It's been removed in Yakkety due to the merge from Debian. Thanks!
** Changed in: sysvinit (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503773
Titl
>AFAICT our kernel config is set to performance - why not just set it to
ondemand?
So from my understanding, the point of the ondemand script is really so
we can have boot set to performance, and then switch later to something
that saves more power. The goal is boot performance so If we survey
ma
@Steve Langasek
A big issue is that the script makes quite arbitrary assumptions on the system,
including the fact that there is an ondemand governor at all.
A large number of modern systems use the intel p-state driver that does
not have an ondemand governor at all! On this systems, the fallback
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sysvinit (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503773
Title:
D
>which is to ensure that the desired governor is set for the running
system.
This is the key part that I don't understand, why don't we just trust
the kernel? If the kernel sets the wrong governor on certain hardware
isn't that the bug that needs fixing? On one system without this
script it def
Please see my answer on bug #1497375.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503773
Title:
Drop ondemand init script
To manage notifications about this bug go to:
https://bugs.launchpad.net
12 matches
Mail list logo
