| Summary: | cpu socket detection fails on some 5.7 i386 boxes | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Adrian Likins <alikins> |
| Component: | subscription-manager | Assignee: | Adrian Likins <alikins> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.7 | CC: | cduryee, jsefler |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-21 08:45:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 675214 | ||
|
Description
Adrian Likins
2011-05-24 15:57:27 UTC
The box I've seen with no topology/ info appears to be a p4 zen dom0, so this might be a xen kernel thing. a patch is out for review commit 2a89d48fe747411f8c79038988292a3690691e36
Author: Adrian Likins <alikins>
Date: Tue May 24 16:53:19 2011 -0400
707292: Better counting of cpu sockets
Look for physical_package_id if it exists. Handle it not being
there for all cpu cores (i386 guest on x86_64 kvm guest).
Handle it not existing at all (xen dom0).
If all else fails, claim we have one cpu socket.
fixed in 2a89d48, rhel5.7 branch v 0.95.5.19 Partial Verification on s390x hardware where detection of the number of cpu sockets has been failing (see bug 696791).... [root@ibm-z10-12 tmp]# uname -a Linux ibm-z10-12.rhts.eng.bos.redhat.com 2.6.18-262.el5 #1 SMP Mon May 16 17:52:56 EDT 2011 s390x s390x s390x GNU/Linux [root@ibm-z10-12 tmp]# rpm -q subscription-manager subscription-manager-0.95.5.19-1.git.2.2a89d48.el5 [root@ibm-z10-12 tmp]# subscription-manager facts --list cpu.core(s)_per_socket: 2 cpu.cpu(s): 2 cpu.cpu_socket(s): 1 distribution.id: Tikanga distribution.name: Red Hat Enterprise Linux Server distribution.version: 5.7 memory.memtotal: 508952 memory.swaptotal: 1048568 net.interface.eth0.broadcast: 10.16.71.255 net.interface.eth0.hwaddr: 02:de:ad:be:ef:0c net.interface.eth0.ipaddr: 10.16.66.203 net.interface.eth0.netmask: 255.255.248.0 net.interface.lo.broadcast: 0.0.0.0 net.interface.lo.hwaddr: 00:00:00:00:00:00 net.interface.lo.ipaddr: 127.0.0.1 net.interface.lo.netmask: 255.0.0.0 net.interface.sit0.broadcast: unknown net.interface.sit0.hwaddr: 00:00:00:00:00:00 net.interface.sit0.ipaddr: unknown net.interface.sit0.netmask: unknown network.hostname: ibm-z10-12.rhts.eng.bos.redhat.com network.ipaddr: 10.16.66.203 system.entitlements_valid: False uname.machine: s390x uname.nodename: ibm-z10-12.rhts.eng.bos.redhat.com uname.release: 2.6.18-262.el5 uname.sysname: Linux uname.version: #1 SMP Mon May 16 17:52:56 EDT 2011 virt.host_type: ibm_systemz ibm_systemz-zvm virt.is_guest: True The fix for this bugzilla is a partial continuation of the story from https://bugzilla.redhat.com/show_bug.cgi?id=696791#c4 Notice in the facts above, that on s390 the number of sockets is now set to 1 (presumably when detection of this hardware property fails as indicated in comment #3). With respect to subscription availability based on sockets, this is a gracious default value. Recreate/Verification of this bug is somewhat tricky. Here we go... Using beaker (jobs/90124) to provision an i386 machine with the kernel-xen... [root@dell-pe1650-02 ~]# uname -a Linux dell-pe1650-02.rhts.eng.bos.redhat.com 2.6.18-264.el5xen #1 SMP Tue May 24 15:28:04 EDT 2011 i686 i686 i386 GNU/Linux Now let's recreate the problem... [root@dell-pe1650-02 ~]# ls /sys/devices/system/cpu/ cpu0 cpu1 [root@dell-pe1650-02 ~]# ls /sys/devices/system/cpu/cpu0/ crash_notes topology [root@dell-pe1650-02 ~]# ls /sys/devices/system/cpu/cpu0/topology/ [root@dell-pe1650-02 ~]# ls /sys/devices/system/cpu/cpu1 crash_notes online topology [root@dell-pe1650-02 ~]# ls /sys/devices/system/cpu/cpu1/topology/ [root@dell-pe1650-02 ~]# [root@dell-pe1650-02 ~]# for cpu in `ls -1 /sys/devices/system/cpu/ | egrep cpu[[:digit:]]`; do echo \"cpu `cat /sys/devices/system/cpu/$cpu/topology/physical_package_id`\"; done | grep cpu | uniq | wc -l cat: /sys/devices/system/cpu/cpu0/topology/physical_package_id: No such file or directory cat: /sys/devices/system/cpu/cpu1/topology/physical_package_id: No such file or directory 1 ^^^ Note there is no physical_package_id file on this hardware, therefore subscription-manger does not know how to count the sockets... Let's verify that subscription-manager-0.95.5.18-1.el5 (built before the fix for this bug) will NOT report a system fact for cpu_socket [root@dell-pe1650-02 ~]# rpm -q subscription-manager subscription-manager-0.95.5.18-1.el5 [root@dell-pe1650-02 ~]# subscription-manager facts --list | grep cpu [root@dell-pe1650-02 ~]# ^^^ Verified the re-create that no cpu facts are known to subscription-manager Now, let's install subscription-manager with this bug fix... [root@dell-pe1650-02 ~]# rpm -q subscription-manager subscription-manager-0.95.5.19-1.git.2.2a89d48.el5 [root@dell-pe1650-02 ~]# subscription-manager facts --list | grep cpu cpu.core(s)_per_socket: 2 cpu.cpu(s): 2 cpu.cpu_socket(s): 1 [root@dell-pe1650-02 ~]# ^^^ Verified that subscription provides a sockets value of 1 in case when topology/physical_package_id does not exist at all (xen dom0) 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/RHEA-2011-1078.html 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/RHEA-2011-1078.html |