Bug 1320204
Summary: | depmod on ppc64le complains about kernel modules need unknown symbol .TOC. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Thomas Huth <thuth> |
Component: | kmod | Assignee: | Tony Camuso <tcamuso> |
Status: | CLOSED ERRATA | QA Contact: | Chunyu Hu <chuhu> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.3 | CC: | chuhu, hannsj_uhl, jfeeney, jshortt, lilu, mkolaja, skozina, thuth, xiaolli, xzhou |
Target Milestone: | rc | Keywords: | Patch |
Target Release: | --- | ||
Hardware: | ppc64le | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-03 23:55:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1274397 |
Description
Thomas Huth
2016-03-22 14:49:53 UTC
I am upgrading kmod to v22 with additional patches. Stay tuned ... Set ack+, sorry for the latency, as the default tester changed several times. Too late in the game to upgrade to V22, so I backported some upstream patches. Please try the kmod rpms at this link: http://people.redhat.com/tcamuso/kmod/ppc64le/ Please tell me if this fixes your problem. Yes, that fixes my problem, there are no more annoying "unknown symbol .TOC." messages during "make modules_install" with these RPMs, thanks! Pushed. remote: *** Checking commit f6f7779710ddb4857cbda9fbcba336a39ff49eb2 remote: *** Resolves: remote: *** Approved: remote: *** rhbz#1320204 (rhel-7.3.0+, pm_ack+) remote: *** Commit f6f7779710ddb4857cbda9fbcba336a39ff49eb2 allowed To ssh://tcamuso.redhat.com/rpms/kmod 542ca2d..f6f7779 rhel-7.3 -> rhel-7.3 Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=11283571 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://rhn.redhat.com/errata/RHBA-2016-2171.html |