Bug 747175

Summary: cpuscaling fail with Sandy Bridge i7 CPU to prompt "error: measured speedup vs expected speedup is 26.8% and is not within 10.0% margin".
Product: [Retired] Red Hat Hardware Certification Program Reporter: David <davi.wang>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED NOTABUG QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: rlandry
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: 2012-05-23 00:15:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
failed result for CPU i7 2600S & v7-1.4-38 none

Description David 2011-10-19 02:23:17 UTC 
Description of problem:
Cpuscaling always fails with Sandy Bridge i7 CPU and 6.1 x86/x64.

Version-Release number of selected component (if applicable):
v7-1.3-46.el6 and RH6.1 x86/x64 workstation 

How reproducible:

Steps to Reproduce:
1. Install OS either x86 or x64 with Sandy Bridge CPU i7-2600
2. Install v7-1.3 kit
3. Execute cpuscaling cert tests item.
  
Actual results:
cpuscaling fail to prompt "error: measured speedup vs expected speedup is 26.8% and is not within 10.0% margin".

Expected results:
pass

Additional info:
Comment 1 Rob Landry 2011-12-12 16:20:28 UTC 
Hi David,  the cpuscaling test received an update in the v7-1.4-48 test suite; can you retest with this update to verify if this continues to be an issue?
Comment 2 David 2011-12-13 02:15:53 UTC 
Hi Rob, do you mean v7-1.4-38 test suite? If sure, I have try it and still fail.
Comment 3 Rob Landry 2011-12-13 19:07:34 UTC 
Hi David,  can you attach the 1.4-38 failed results?
Comment 4 David 2011-12-16 05:31:29 UTC 
Created attachment 547605 [details]
failed result for CPU i7 2600S & v7-1.4-38
Comment 5 Rob Landry 2011-12-16 16:01:25 UTC 
The failure is reported because the cpu should be scaling to 2.8GHz but is only scaling to 1.9GHz with the user control maximum, performance, and ondemand governors; thus is it correct for the cpuscaling test to fail.  This is shown using the aperf/mperf register calculation as well as the time to complete.  Typically this is caused by a system BIOS issue.