Red Hat Bugzilla – Bug 797576
Update hwloc to latest stable upstream
Last modified: 2013-02-21 05:42:59 EST
Description of problem:
hwloc 1.4 is now available upstream. What are the plans to update hwloc in RHEL6?
I maintain hwloc package for Fedora and I can can make new package "hwloc14" available for EPEL6 if there are no plans to update hwloc in RHEL6.
I can request an update for 6.4 and see if it gets approved. I won't know for a few months though.
it sounds like a good plan. Please let us know the status once 6.4 is finalized.
I will update this bz when I get new info.
I have updated to v1.5 and will push that out to 6.4 barring any unforseen issues.
*** Bug 757759 has been marked as a duplicate of this bug. ***
hwloc 1.5.1 was released on October 17th:
I am curious if we want to package that instead or stick with 1.5?
The Hardware Locality (hwloc) team is pleased to announce the release
v1.5.1 is a bug fix release which addresses all known bugs in the
* Fix block OS device detection on Linux kernel 3.3 and later.
Thanks to Guy Streeter for reporting the problem and testing the fix.
* Fix the cpuid code in the x86 backend (for FreeBSD). Thanks to
Sebastian Kuzminsky for reporting problems and testing patches.
* Fix 64bit detection on FreeBSD.
* Fix some corner cases in the management of the thissystem flag with
respect to topology flags and environment variables.
* Fix some corner cases in command-line parsing checks in hwloc-distrib
* Make sure we do not miss some block OS devices on old Linux kernels
when a single PCI device has multiple IDE hosts/devices behind it.
* Do not disable I/O devices or instruction caches in hwloc-assembler output.
I definitely agree that it makes sense to go for 1.5.1
I have updated master branch of hwloc for Fedora in case that anybody would like to test 1.5.1. My local tests all went through.
Automated and manual testing succeeded
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.