Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 692177

Summary: sysconf(_SC_*CACHE) returns 0 for all caches on some CPUs.
Product: Red Hat Enterprise Linux 6 Reporter: john.haxby <john.haxby>
Component: glibcAssignee: Andreas Schwab <schwab>
Status: CLOSED ERRATA QA Contact: qe-baseos-tools-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0CC: fweimer, mfranc, pmuller, syeghiay
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glibc-2.12-1.25.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 13:16:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Variation of the patch posted upstream to use cpuid 4 rather than cpuid 2 when possible none

Description john.haxby@oracle.com 2011-03-30 15:57:52 UTC
Created attachment 488813 [details]
Variation of the patch posted upstream to use cpuid 4 rather than cpuid 2 when possible

Description of problem:
  The mechanism that sysconf(3) uses to get the various CACHE parameters
  fails on the Xen 5670

Version-Release number of selected component (if applicable): 2.12-1.7.el6_0.4

How reproducible:
  Every time

Steps to Reproduce:
1.  Find a machine whose /proc/cpuinfo starts something like this:

  vendor_id       : GenuineIntel
  cpu family      : 6
  model           : 44
  model name      : Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz
  stepping        : 2

2. run "getconf -a | grep CACHE"
3. Observe values printed
  
Actual results:
  All the cache parameter values are zero.

Expected results:
  Non-zero values for all but the level 4 cache

Additional info:
  Recent CPUs no longer have useful cpuid leaf 2 cache descriptors.  For this
  particular machine, cpuid 2 returns 0x55035a01 0xf0b2ff 0x0 0xca0000 in eax,
  ebx, ecx and edx respectively.  The 0xff in the least significant byte of
  ebx indicates that you need to use cpuid leaf 4.  Actually, for all but
  somewhat old CPUs you're better off using cpuid leaf 4 anyway (the only
  machines I have access to that have a cpuid level less than four are a
  "Intel(R) Pentium(R) 4 CPU 1.70GHz" and "Intel(R) Pentium(R) 4 CPU 2.40GHz"
  both of which are long past their use-by date).

Comment 5 errata-xmlrpc 2011-05-19 13:16:31 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0584.html