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.
Description of problem:
Platform stress software and CPUID software are reading cache information via CPUID and find this bad descriptor:
Type of cache Unified Cache
Cache Level 0
Cache Level can't be 0 if cache type is non-zero.
Version-Release number of selected component (if applicable):
How reproducible:
Easily on Linux or Windows guest OS.
Steps to Reproduce:
1. Boot guest OS via KVM
2. Check CPUID cache descriptors
x86info -c seems to ignore the bad descriptor, so use something else
Actual results:
Type of cache Unified Cache
Cache Level 0
Expected results:
Type of cache = 0
Additional info:
(In reply to comment #0)
> Description of problem:
> Platform stress software and CPUID software are reading cache information via
> CPUID and find this bad descriptor:
>
> Type of cache Unified Cache
> Cache Level 0
>
> Cache Level can't be 0 if cache type is non-zero.
Hi,thomas
Would you please tell me which tool you used to read cache information and found bad descriptor?I tried cup-z & CPUID TMonitor.failed to get infos what you de scripted.thanks
Comment 3RHEL Program Management
2011-04-04 02:05:11 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
We don't have the option to configure the cache bits with the current cpu model design. We'll need the complete cpu-type infrastructure planned for RHEL7 (bug 824991) in order to properly fix this.
So deferring to RHEL7.
I can't locate the issue in the code and there's not enough information to reproduce the bug. Even the older RHEL-6 code looks correct and has level=2 in the only CPUID entry where cache type is 3 (unified cache).
Description of problem: Platform stress software and CPUID software are reading cache information via CPUID and find this bad descriptor: Type of cache Unified Cache Cache Level 0 Cache Level can't be 0 if cache type is non-zero. Version-Release number of selected component (if applicable): How reproducible: Easily on Linux or Windows guest OS. Steps to Reproduce: 1. Boot guest OS via KVM 2. Check CPUID cache descriptors x86info -c seems to ignore the bad descriptor, so use something else Actual results: Type of cache Unified Cache Cache Level 0 Expected results: Type of cache = 0 Additional info: