cpufreq_boost from kernel_misc in ubuntu_ltp failed on B-5.0 / 5.3 / F-5.11

Bug #1842032 reported by Po-Hsu Lin
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Undecided
Krzysztof Kozlowski
linux-hwe-edge (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

 startup='Fri Aug 23 20:24:18 2019'
 cpufreq_boost 0 TINFO : found 'acpi_cpufreq' driver, sysfs knob '/sys/devices/system/cpu/cpufreq/boost'
 cpufreq_boost 0 TINFO : maximum speed is 3800000 KHz
 cpufreq_boost 0 TINFO : load CPU0 with boost enabled
 cpufreq_boost 0 TINFO : elapsed time is 3588 ms
 cpufreq_boost 0 TINFO : load CPU0 with boost disabled
 cpufreq_boost 0 TINFO : elapsed time is 3587 ms
 cpufreq_boost 1 TFAIL : cpufreq_boost.c:187: compare time spent with and without boost (-2%)
 tag=cpufreq_boost stime=1566591858 dur=7 exit=exited stat=1 core=no cu=717 cs=0

Po-Hsu Lin (cypressyew)
tags: added: 5.0 ppc64el sru-20190812 ubuntu-ltp
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This failure could be found on some instances of B-AWS-5.0 this cycle (5.0.0-1022.25~18.04.1)
 * x1e.large

tags: added: aws bionic sru-20191111
tags: added: amd64
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Found on node baltar with 5.3.0 Bionic 5.3.0-40.32~18.04.1

tags: added: 5.3 sru-20200127
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Found on node baltar with 5.3.0 Bionic 5.3.0-40.32~18.04.1, didn't see this on P8 node modoc

Log:
cpufreq_boost 1 TBROK : safe_file_ops.c:301: Failed to close FILE '/sys/devices/system/cpu/cpufreq/boost' at cpufreq_boost.c:180: errno=EINVAL(22): Invalid argument

Po-Hsu Lin (cypressyew)
tags: added: sru-20200316
summary: - cpufreq_boost from kernel_misc in ubuntu_ltp failed on B-5.0 P9
+ cpufreq_boost from kernel_misc in ubuntu_ltp failed on B-5.0 / 5.3 P9
Revision history for this message
Kelsey Steele (kelsey-steele) wrote : Re: cpufreq_boost from kernel_misc in ubuntu_ltp failed on B-5.0 / 5.3 P9

Spotted on Bionic aws : 4.15.0-1084.88 : amd64

Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

Also spotted on Focal aws : 5.4.0-1026.26 : amd64

tags: added: 5.4 focal sru-20200921
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

Found on Groovy/linux 5.8.0-31.33 ppc64el (P9)

tags: added: 5.8 groovy sru-20201109
tags: added: sru-20210412
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Found on 5.11.0-1005.5 - intel
with node spitfire, skipped on node bavor (Turbo is disabled by BIOS or unavailable on processor)

 startup='Wed Jun 9 04:16:06 2021'
 cpufreq_boost 0 TINFO : found 'intel_pstate' driver, sysfs knob '/sys/devices/system/cpu/intel_pstate/no_turbo'
 cpufreq_boost 0 TINFO : maximum speed is 3400000 KHz
 cpufreq_boost 0 TINFO : load CPU0 with boost enabled
 cpufreq_boost 0 TINFO : elapsed time is 2062 ms
 cpufreq_boost 0 TINFO : load CPU0 with boost disabled
 cpufreq_boost 0 TINFO : elapsed time is 1650 ms
 cpufreq_boost 1 TFAIL : cpufreq_boost.c:186: compare time spent with and without boost (-2%)
 tag=cpufreq_boost stime=1623212166 dur=3 exit=exited stat=1 core=no cu=356 cs=2

tags: added: 5.11 sru-20210531
Po-Hsu Lin (cypressyew)
summary: - cpufreq_boost from kernel_misc in ubuntu_ltp failed on B-5.0 / 5.3 P9
+ cpufreq_boost from kernel_misc in ubuntu_ltp failed on B-5.0 / 5.3 /
+ F-5.11
Revision history for this message
Krzysztof Kozlowski (krzk) wrote :

Found on focal/aws-5.8 5.8.0-1036.38~20.04.1

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-hwe-edge (Ubuntu):
status: New → Confirmed
Revision history for this message
Krzysztof Kozlowski (krzk) wrote :

Found on focal/linux-aws 5.4.0-1050.52

Changed in ubuntu-kernel-tests:
assignee: nobody → Krzysztof Kozlowski (krzk)
Revision history for this message
Krzysztof Kozlowski (krzk) wrote :
Changed in ubuntu-kernel-tests:
status: New → In Progress
Revision history for this message
Krzysztof Kozlowski (krzk) wrote :

The fix for virtual environments was committed to autotest-client-tests. Could not find the error on metal instances, so closing the bug.

Changed in ubuntu-kernel-tests:
status: In Progress → Fix Released
Changed in linux-hwe-edge (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.