Bug 2513629 - tuned-adm verify always fails
Summary: tuned-adm verify always fails
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: tuned
Version: 45
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-10 19:38 UTC by Petr Sklenar
Modified: 2026-08-18 15:02 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
tuned.log from Raspberry Pi 400 - shows boost write failures and verify errors (32.07 KB, text/plain)
2026-08-10 19:40 UTC, Petr Sklenar
no flags Details

Description Petr Sklenar 2026-08-10 19:38:57 UTC
Description of problem:
On Raspberry Pi 400 (aarch64, cpufreq-dt driver), tuned-adm verify always fails because the throughput-performance and balanced profiles both set boost=1, but the BCM2711 SoC does not support CPU frequency boost. Writing to /sys/devices/system/cpu/cpufreq/policy0/boost returns EINVAL.

Tuned logs the write failure during apply but still expects boost=1 during verification, causing a permanent verify failure on this hardware. This affects all aarch64 platforms using cpufreq-dt without boost support.

Additionally, the default active profile is throughput-performance (server) while tuned-adm recommend correctly returns balanced (appropriate for a desktop SBC).

Version-Release number of selected component:
tuned-2.27.0-3.fc45.noarch
kernel-7.2.0-0.rc6.260806g0d8395707651.51.fc45.aarch64

How reproducible:
Always (100%)

Steps to Reproduce:
1. Install Fedora 45 (Rawhide) on Raspberry Pi 400
2. Run: tuned-adm active
3. Run: tuned-adm verify
4. Run: tuned-adm recommend
5. Check: cat /var/log/tuned/tuned.log

Actual Results:
tuned-adm verify fails:

  verify: failed: device cpu2: 'boost' = 'None', expected '1'
  verify: failed: device cpu3: 'boost' = 'None', expected '1'
  verify: failed: device cpu1: 'boost' = 'None', expected '1'
  verify: failed: device cpu0: 'boost' = '', expected '1'

tuned.log shows apply also fails:

  WARNING  tuned.plugins.plugin_cpu: Unable to set boost on cpu 'cpu2'. Neither per-policy boost nor intel_pstate no_turbo is available.
  ERROR    tuned.utils.commands: Writing to file '/sys/devices/system/cpu/cpufreq/policy0/boost' error: '[Errno 22] Invalid argument'

Active profile is throughput-performance but tuned-adm recommend returns balanced.

Expected Results:
1. If boost is not supported by the hardware, tuned should skip boost verification (or treat it as passed) instead of reporting a permanent failure.
2. The default active profile should match tuned-adm recommend (balanced) on desktop/SBC hardware.

Additional info:
- Hardware: Raspberry Pi 400 Rev 1.0 (aarch64)
- CPU: BCM2711 (Cortex-A72), cpufreq-dt driver, 600-1800 MHz, no boost
- Affects: All aarch64 platforms using cpufreq-dt without boost support
- Note: Both throughput-performance and balanced profiles have boost=1, so switching profiles does not help

Comment 1 Petr Sklenar 2026-08-10 19:40:59 UTC
Created attachment 2154177 [details]
tuned.log from Raspberry Pi 400 - shows boost write failures and verify errors

Comment 2 Petr Sklenar 2026-08-11 13:24:42 UTC
Confirmed also on x86_64 KVM virtual machine (F45 Rawhide):

Host CPU: Intel Core Ultra 7 165H
Guest: QEMU/KVM, 8 vCPUs
Kernel: 7.2.0-0.rc6.260806g0d8395707651.51.fc45.x86_64
tuned-2.27.0-3.fc45.noarch

All 3 profiles fail verify due to boost:
- balanced (active): boost='None', expected '1' on all 8 CPUs
- virtual-guest (recommended): same boost failure
- throughput-performance: same

KVM guests have no cpufreq boost support - /sys/devices/system/cpu/cpufreq/policy0/boost does not exist.

Additional failures on x86_64 VM not seen on RPi:
- ALPM: 6 SCSI hosts report max_performance instead of med_power_with_dipm
- cpufreq_conservative module not loaded (balanced profile expects it)

This bug affects both aarch64 (RPi 400) and x86_64 (KVM guests) - any platform where CPU boost is not available.

Comment 3 Aoife Moloney 2026-08-17 15:50:50 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle.
Changing version to 45.


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