This bug was fixed in the package linux-raspi - 5.8.0-1003.6
---
linux-raspi (5.8.0-1003.6) groovy; urgency=medium
* groovy/linux-raspi: 5.8.0-1003.6 -proposed tracker (LP: #1898142)
* Please switch default, hwe, oem kernel flavours governor to
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-raspi (Ubuntu Groovy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
This bug was fixed in the package linux-riscv - 5.8.0-3.3
---
linux-riscv (5.8.0-3.3) groovy; urgency=medium
* groovy/linux-riscv: 5.8.0-3.3 -proposed tracker (LP: #189)
* Miscellaneous Ubuntu changes
- [Config] update config for CONFIG_VGACON_SOFT_SCROLLBACK
[
This bug was fixed in the package linux - 5.8.0-19.20
---
linux (5.8.0-19.20) groovy; urgency=medium
* groovy/linux: 5.8.0-19.20 -proposed tracker (LP: #1895120)
* Please switch default, hwe, oem kernel flavours governor to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that
not needed for oem-5,6 which is (mostly) focal only
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
>From my understanding, focal has systemd 245.4-4, so we don't yet need
to backport this kernel chnage to focal. If it is deemed necessary to
backport this to focal kernels please let me know.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@Dimitry: Are we not safe on 20.04 because the "ondemand" systemd
service is still there and will switch to "ondemand" CPU freq governor
after boot?
This service has been removed in systemd 245.5-1. Are there plan to
backport this to 20.04.2?
--
You received this bug notification because you
@colin-king with or without additional measurements default to
performance and relying on userspace to switch to ondemand at some later
point during boot is wrong. It means we are risking melting laptops and
catching fire. I.e. boot machine, walk away, it sits in the initrd at
the LUKS unlock
@julian Ubuntu Desktop in 20.04.2 will receive the 20.10's kernel by
default and thus will adopt the 20.10 default. Imho the linux-generic
(ga) kernel should also be updated to the same default, to make it the
same across -generic, -hwe, -oem kernel flavours in 20.04. Because in
20.04, defaulting
Thanks Julian, I'd like to find range of recent kit and do a full
analysis. I fear that what ever the default, it will be suboptimal for
some configurations.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
For example, the measurements on the X220 do not reflect situation on
modern Intel systems, as they scale differently from Skylake and newer,
as they do not have HWP.
A CPU with HWP (hardware P-states) behaves as you'd expect sort of - it
runs at close to max frequency all the time, and scales
Why are we looking at focal now? The change to systemd only happened
after the opening of groovy.
Data is tricky. There are a ton of different cpufreq drivers that are
affected, and they all have different behavior. pstates alone has
different behavior on newer intels that do pstates in hardware
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-riscv (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
Proof that we must not use performance governor attached, from one of my
team mates.
** No longer affects: systemd (Ubuntu)
** Attachment added: "performance-governor.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+attachment/5403156/+files/performance-governor.jpg
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-riscv (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-oem-5.6 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
** Description changed:
[Impact]
* Kernel should have sensible default governor set to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y for the generic, hwe, raspi,
- riscv64, oem kernel flavours in Focal and Groovy+.
+ riscv, oem kernel flavours in Focal and Groovy+.
* ondemand.service
Fix sent to mailing list for review: https://lists.ubuntu.com/archives
/kernel-team/2020-August/112820.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1885730
Title:
Please
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu Groovy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in
20 matches
Mail list logo
