Bug 704412 - cpuscaling test should be OK to starts the cpu's in any state
Summary: cpuscaling test should be OK to starts the cpu's in any state
Keywords:
Status: CLOSED DUPLICATE of bug 699653
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Test Suite (tests)
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Greg Nichols
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-13 03:47 UTC by QinXie
Modified: 2011-07-01 19:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-01 19:14:01 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.