Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
With kernel 2.6.32-71.18.2.el6 (RHEL6.0.z), these testcases from systemtap testsuite worked:
systemtap.examples/process/errsnoop build
buildok/syscall.stp
buildok/syscalls2-detailed.stp
With 6.1 candidate kernel 2.6.32-122.el6, these testcases fail with the following error:
semantic error: unable to find local 'arg' near pc 0xffffffff811bc0b0 in compat_sys_nfsservctl(fs/compat.c) (alternatives: $cmd $notused $notused2): identifier '$arg' at /usr/share/systemtap/tapset/syscalls2.stp:71:56
source: argstr = sprintf("%s, %p, %p", _nfsctl_cmd_str($cmd), $arg, $res)
^
Pass 2: analysis failed. Try again with another '--vp 01' option
Version-Release number of selected component (if applicable):
# rpm -q kernel systemtap-debuginfo systemtap
kernel-2.6.32-122.el6.x86_64
kernel-2.6.32-71.18.2.el6.x86_64
systemtap-1.4-4.el6.x86_64
systemtap-1.4-4.el6.x86_64
I've also checked this is not caused by elfutils (happens with both 6.0 and 6.1 candidate elfutils)
How reproducible:
always
Steps to Reproduce:
1. stap -p4 /usr/share/systemtap/testsuite/buildok/syscall.stp
Actual results:
fails to build
Expected results:
builds
I guess this is a matter of tapset adjustment.
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-0651.html
Description of problem: With kernel 2.6.32-71.18.2.el6 (RHEL6.0.z), these testcases from systemtap testsuite worked: systemtap.examples/process/errsnoop build buildok/syscall.stp buildok/syscalls2-detailed.stp With 6.1 candidate kernel 2.6.32-122.el6, these testcases fail with the following error: semantic error: unable to find local 'arg' near pc 0xffffffff811bc0b0 in compat_sys_nfsservctl(fs/compat.c) (alternatives: $cmd $notused $notused2): identifier '$arg' at /usr/share/systemtap/tapset/syscalls2.stp:71:56 source: argstr = sprintf("%s, %p, %p", _nfsctl_cmd_str($cmd), $arg, $res) ^ Pass 2: analysis failed. Try again with another '--vp 01' option Version-Release number of selected component (if applicable): # rpm -q kernel systemtap-debuginfo systemtap kernel-2.6.32-122.el6.x86_64 kernel-2.6.32-71.18.2.el6.x86_64 systemtap-1.4-4.el6.x86_64 systemtap-1.4-4.el6.x86_64 I've also checked this is not caused by elfutils (happens with both 6.0 and 6.1 candidate elfutils) How reproducible: always Steps to Reproduce: 1. stap -p4 /usr/share/systemtap/testsuite/buildok/syscall.stp Actual results: fails to build Expected results: builds I guess this is a matter of tapset adjustment.