This bug has been copied from bug #568032 and has been proposed to be backported to 5.5 z-stream (EUS).
As mentioned in comment 11 of bug 568032 (<https://bugzilla.redhat.com/show_bug.cgi?id=568032#c11>), this has been fixed in upstream commit 9ab564b and fc2a22c by adding support for sys_ia64_pipe. Fix for the syscalls2.stp tapset: <http://sources.redhat.com/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=9ab564b0a21f2df7d9457857cc636c621a2f7090> Fix for the nd_syscalls2.stp tapset: <http://sources.redhat.com/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=fc2a22c05edf578c05acb91d2f9d0d159c717061> These patches will need to be backported.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Although the kernel in Red Hat Enterprise Linux 5.5 for the Itanium architecture introduced a new pipe system call handler, "sys_ia64_pipe", the function was not added to the SystemTap tapset. As a result, probing the system call from the script via "probe syscall.pipe" did not succeed. This error has been fixed, the new function has been added to the tapset, and the pipe system call should now be probed correctly.
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-2010-0525.html