Bug 875988

Summary: Linux in ACPI mode not working properly on Shuttle SH55J2 + i7-870
Product: [Fedora] Fedora Reporter: J. Bruce Fields <bfields>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: gansalmon, itamar, jonathan, kernel-maint, len.brown, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-01 13:10:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description J. Bruce Fields 2012-11-13 01:32:49 UTC
When booting with intel_idle.max_cstate=0, c-states aren't used:

# ./turbostat -M 0xe2 sleep 1
cor CPU    %c0  GHz  TSC           MSR 0x0E2    %c1    %c3    %c6   %pc3   %pc6
          2.13 1.20 2.93  0x0000000000000000  97.87   0.00   0.00   0.00   0.00
  0   0   3.61 1.20 2.93  0x0000000000000003  96.39   0.00   0.00   0.00   0.00
  0   4   1.47 1.20 2.93  0x0000000000000003  98.53
  1   1   6.14 1.20 2.93  0x0000000000000003  93.86   0.00   0.00
  1   5   0.12 1.20 2.93  0x0000000000000003  99.88
  2   2   0.42 1.20 2.93  0x0000000000000003  99.58   0.00   0.00
  2   6   0.02 1.20 2.93  0x0000000000000003  99.98
  3   3   5.21 1.20 2.93  0x0000000000000003  94.79   0.00   0.00
  3   7   0.05 1.20 2.93  0x0000000000000003  99.95
1.001825 sec

and turbostat run concurrently with a "cat /dev/zero >/dev/null &" shows the cpu never exceeding 3.2GHz.

See bug 715485 for more background.

Comment 1 Josh Boyer 2013-04-01 19:44:42 UTC
Is this still an issue with 3.8.x?

Comment 2 Josh Boyer 2013-07-01 13:10:27 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.