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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
@dino99: That's fine, the script has
AVAILABLE="/sys/devices/system/cpu/cpu$FIRSTCPU/cpufreq/scaling_available_governors"
[ -f $AVAILABLE ] || exit 0
thus it's a no-op for those cases.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
Closing the kernel task, as it's now obvious that we want to keep the
"performance" default there, and only do the "ondemand" thing for older
processors.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
--
Yo
Note that with old cpu (Piv q9550) the cpufreq subdir does not exist (with or
without cpufreq* installed).
So checking that path will always fails.
ls /sys/devices/system/cpu/cpu0/
cache driver microcode subsystem uevent
crash_notes firmware_node node0 th
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584124
Title:
revisit /etc/init.d/ondemand
Status in l
So it seems we should make the "ondemand" init script a no-op if
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver contains
"intel_pstate", since in this case "ondemand" is worse than
"performance"?
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Thanks Colin! So this confirms that we really should let the kernel be
in "performance" during boot. But from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278/comments/9
it actually sounds like we should leave it to "performance" all the time
at least for processors which are ≤ 5 years
Some data to take into consideration. I've tested 4 difference configs
(3 laptops, 1 server) of mixed Intel and AMD hardware, comparing the
default powersave/ondemand [1] vs performance
[1] depends on CPU and if intel-pstate is supported
For faster modern Intel CPUs where intel-pstate is support
Holding the porting to a systemd unit until we have some updated
measurements and a decision whether we'll move to "performance" as
default or keep the current logic.
** Changed in: systemd (Ubuntu)
Milestone: ubuntu-16.05 => None
** Changed in: systemd (Ubuntu)
Assignee: Martin Pitt (pi
Bug #1579278 to consider switching to "performamce" may be of relevance
here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584124
Title:
revisit /etc/init.d/ondemand
Status in linux
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-16.05
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584124
Title:
revisit /etc/init.d/ondemand
Status in linux package in
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584124
Title:
revisit /etc/init.d/ondemand
Statu
13 matches
Mail list logo
