Bug 559599
Summary: | Errata testing: buildok/fortyfive.stp FAIL (ia64) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Petr Muller <pmuller> |
Component: | systemtap | Assignee: | Frank Ch. Eigler <fche> |
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-tools-bugs |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.5 | CC: | dsmith, mjw, ohudlick |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | ia64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | systemtap-1.3-5.el5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-07-21 11:10:57 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Petr Muller
2010-01-28 15:15:52 UTC
For ia64, the problem is similar to bug #669740. The tapset/target_set.stp file was switched from using syscall probes to nd_syscall syscall probes (which map to dwarfless 'kprobe.function' probes). The ia64 platform doesn't support dwarfless probes (see upstream bug 6971 <http://sources.redhat.com/bugzilla/show_bug.cgi?id=6971>). The easiest solution for ia64 would be to extend the patch that fixed bug #669740 and fall back to syscall probes for ia64. From testing systemtap-1.3-4.el5 on s390x, buildok/fortyfive.stp no longer gets a compilation error. So certainly for s390x this is CLOSED/CURRENTRELEASE. I couldn't find a ppc64 machine to test on, but I'd bet that buildok/fortyfive.stp works with systemtap-1.3-4.el5 there also. That only leaves us with ia64, where buildok/fortyfive.stp is still broken with systemtap-1.3-4.el5. This has been fixed upstream by applying the following 2 commits (which will need to be backported to 1.3): commit 4ec30a2 (which fixed bug #669740): <http://sources.redhat.com/git/gitweb.cgi?p=systemtap.git;a=patch;h=4ec30a2e5dd462bddce36728de7332fd0942bd31> commit 1916e83 (which fixes the ia64 specific problem): <http://sources.redhat.com/git/gitweb.cgi?p=systemtap.git;a=patch;h=1916e8381d5c7d6a06d6b19abeca32ad2f1cef78> 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/RHBA-2011-1044.html |