Description of problem: Version-Release number of selected component (if applicable): Red Hat 7.3 How reproducible: Steps to Reproduce: 1. Install red hat 7.3 with kernel-3.10.0-514.el7.x86_64, kernel-debuginfo-3.10.0-514.el7.x86_64 and kernel-debuginfo-common-x86_64-3.10.0-514.el7.x86_64. 2. Run Cpuscaling test 3. Get the result from web interface Actual results: Checking installed rpms: kernel-tools-3.10.0-327.el7.x86_64 All required packages installed System Capabilites: ------------------------------------------------- CPU 0 Model: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz System has 8 cpus Packages: package 0 has cpus: 0, 1, 2, 3, 4, 5, 6, 7 No supported frequency information Current Frequencies: cpu0: 4160109 cpu1: 3621656 cpu2: 3702375 cpu3: 4145484 cpu4: 4151953 cpu5: 4112437 cpu6: 4158703 cpu7: 4111031 Supported Governors: performance powersave Current governors: cpu0: performance cpu1: performance cpu2: performance cpu3: performance cpu4: performance cpu5: performance cpu6: performance cpu7: performance Verified cpus are uniform in supported frequencies and governors Processor Model: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz Maximum Model Frequency: 3600 MHz cpufreq driver: intel_pstate analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 4294.967295 ms. hardware limits: 800000 MHz - 4.200000 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800000 MHz and 4.200000 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 4.160109 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes analyzing CPU 1: driver: intel_pstate CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 4294.967295 ms. hardware limits: 800000 MHz - 4.200000 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800000 MHz and 4.200000 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 3.621656 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes analyzing CPU 2: driver: intel_pstate CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 4294.967295 ms. hardware limits: 800000 MHz - 4.200000 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800000 MHz and 4.200000 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 3.702375 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes analyzing CPU 3: driver: intel_pstate CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 4294.967295 ms. hardware limits: 800000 MHz - 4.200000 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800000 MHz and 4.200000 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 4.100906 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes analyzing CPU 4: driver: intel_pstate CPUs which run at the same hardware frequency: 4 CPUs which need to have their frequency coordinated by software: 4 maximum transition latency: 4294.967295 ms. hardware limits: 800000 MHz - 4.200000 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800000 MHz and 4.200000 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 4.151953 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes analyzing CPU 5: driver: intel_pstate CPUs which run at the same hardware frequency: 5 CPUs which need to have their frequency coordinated by software: 5 maximum transition latency: 4294.967295 ms. hardware limits: 800000 MHz - 4.200000 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800000 MHz and 4.200000 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 4.112437 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes analyzing CPU 6: driver: intel_pstate CPUs which run at the same hardware frequency: 6 CPUs which need to have their frequency coordinated by software: 6 maximum transition latency: 4294.967295 ms. hardware limits: 800000 MHz - 4.200000 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800000 MHz and 4.200000 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 4.137750 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes analyzing CPU 7: driver: intel_pstate CPUs which run at the same hardware frequency: 7 CPUs which need to have their frequency coordinated by software: 7 maximum transition latency: 4294.967295 ms. hardware limits: 800000 MHz - 4.200000 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800000 MHz and 4.200000 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 4.111031 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes CPU: 0 ---------- min: 800000 MHz max: 4200 MHz governors: performance, powersave, performance, powersave CPU: 1 ---------- min: 800000 MHz max: 4200 MHz governors: performance, powersave, performance, powersave CPU: 2 ---------- min: 800000 MHz max: 4200 MHz governors: performance, powersave, performance, powersave CPU: 3 ---------- min: 800000 MHz max: 4200 MHz governors: performance, powersave, performance, powersave CPU: 4 ---------- min: 800000 MHz max: 4200 MHz governors: performance, powersave, performance, powersave CPU: 5 ---------- min: 800000 MHz max: 4200 MHz governors: performance, powersave, performance, powersave CPU: 6 ---------- min: 800000 MHz max: 4200 MHz governors: performance, powersave, performance, powersave CPU: 7 ---------- min: 800000 MHz max: 4200 MHz governors: performance, powersave, performance, powersave CPU Flags: ida: Turbo Boost is supported aperfmperf: aperf/mperf is supported Measurement Method: /dev/cpu/0/cpuid indicates aperf/mperf is supported Using C sqrt load processes and aperf/mperf effective freq. measurement (aperf.c) Testing CPU Package 0 Syncing disks Waiting for low load... Current load average: 0.22 Done waiting Note: The userspace governor is not supported Using powersave min/max policies to get min and max performance workloads On Min/Max Power Save Governor Test: ------------------------------------------------- Setting governor to powersave Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? Error: can't set the governor: "cpupower -c all frequency-set --governor powersave --min 800000000 --max 3600000" returned 234 Changing cpu frequency from 4128 to 800000 MHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? Error: can't set the governor: "cpupower -c all frequency-set --governor powersave --min 800000000 --max 800000000" returned 237 Warning: Could not verify that cpu frequency is set to the minimum value of 800000000 KHz Running CPU load test - for all cpus in the package Running load test for package 0 starting process for cpu 0 using work process: ./aperf 0 starting process for cpu 1 using work process: ./aperf 1 starting process for cpu 2 using work process: ./aperf 2 starting process for cpu 3 using work process: ./aperf 3 starting process for cpu 4 using work process: ./aperf 4 starting process for cpu 5 using work process: ./aperf 5 starting process for cpu 6 using work process: ./aperf 6 starting process for cpu 7 using work process: ./aperf 7 waiting for load processes... process for cpu 0 is done in 14.25 seconds, at 4201 MHz process effective frequency: 4000 MHz process for cpu 1 is done in 14.18 seconds, at 4195 MHz process effective frequency: 4000 MHz process for cpu 2 is done in 14.20 seconds, at 4053 MHz process effective frequency: 3999 MHz process for cpu 3 is done in 14.21 seconds, at 4038 MHz process effective frequency: 4000 MHz process for cpu 4 is done in 14.19 seconds, at 4041 MHz process effective frequency: 3999 MHz process for cpu 5 is done in 14.17 seconds, at 4084 MHz process effective frequency: 4000 MHz process for cpu 6 is done in 14.19 seconds, at 4084 MHz process effective frequency: 4000 MHz process for cpu 7 is done in 14.19 seconds, at 4184 MHz process effective frequency: 4000 MHz processes complete average worker process time: 14.20 seconds Running load test for package 0 starting process for cpu 0 using work process: ./aperf 0 starting process for cpu 1 using work process: ./aperf 1 starting process for cpu 2 using work process: ./aperf 2 starting process for cpu 3 using work process: ./aperf 3 starting process for cpu 4 using work process: ./aperf 4 starting process for cpu 5 using work process: ./aperf 5 starting process for cpu 6 using work process: ./aperf 6 starting process for cpu 7 using work process: ./aperf 7 waiting for load processes... process for cpu 0 is done in 14.25 seconds, at 4183 MHz process effective frequency: 4000 MHz process for cpu 1 is done in 14.20 seconds, at 4097 MHz process effective frequency: 4000 MHz process for cpu 2 is done in 14.20 seconds, at 4062 MHz process effective frequency: 4000 MHz process for cpu 3 is done in 14.22 seconds, at 4105 MHz process effective frequency: 4000 MHz process for cpu 4 is done in 14.18 seconds, at 4189 MHz process effective frequency: 3999 MHz process for cpu 5 is done in 14.18 seconds, at 4097 MHz process effective frequency: 4000 MHz process for cpu 6 is done in 14.19 seconds, at 4098 MHz process effective frequency: 3999 MHz process for cpu 7 is done in 14.19 seconds, at 4099 MHz process effective frequency: 4000 MHz processes complete average worker process time: 14.20 seconds Minumum frequency average load test time: 14.20 Error: cpu0 in package 0 has a measured frequency of 4000 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz Error: cpu1 in package 0 has a measured frequency of 4000 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz Error: cpu2 in package 0 has a measured frequency of 4000 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz Error: cpu3 in package 0 has a measured frequency of 4000 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz Error: cpu4 in package 0 has a measured frequency of 3999 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz Error: cpu5 in package 0 has a measured frequency of 4000 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz Error: cpu6 in package 0 has a measured frequency of 3999 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz Error: cpu7 in package 0 has a measured frequency of 4000 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz Changing cpu frequency from 4079 to 3600 MHz, performance governor Setting cpu: 0 Setting cpu: 1 Setting cpu: 2 Setting cpu: 3 Setting cpu: 4 Setting cpu: 5 Setting cpu: 6 Setting cpu: 7 Warning: Could not verify that cpu frequency 4079 MHzis set to the maximum value of 3600 MHz Running CPU load test - for all cpus in the package Running load test for package 0 starting process for cpu 0 using work process: ./aperf 0 starting process for cpu 1 using work process: ./aperf 1 starting process for cpu 2 using work process: ./aperf 2 starting process for cpu 3 using work process: ./aperf 3 starting process for cpu 4 using work process: ./aperf 4 starting process for cpu 5 using work process: ./aperf 5 starting process for cpu 6 using work process: ./aperf 6 starting process for cpu 7 using work process: ./aperf 7 waiting for load processes... process for cpu 0 is done in 15.81 seconds, at 3600 MHz process effective frequency: 3600 MHz process for cpu 1 is done in 15.96 seconds, at 3600 MHz process effective frequency: 3599 MHz process for cpu 2 is done in 15.99 seconds, at 3600 MHz process effective frequency: 3599 MHz process for cpu 3 is done in 15.87 seconds, at 3600 MHz process effective frequency: 3599 MHz process for cpu 4 is done in 15.76 seconds, at 3600 MHz process effective frequency: 3600 MHz process for cpu 5 is done in 16.04 seconds, at 3600 MHz process effective frequency: 3599 MHz process for cpu 7 is done in 15.84 seconds, at 3600 MHz process effective frequency: 3600 MHz process for cpu 6 is done in 16.13 seconds, at 3600 MHz process effective frequency: 3600 MHz processes complete average worker process time: 15.93 seconds Running load test for package 0 starting process for cpu 0 using work process: ./aperf 0 starting process for cpu 1 using work process: ./aperf 1 starting process for cpu 2 using work process: ./aperf 2 starting process for cpu 3 using work process: ./aperf 3 starting process for cpu 4 using work process: ./aperf 4 starting process for cpu 5 using work process: ./aperf 5 starting process for cpu 6 using work process: ./aperf 6 starting process for cpu 7 using work process: ./aperf 7 waiting for load processes... process for cpu 1 is done in 15.80 seconds, at 3600 MHz process effective frequency: 3600 MHz process for cpu 2 is done in 15.78 seconds, at 3600 MHz process effective frequency: 3599 MHz process for cpu 3 is done in 15.90 seconds, at 3600 MHz process effective frequency: 3599 MHz process for cpu 4 is done in 16.11 seconds, at 3599 MHz process effective frequency: 3600 MHz process for cpu 5 is done in 15.79 seconds, at 3600 MHz process effective frequency: 3600 MHz process for cpu 6 is done in 15.79 seconds, at 3600 MHz process effective frequency: 3600 MHz process for cpu 7 is done in 15.94 seconds, at 3600 MHz process effective frequency: 3600 MHz process for cpu 0 is done in 16.30 seconds, at 3600 MHz process effective frequency: 3600 MHz processes complete average worker process time: 15.93 seconds Maximum frequency average load test time: 15.93 CPU Frequency Speed Up: 0.00 CPU 0 Measured Speed Up: 0.87 Warning: measured speedup 0.87 greater than the maximum speedup of -0.49 CPU Frequency Speed Up: 0.00 CPU 1 Measured Speed Up: 0.90 Warning: measured speedup 0.90 greater than the maximum speedup of -0.49 CPU Frequency Speed Up: 0.00 CPU 2 Measured Speed Up: 0.90 Warning: measured speedup 0.90 greater than the maximum speedup of -0.49 CPU Frequency Speed Up: 0.00 CPU 3 Measured Speed Up: 0.89 Warning: measured speedup 0.89 greater than the maximum speedup of -0.49 CPU Frequency Speed Up: 0.00 CPU 4 Measured Speed Up: 0.88 Warning: measured speedup 0.88 greater than the maximum speedup of -0.49 CPU Frequency Speed Up: 0.00 CPU 5 Measured Speed Up: 0.90 Warning: measured speedup 0.90 greater than the maximum speedup of -0.49 CPU Frequency Speed Up: 0.00 CPU 6 Measured Speed Up: 0.90 Warning: measured speedup 0.90 greater than the maximum speedup of -0.49 CPU Frequency Speed Up: 0.00 CPU 7 Measured Speed Up: 0.89 Warning: measured speedup 0.89 greater than the maximum speedup of -0.49 Single CPU Power Save Test: ------------------------------------------------- Setting governor to powersave (min: 800000 MHz, max: 3600 MHz) Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? Error: can't set the governor: "cpupower -c all frequency-set --governor powersave --min 800000000 --max 3600000" returned 234 Waiting 5 seconds... done. Using cpu 1 to test Single CPU On Demand. Running CPU load test - for only cpu 1 Running load test for package 0 Single CPU Test: Loading only cpu1 starting process for cpu 1 using work process: ./aperf 1 waiting for load processes... process for cpu 1 is done in 14.96 seconds, at 3600 MHz process effective frequency: 3599 MHz processes complete average worker process time: 14.96 seconds Running load test for package 0 Single CPU Test: Loading only cpu1 starting process for cpu 1 using work process: ./aperf 1 waiting for load processes... process for cpu 1 is done in 14.98 seconds, at 3600 MHz process effective frequency: 3599 MHz processes complete average worker process time: 14.98 seconds Single CPU load test time: 14.98 Single CPU Power Save Speedup: 0.9 Warning: measured speedup 0.95 greater than the maximum speedup of -0.49 Performance Governor Test: ------------------------------------------------- Setting governor to performance Setting cpu: 0 Setting cpu: 1 Setting cpu: 2 Setting cpu: 3 Setting cpu: 4 Setting cpu: 5 Setting cpu: 6 Setting cpu: 7 Running CPU load test - for all cpus in the package Running load test for package 0 starting process for cpu 0 using work process: ./aperf 0 starting process for cpu 1 using work process: ./aperf 1 starting process for cpu 2 using work process: ./aperf 2 starting process for cpu 3 using work process: ./aperf 3 starting process for cpu 4 using work process: ./aperf 4 starting process for cpu 5 using work process: ./aperf 5 starting process for cpu 6 using work process: ./aperf 6 starting process for cpu 7 using work process: ./aperf 7 waiting for load processes... process for cpu 0 is done in 15.86 seconds, at 3599 MHz process effective frequency: 3599 MHz process for cpu 1 is done in 15.79 seconds, at 3600 MHz process effective frequency: 3599 MHz process for cpu 2 is done in 15.78 seconds, at 3497 MHz process effective frequency: 3600 MHz process for cpu 3 is done in 15.77 seconds, at 3600 MHz process effective frequency: 3599 MHz process for cpu 4 is done in 15.76 seconds, at 3598 MHz process effective frequency: 3599 MHz process for cpu 5 is done in 15.77 seconds, at 3590 MHz process effective frequency: 3600 MHz process for cpu 6 is done in 15.76 seconds, at 3581 MHz process effective frequency: 3600 MHz process for cpu 7 is done in 15.76 seconds, at 3585 MHz process effective frequency: 3600 MHz processes complete average worker process time: 15.78 seconds Running load test for package 0 starting process for cpu 0 using work process: ./aperf 0 starting process for cpu 1 using work process: ./aperf 1 starting process for cpu 2 using work process: ./aperf 2 starting process for cpu 3 using work process: ./aperf 3 starting process for cpu 4 using work process: ./aperf 4 starting process for cpu 5 using work process: ./aperf 5 starting process for cpu 6 using work process: ./aperf 6 starting process for cpu 7 using work process: ./aperf 7 waiting for load processes... process for cpu 0 is done in 15.85 seconds, at 3488 MHz process effective frequency: 3600 MHz process for cpu 1 is done in 15.77 seconds, at 3598 MHz process effective frequency: 3600 MHz process for cpu 2 is done in 15.77 seconds, at 3588 MHz process effective frequency: 3600 MHz process for cpu 3 is done in 15.78 seconds, at 3600 MHz process effective frequency: 3600 MHz process for cpu 4 is done in 15.76 seconds, at 3596 MHz process effective frequency: 3600 MHz process for cpu 5 is done in 15.76 seconds, at 3499 MHz process effective frequency: 3600 MHz process for cpu 6 is done in 15.76 seconds, at 3500 MHz process effective frequency: 3599 MHz process for cpu 7 is done in 15.76 seconds, at 3500 MHz process effective frequency: 3600 MHz processes complete average worker process time: 15.78 seconds Performance load test time: 15.78 CPU 0 Performance Speedup: 0.90 Warning: measured speedup 0.90 greater than the maximum speedup of -0.49 CPU 1 Performance Speedup: 0.90 Warning: measured speedup 0.90 greater than the maximum speedup of -0.49 CPU 2 Performance Speedup: 0.90 Warning: measured speedup 0.90 greater than the maximum speedup of -0.49 CPU 3 Performance Speedup: 0.90 Warning: measured speedup 0.90 greater than the maximum speedup of -0.49 CPU 4 Performance Speedup: 0.90 Warning: measured speedup 0.90 greater than the maximum speedup of -0.49 CPU 5 Performance Speedup: 0.90 Warning: measured speedup 0.90 greater than the maximum speedup of -0.49 CPU 6 Performance Speedup: 0.90 Warning: measured speedup 0.90 greater than the maximum speedup of -0.49 CPU 7 Performance Speedup: 0.90 Warning: measured speedup 0.90 greater than the maximum speedup of -0.49 Restoring original governor to performance Setting cpu: 0 Setting cpu: 1 Setting cpu: 2 Setting cpu: 3 Setting cpu: 4 Setting cpu: 5 Setting cpu: 6 Setting cpu: 7 Summary for Package 0: CPU Effective Frequency: User Min User Max Performance -------- -------------- -------------- -------------- expected 800000 MHz 3600 MHz 3600 MHz cpu 0 4000 (14.25s) 3600 (16.30s) 3600 (15.85s) cpu 1 4000 (14.20s) 3600 (15.80s) 3600 (15.77s) cpu 2 4000 (14.20s) 3599 (15.78s) 3600 (15.77s) cpu 3 4000 (14.22s) 3599 (15.90s) 3600 (15.78s) cpu 4 3999 (14.18s) 3600 (16.11s) 3600 (15.76s) cpu 5 4000 (14.18s) 3600 (15.79s) 3600 (15.76s) cpu 6 3999 (14.19s) 3600 (15.79s) 3599 (15.76s) cpu 7 4000 (14.19s) 3600 (15.94s) 3600 (15.76s) CPU Workload Test: Expected Speedup: 0.00 Allowable Speedup: 0.50 to -0.49 Power Save -------- -------------- cpu 1 0.95 (3599 MHz Error Summary: ---------------- User Space (min): Error: cpu0 in package 0 has a measured frequency of 4000 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz User Space (min): Error: cpu1 in package 0 has a measured frequency of 4000 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz User Space (min): Error: cpu2 in package 0 has a measured frequency of 4000 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz User Space (min): Error: cpu3 in package 0 has a measured frequency of 4000 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz User Space (min): Error: cpu4 in package 0 has a measured frequency of 3999 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz User Space (min): Error: cpu5 in package 0 has a measured frequency of 4000 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz User Space (min): Error: cpu6 in package 0 has a measured frequency of 3999 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz User Space (min): Error: cpu7 in package 0 has a measured frequency of 4000 MHz vs. a requirement of 800000 MHz - 5000/+ 100 MHz FAIL Additional info: When we use Red Hat 7.2 the cpuscaling test is ok. The problem is that the redhat 7.2 kernel does not support Intel i7-7000 cpu...we got a TAINED kernel on INFO test. We try to update the 7.2 OS to use the kernel 7.3 but the problem remains the same...
Please try again using latest versions of redhat-certification redhat-certification-backend redhat-certification-hardware and let us know whether this issue is still present.