Kernel 5.5

RC1 is out.

Code:

---

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.5.0-050500rc1-lowlatency
Found initrd image: /boot/initrd.img-5.5.0-050500rc1-lowlatency
Found linux image: /boot/vmlinuz-5.5.0-050500rc1-generic
Found initrd image: /boot/initrd.img-5.5.0-050500rc1-generic
Found linux image: /boot/vmlinuz-5.5.0-999-lowlatency
Found initrd image: /boot/initrd.img-5.5.0-999-lowlatency
Found linux image: /boot/vmlinuz-5.5.0-999-generic
Found initrd image: /boot/initrd.img-5.5.0-999-generic
Found linux image: /boot/vmlinuz-5.5.0-994-lowlatency
Found initrd image: /boot/initrd.img-5.5.0-994-lowlatency
Found linux image: /boot/vmlinuz-5.5.0-994-generic
Found initrd image: /boot/initrd.img-5.5.0-994-generic
Found linux image: /boot/vmlinuz-5.3.0-25-lowlatency
Found initrd image: /boot/initrd.img-5.3.0-25-lowlatency
Found linux image: /boot/vmlinuz-5.3.0-25-generic
Found initrd image: /boot/initrd.img-5.3.0-25-generic

---

;)

Kernel 5.5 rc1 is available and is owrking fine here.

https://ubuntuforums.org/showthread.php?t=2432815

Threads merged

Kernel 5.5-rc2 is available:

Code:

---

doug@s18:~$ uname -a
Linux s18 5.5.0-050500rc2-lowlatency #201912151930 SMP PREEMPT Mon Dec 16 00:45:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

---

I have only been running it for a few minutes, but I ran 5.5-rc1 for most of the week without issues.

Link back trail to previous Kernel rc series threads: 5.4, 5.3, 5.2, 5.1, 5.0, 4.20, 4.19 ?, 4.18, 4.17, 4.16, 4.15, 4.14.

Among other kernel configuration changes, sometime during the kernel 5.4-rc series Ubuntu changed from "CONFIG_UCLAMP_TASK_GROUP is not set" to "CONFIG_UCLAMP_TASK_GROUP=y".
The new cgroup v2 related code involved was only added as of kernel 5.4-rc1, and it has issues.
On one of two Ubuntu server test computers, when the schedutil CPU frequency scaling governor is used with either the acpi-cpufreq or intel_cpufreq CPU frequency scaling drivers, the system response is more like the performance governor as opposed to the expected response of the schedutil governor.
From what I've experienced, and been challenged by, it is premature to be setting CONFIG_UCLAMP_TASK_GROUP in the kernel configuration, and if I reset it, the resulting system response is as expected for the schedutil governor.

This issue has being driving me crazy for over a month. I have misdiagnosed it and come to incorrect conclusions several times. After a few weeks, someone upstream followed up, and now it is finally understood.

References:
Proposed patch
proposed patch test results
pre-patch test reaults

also rc6 is here

Code:

---

corrado@corrado-p9-ff-0104-x:~$ inxi -Sxx
System:
  Host: corrado-p9-ff-0104-x Kernel: 5.5.0-050500rc6-generic x86_64 bits: 64
  compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.3 wm: gnome-shell dm: GDM3
  Distro: Ubuntu 20.04 LTS (Focal Fossa)
corrado@corrado-p9-ff-0104-x:~$

---

Hope Ubuntu releases a signed 5.5 kernel soon. Due to needing to "secure boot" for reasons, I'm currently stuck on 5.4.0-9, which is based on 5.4.3.

The problem is that 5.4 3 introduced a nasty audio bug (#204477)for those of us using Nvidia GPU's to send audio over HDMI & Bluetooth to our monitor's speakers.

EDIT: Today's 5.4.0-12 release fixes the issue I described. Also, 5.5 was finally released by Linus.

Also 5.5.2 is released but unfortunately on focal we will have the 5.4 kernel
https://www.omgubuntu.co.uk/2020/02/...kernel-5-4-lts