Bug 2094581 - Kernel 5.18 test week: performance regression (kaby lake)
Summary: Kernel 5.18 test week: performance regression (kaby lake)
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 36
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2022-06-07 23:19 UTC by itrymybest80
Modified: 2022-06-08 15:54 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-06-08 15:15:41 UTC
Type: Bug

Attachments (Terms of Use)

Description itrymybest80 2022-06-07 23:19:11 UTC
My system performance has tanked following the 5.18 kernel upgrade with slower boot, file browsing, gaming performance and audio stutter.

Enabling "performance mode" doesn't help, but rebooting into 5.17.12 makes all tasks run like prior to the kernel upgrade.

The same game that would run at 57fps (over multiple runs) will drop to 45fps at the same scene and video playback on the web now has intermittent stutter.

I'm not running any modules that didn't ship directly with your kernel and it's reproducible on my end.

kernel-5.18.1-200.fc36.x86_64 (regression)
kernel-5.18.2-200.fc36.x86_64 (regression)
kernel-5.19.0-0.rc0.20220531git8ab2afa23bd1.8.fc37.x86_64 (regression)
kernel-5.19.0-0.rc1.20220607gite71e60cd74df.15.fc37.x86_64 (regression)

Fedora Linux 36 (Workstation Edition) x86_64 sv_SE.UTF-8
GNOME 42.2 / Mutter
Intel 200 Series / Z370 Chipset Family
Intel i5-7600K (4) @ 4.200GHz
2211MiB / 15935MiB (16GB)
Realtek ALC1220 / PipeWire 0.3.51 (i686, x86_64) WirePlumber 0.4.10
AMD Radeon RX 580 (LLVM 14.0.0, DRM 3.46) MESA 22.1.1

Comment 1 Justin M. Forbes 2022-06-08 15:15:41 UTC
Test again with 5.18.2-201 that should fix it.

Comment 2 itrymybest80 2022-06-08 15:54:49 UTC
Thank you so much! My apologies for overlooking your 201 build. My system performance is back to "normal" again.

Note You need to log in before you can comment on or make changes to this bug.