Kernel 5.8.1 now on Stable

All looks normal, linux zen, linux lts, and mainline. Updated a few minutes ago.

System:    Kernel: 5.8.1-zen1-1-zen x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-linux-zen root=UUID=28319503-4f89-40d4-9d43-5d7d683fc87c rw quiet 
           resume=UUID=fa32a52c-c132-4799-a179-1f5cf76fb29c loglevel=3 nowatchdog 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 info: xfce4-panel, plank wm: xfwm4 dm: LightDM 1.30.0 
           Distro: EndeavourOS 2020.07.15 
Machine:   Type: Desktop Mobo: ASUSTeK model: CROSSHAIR VI HERO v: Rev 1.xx serial: <filter> UEFI: American Megatrends v: 6401 
           date: 12/07/2018 
CPU:       Topology: 8-Core model: AMD Ryzen 7 1800X bits: 64 type: MT MCP arch: Zen family: 17 (23) model-id: 1 stepping: 1 
           microcode: 8001137 L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 127751 
           Speed: 2196 MHz min/max: 2200/4000 MHz boost: disabled Core speeds (MHz): 1: 2506 2: 2215 3: 2197 4: 2318 5: 2195 
           6: 2195 7: 2196 8: 2196 9: 2080 10: 2071 11: 2097 12: 2070 13: 1837 14: 2083 15: 2202 16: 2198 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] vendor: ASUSTeK driver: amdgpu 
           v: kernel bus ID: 0d:00.0 chip ID: 1002:687f 
           Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa display ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9") 
           Monitor-1: HDMI-A-0 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") diag: 686mm (27") 
           Message: Unable to show advanced data. Required tool glxinfo missing. 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Vega 10 HDMI Audio [Radeon Vega 56/64] driver: snd_hda_intel v: kernel 
           bus ID: 0d:00.1 chip ID: 1002:aaf8 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 0f:00.3 chip ID: 1022:1457 
           Sound Server: ALSA v: k5.8.1-zen1-1-zen 
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: 5.6.0-k port: e000 bus ID: 05:00.0 
           chip ID: 8086:1539 
           IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 12.96 TiB used: 990.49 GiB (7.5%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 250GB size: 232.89 GiB block size: physical: 512 B 
           logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 1B2QEXE7 scheme: GPT 
           ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block size: physical: 512 B logical: 512 B 
           speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
           ID-3: /dev/sdb vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block size: physical: 512 B logical: 512 B 
           speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
           ID-4: /dev/sdc vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block size: physical: 512 B logical: 512 B 
           speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
           ID-5: /dev/sdd vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block size: physical: 512 B logical: 512 B 
           speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT 
           ID-6: /dev/sde type: USB vendor: Western Digital model: WD easystore 25FB size: 9.10 TiB block size: 
           physical: 4096 B logical: 512 B serial: <filter> rev: 3004 scheme: GPT 
Partition: ID-1: / raw size: 216.21 GiB size: 211.82 GiB (97.97%) used: 7.74 GiB (3.7%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: /home raw size: 931.51 GiB size: 3.64 TiB (400.00%) used: 982.75 GiB (26.4%) fs: btrfs dev: /dev/sda1 
Swap:      Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 15.69 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 36.9 C mobo: N/A gpu: amdgpu temp: 24 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 
Info:      Processes: 363 Uptime: 16m Memory: 31.35 GiB used: 2.14 GiB (6.8%) Init: systemd v: 246 Compilers: gcc: 10.1.0 
           Packages: pacman: 823 lib: 230 Shell: Bash v: 5.0.17 running in: xfce4-terminal inxi: 3.1.05 

Looks like there is more lurking in kernel 5.8.1, first time at my desk today with two external monitors and right away I had a couple of Bumblebee crashes and another Virtualbox crash this morning. About time for 5.8.2 :slight_smile:

1 Like

5.8.2 brings in a lot of fixes (over 400).
For 5.8.3, already about 100 fixes in the queue… :slight_smile:


Nice! A lot of Bluetooth too. From glancing over it the BT issues 5.8 introduced could be fixed.


this is only a start , 5.8 to 4.19 sync changes

and more are coming

that why btrfs is never ended ( network too )


Aaand 5.8.2 is out. Bluetooth connection issue seems to be fixed and it’s working as expected again. :raised_hands:


Aaand 5.8.3 is out now :joy:

1 Like

It looks like schedutil replaced powersave as scaling governor? :thinking:

On Intel or AMD?
I think schedutil has been the default for (newer) AMD since some time already, but not sure.
My Intel laptop still is on powersave but that might be some setting.

Intel IvyBridge. Conky is always running and I noticed that the frequencies were somewhat unusual for the load. This is 5.8.2:

# cpupower frequency-info 
available cpufreq governors: performance schedutil

Checking on 5.4 LTS its still performance and powersave.

Hmm on Kaby Lake I still have performance and powersave
Maybe you need to load the module?
sudo modprobe governor_powersave
sudo modprobe cpufreq_powersave

1 Like

Interesting. Currently I see a few hundred MHz more on light load but also slightly lower temperatures (it’s a desktop). I guess it’s fine. I was just irritated having that change happen on a minor release.

5.8.4-rc1 just hit and it looks a little more reasonable in size. Maybe this one will fix my touchscreen (that still works fine with 5.7)

Edit: 5.8.4-rc2 just hit, so it is no longer a little update, though still smaller than 5.8.2 and 5.8.3. 5.8.x might take a while to get sorted out.

see this

from The kernel’s command-line parameters — The Linux Kernel documentation

value are disable , passive , force , no_hwp , hwp_only ,support_acpi_ppc ,per_cpu_perf_limits

try with hwp_only ,per_cpu_perf_limits , force

check on kernel 5.8

@Stephane Thanks, I’m fine at the moment.

I’m getting powersave back with modprobe as described by @anon31687413 , but for whatever reason that currently hard throttles the CPU to the minimum frequency. :man_shrugging:

we have also a report

Interesting. I have a Kaby Lake i5-8250U laptop on manjaro latest stable with 5.8.1 and everything is fine (powersave & performance, no throttling on powersave). And as I said, I’m 99.9% sure the desktop (EOS) was fine on 5.8.1 and 5.8.2, here it started with 5.8.3.

Biggest Kernel release…
Kinda what i expected, biggest amount of problems :sweat_smile:

KISS Tux :penguin:, KISS :kiss:


OK, from my limited understanding looking at the code - and this is the first C code I tried to read in 20 years: [1] changes the intel_pstate driver so that everything before Broadwell isn’t running intel_pstate but intel_cpufreq.

The good news: there’s an undocumented intel_pstate=active which brings back intel_pstate.

PS: There’s also heavy refactoring going on for 5.9 which seems to affect Broadwell and older. [edit] There it also documents the new behavior (“optional”) [2]:

Active Mode Without HWP
This operation mode is optional for processors that do not support the HWP feature or when the intel_pstate=no_hwp argument is passed to the kernel in the command line. The active mode is used in those cases if the intel_pstate=active argument is passed to the kernel in the command line.

HWP is supported in Skylake and later.



5.8.4 is in the repo!

5.8.5: Hold my beer …