Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1445473 - lshw fails to enumerate all CPUS on an Intel Phi based system
lshw fails to enumerate all CPUS on an Intel Phi based system
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lshw (Show other bugs)
7.4
All Linux
unspecified Severity high
: rc
: ---
Assigned To: Petr Oros
Mike Gahagan
:
: 1456533 (view as bug list)
Depends On:
Blocks: 1400036 1449793 1456469 1461180 1469549 1472889 1477926 1478963 1522983
  Show dependency treegraph
 
Reported: 2017-04-25 14:11 EDT by Mike Gahagan
Modified: 2018-04-10 06:03 EDT (History)
4 users (show)

See Also:
Fixed In Version: lshw-B.02.18-8.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 06:03:13 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
console log (62.88 KB, application/octet-stream)
2018-02-14 06:01 EST, IBM Bug Proxy
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0689 None None None 2018-04-10 06:03 EDT

  None (edit)
Description Mike Gahagan 2017-04-25 14:11:00 EDT
Description of problem:

CPU/core count stops at 255 when the system in fact has 272 cores

Version-Release number of selected component (if applicable):
lshw-B.02.18-4.el7

How reproducible:
always

Steps to Reproduce:
1.run lshw and compare with /proc/cpuinfo and other tools
2.
3.

Actual results:


Expected results:


Additional info:
Comment 4 Petr Oros 2017-11-06 09:40:01 EST
*** Bug 1456533 has been marked as a duplicate of this bug. ***
Comment 5 IBM Bug Proxy 2017-11-06 10:00:38 EST
------- Comment From hegdevasant@in.ibm.com 2017-06-01 23:19 EDT-------
Hello RedHat,

RHEL 7.4 contains all the patches of our interest. This is a placeholder FEAT to push any new changes (specifically for Power9)

-Vasant
Comment 6 Mike Gahagan 2017-11-06 10:39:28 EST
Hi Vasant,

IBM may be linking to the wrong bz here. This bug was to track a defect in lshw with respect to an x86_64 based system. We should be tracking the power specific feature in another bug.
Comment 7 Hanns-Joachim Uhl 2017-11-06 11:10:33 EST
(In reply to Mike Gahagan from comment #6)
> Hi Vasant,
> 
> IBM may be linking to the wrong bz here. This bug was to track a defect in
> lshw with respect to an x86_64 based system. We should be tracking the power
> specific feature in another bug.

.
Hello Red Hat / Mike,
... yes, the related POWER specific feature is
RHBZ bug 1456533 - [IBM 7.5 FEAT] lshw update for ppc64le ...
... but that bugzilla was duped to this bugzilla ...
Thanks for your attention and support.
Comment 8 Mike Gahagan 2017-12-04 14:24:43 EST
Confirmed lshw-B.02.18-9.el7.x86_64 is shipping with 7.5 which has the requested upstream changes. Please open new bugs for any issues found.
Comment 9 IBM Bug Proxy 2018-02-14 06:01:02 EST
Created attachment 1395843 [details]
console log
Comment 10 Hanns-Joachim Uhl 2018-02-23 05:05:09 EST
(In reply to Hanns-Joachim Uhl from comment #7)
> (In reply to Mike Gahagan from comment #6)
> > Hi Vasant,
> > 
> > IBM may be linking to the wrong bz here. This bug was to track a defect in
> > lshw with respect to an x86_64 based system. We should be tracking the power
> > specific feature in another bug.
> 
> .
> Hello Red Hat / Mike,
> ... yes, the related POWER specific feature is
> RHBZ bug 1456533 - [IBM 7.5 FEAT] lshw update for ppc64le ...
> ... but that bugzilla was duped to this bugzilla ...
> Thanks for your attention and support.
.
fyi ... this feature request is verified with RHEL7.5 Snapshot 4 ... thanks ...
Comment 13 errata-xmlrpc 2018-04-10 06:03:13 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:0689

Note You need to log in before you can comment on or make changes to this bug.