Ubuntu
systemtap package

natty: systemtap incompatible with kernel

Bug #721771 reported by Uwe Geuder
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemtap (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: systemtap

Systemtap module compilation fails with

error: ‘param_ops_int64_t’ undeclared here (not in a function)

This has been reported and also fixed upstream: http://sourceware.org/bugzilla/show_bug.cgi?id=11940

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: systemtap 1.3-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5
Uname: Linux 2.6.38-4-generic i686
Architecture: i386
Date: Sat Feb 19 15:21:32 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110218)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: systemtap

Related branches

lp:~f-turgis/ubuntu/natty/systemtap/systemtap.2.6.38
Ubuntu branches: Pending requested
Diff: 10383 lines (+9776/-122)
47 files modified
.pc/01-Add-irq.stp-to-Tapset-Reference-manual.patch/doc/SystemTap_Tapset_Reference/tapsets.tmpl (+286/-0)
.pc/01-Add-irq.stp-to-Tapset-Reference-manual.patch/tapset/irq.stp (+172/-0)
.pc/02-Fixed-PR12338-by-updating-softirq.entry-softirq.exit.patch/tapset/irq.stp (+152/-0)
.pc/02-Fixed-PR12338-by-updating-softirq.entry-softirq.exit.patch/testsuite/buildok/irq-detailed.stp (+46/-0)
.pc/Fix-for-undefined-STAPCONF_PERF_STRUCTPID.patch/runtime/perf.c (+86/-0)
.pc/Fixed-PR11940-by-getting-scripts-w-global-variables-.patch/runtime/runtime.h (+204/-0)
.pc/Local-definitions-of-NIPQUAD-and-NIPQUAD_FMT-when-re.patch/tapset/ip.stp (+86/-0)
.pc/Local-definitions-of-NIPQUAD-and-NIPQUAD_FMT-when-re.patch/testsuite/systemtap.examples/process/pfiles.stp (+612/-0)
.pc/Updated-__ip_sock_daddr-for-2.6.38-kernels.patch/tapset/ip.stp (+96/-0)
.pc/Updated-memory.stp-rpc.stp-task.stp-and-vfs.stp-for-.patch/tapset/memory.stp (+635/-0)
.pc/Updated-memory.stp-rpc.stp-task.stp-and-vfs.stp-for-.patch/tapset/rpc.stp (+1185/-0)
.pc/Updated-memory.stp-rpc.stp-task.stp-and-vfs.stp-for-.patch/tapset/task.stp (+384/-0)
.pc/Updated-memory.stp-rpc.stp-task.stp-and-vfs.stp-for-.patch/tapset/vfs.stp (+1018/-0)
.pc/Use-linux-blk_types.h-and-REQ_WRITE-for-2.6.36-and-n.patch/buildrun.cxx (+650/-0)
.pc/Use-linux-blk_types.h-and-REQ_WRITE-for-2.6.36-and-n.patch/tapset/ioblock.stp (+316/-0)
.pc/adding-ifdef-CLONE_STOPPED-to-stop-module-compilatio.patch/tapset/aux_syscalls.stp (+2048/-0)
.pc/applied-patches (+10/-0)
.pc/compatibility-perf_event.h-updates-for-kernel-2.6.37.patch/buildrun.cxx (+651/-0)
.pc/compatibility-perf_event.h-updates-for-kernel-2.6.37.patch/runtime/perf.c (+81/-0)
buildrun.cxx (+2/-0)
debian/changelog (+8/-0)
debian/patches/01-Add-irq.stp-to-Tapset-Reference-manual.patch (+210/-0)
debian/patches/02-Fixed-PR12338-by-updating-softirq.entry-softirq.exit.patch (+72/-0)
debian/patches/Fix-for-undefined-STAPCONF_PERF_STRUCTPID.patch (+25/-0)
debian/patches/Fixed-PR11940-by-getting-scripts-w-global-variables-.patch (+57/-0)
debian/patches/Local-definitions-of-NIPQUAD-and-NIPQUAD_FMT-when-re.patch (+60/-0)
debian/patches/Updated-__ip_sock_daddr-for-2.6.38-kernels.patch (+37/-0)
debian/patches/Updated-memory.stp-rpc.stp-task.stp-and-vfs.stp-for-.patch (+214/-0)
debian/patches/Use-linux-blk_types.h-and-REQ_WRITE-for-2.6.36-and-n.patch (+60/-0)
debian/patches/adding-ifdef-CLONE_STOPPED-to-stop-module-compilatio.patch (+26/-0)
debian/patches/compatibility-perf_event.h-updates-for-kernel-2.6.37.patch (+68/-0)
debian/patches/series (+10/-0)
doc/SystemTap_Tapset_Reference/tapsets.tmpl (+10/-0)
runtime/autoconf-blk-types.c (+2/-0)
runtime/autoconf-perf-structpid.c (+14/-0)
runtime/perf.c (+6/-1)
runtime/runtime.h (+14/-3)
tapset/aux_syscalls.stp (+2/-0)
tapset/ioblock.stp (+6/-1)
tapset/ip.stp (+18/-5)
tapset/irq.stp (+62/-74)
tapset/memory.stp (+2/-1)
tapset/rpc.stp (+8/-6)
tapset/task.stp (+10/-12)
tapset/vfs.stp (+41/-18)
testsuite/buildok/irq-detailed.stp (+1/-1)
testsuite/systemtap.examples/process/pfiles.stp (+13/-0)
lp:ubuntu/oneiric/systemtap
Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :
Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :

Because systemtap package does not declare the dependecy on the kernel debug info correctly, obviously apport-bug has not included the relevant info either. But yes I have correct kernel debug info installed:

 ii linux-image-2.6.38-4-generic-dbgsym 2.6.38-4.31 Linux kernel debug image for version 2.6.38 on x86/x86_64

Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :

Commit 75a48ca3 mentioned in the upstream bug report applies cleanly to the systemtap source in natty and solves the problem with

error: ‘param_ops_int64_t’ undeclared here (not in a function)

I tried 2 simple system tap scripts: 1 succeeded and 1 failed. The new error is:

error: 'CLONE_STOPPED’ undeclared here (not in a function)

Upstream there is a changelog entry

> Wed Jan 19 2011 Frank Ch. Eigler <email address hidden>
> - 1.4-3 - adapt to kernel CLONE_STOPPED deprecation

Haven't had time to look into that yet. But from the changelog text I guess it's the same problem again. The systemtap version in natty is just too old to work with the natty kernel.

Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) wrote :

The second problem

error: 'CLONE_STOPPED’ undeclared here (not in a function)

is fixed by upstream commit b30b7ed1.

All my tests are successful for the moment (that doesn't tell much, I have used only very simple scripts)

Revision history for this message
Frederic Turgis (f-turgis) wrote :

was about to enter the same defect, tested on arm architecture. I faced the "error: ‘param_ops_int64_t’ undeclared here (not in a function)" and also applied redhat fix. The scripts I tested after were essentially home-made, related to scheduler context switches, v4l2 monitoring, ... while using "expert" mode where C-code is embedded in the scripts.
I tried v1.4 but it was not 100% OK for arm (and it does not include the "CLONE_STOPPED" fix): there is a warning at kernel module compilation and warnings are handled as errors (64-bit constant truncated to 32-bit). Redhat is currently looking at this issue

Revision history for this message
Frederic Turgis (f-turgis) wrote :

By running testsuite on ARM, I have identified a set of upstream patches for 2.6.37 kernel + new fixes from Redhat for 2.6.38 when we mentioned our test results on their mailing list. Will submit new package

v1.4 issue is understood as a wrong management of .note.gnu.build-id section in linker command file. ARM has fixed it by using NOTES macro http://ftp.arm.linux.org.uk/git/gitweb.cgi?p=linux-2.6-arm.git;a=commitdiff;h=dc810efb0ca5702c9d + Redhat will repair a broken fix around this topic (but ARM change is sufficient)

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package systemtap - 1.3-2ubuntu2

---------------
systemtap (1.3-2ubuntu2) natty; urgency=low

  * Added upstream patches for kernels 2.6.37/2.6.38, identified after
    running testsuite (LP: #721771)
 -- Frederic Turgis <email address hidden> Thu, 17 Mar 2011 12:25:48 +0000

Changed in systemtap (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.