Bug 704412

Summary: cpuscaling test should be OK to starts the cpu's in any state
Product: [Retired] Red Hat Hardware Certification Program Reporter: QinXie <xiqin>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0CC: hwcert-reviewers, jweng, rlandry, ykun
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-01 19:14:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description QinXie 2011-05-13 03:47:14 UTC 
cpus start in different states should be a warning, but not an error. 

Belowing log shows it's reported as an error, but not a warning:
https://hardware.redhat.com/results.cgi?cert_id=697720&id=229501

<snip>
On Userspace Governor Test:
-------------------------------------------------
Setting governor to userspace
Error: cpu1 in package 0 has the value 1064000 which differs from other cpus in the package
Setting cpu frequency to 1064 MHz
Running CPU load test...
Running load test for package 0
starting process for cpu 0
starting process for cpu 1
starting process for cpu 2
......
......
......
</snip>
Comment 1 Jianwei Weng 2011-06-14 05:51:47 UTC 
As per https://hardware.redhat.com/show.cgi?id=697716#c42
The Error "Could not verify that cpu frequency has settled to the minimum value" should also be considered a warning instead of error? since the one causes the other.
Comment 2 Rob Landry 2011-07-01 19:14:01 UTC 

*** This bug has been marked as a duplicate of bug 699653 ***