Systemtap testsuite report for arm architecture

["Bruno Abinader" <bruno dot abinader at openbossa dot org>]

Hi all,
We at INdT made a few tests using systemtap on maemo devices (arm
architecture). For these results, it was used the Systemtap snapshot
20081201 and elfutils 0.131.

Results for 20080201:
                 === systemtap Summary ===

 # of expected passes            367
 # of unexpected failures        68
 # of unexpected successes       1
 # of expected failures          153
 # of known failures             6
 # of untested testcases         15
 # of unsupported tests          4
 runtest completed at Fri Feb  1 15:28:08 2008

 On the failed tests, some of them were caused due to timeout. All others
 errors were commented below:

 FAIL: cmd_parse6: unexpected EOF
 -----------------------------------------------------
 This test gives EOF because systemtap was unable to evaluate the
 following sentence:
 stap -c '(((a=42+7)); echo "The answer is $a")' -e 'probe begin {}'
 The correct output is: "The answer is 49" but console output shown "The
 answer is" without number.

 FAIL: systemtap.base/deref.stp startup (eof)
 ---------------------------------------------------------------
 Fails to compile on ARM. Looks like a bug on ARM-specific read/write
 memory addresses code. According to the test failure, what do not work
 on ARM are: Write to a kernel space memory address using kwrite() (not
 used in any of current tapsets) and reading uint64_t values using
 kread().

 FAIL: OVERLOAD2 didn't receive expected overload
 ---------------------------------------------------------------------------
 Affects systemtap's CPU overload protection, with may not work properly
 on ARM.
 This failure is related with bug 4569
 (http://sources.redhat.com/bugzilla/show_bug.cgi?id=4569)

 FAIL: probefunc:kernel.statement(0xc0055598).absolute shutdown (eof)
 -------------------------------------------------------------------------------------------------------
 probefunc() function is not working on ARM. It is used to return probe
 point's function name, if known.

 FAIL: warnings (timeout)
 -----------------------------------
 The experiment expect 6 warnings at parsing stage, but only 5 appeared:

 WARNING: eliding unused function identifier 'elide_me2' at
 warnings.stp:5:10
 WARNING: eliding unused variable identifier 'elide_me1' at
 warnings.stp:3:8
 WARNING: eliding unused variable identifier 'elide_me4' at
 warnings.stp:9:15
 WARNING: eliding unused variable identifier 'elide_me5' at
 warnings.stp:9:31
 WARNING: eliding unused variable identifier 'elide_me3' at
 warnings.stp:7:24
 This can be ignored.

 FAIL: backtrace - could not build modules
 FAIL: args - could not build modules
 FAIL: pid - could not build modules
 --------------------------------------------------
 stap was unable to find "systemtap_test_module2" on ARM.

 'backtrace' stap output:
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_func3").call
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_func4").return

 'args' stap output:
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_int")
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_int").return
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_uint")
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_uint").return
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_long")
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_long").return
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_int64")
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_int64").return
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_char")
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_char").return
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_str")
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_str").return

 'pid' stap output:
 semantic error: no match while resolving probe point
 module("systemtap_test_module2").function("yyy_int")

 FAIL: buildok/eighteen.stp
 -------------------------------------
 CONFIG_AUDITSYSCALL was disabled in kernel compilation, which is not
 available for ARM. Can be ignored.

 FAIL: buildok/scheduler-all-probes.stp
 ------------------------------------------------------
 Fails with the following output:
 semantic error: no match while resolving probe point
 kernel.function("__switch_to")

 FAIL: buildok/seventeen.stp
 ----------------------------------------
 Fails with the following output:
 semantic error: cannot relocate user-space dso (?) address: identifier
 '$write_fifo_fops' at seventeen.stp:8:19

 FAIL: buildok/nfs-all-probes.stp
 FAIL: buildok/nfsd-all-probes.stp
 ----------------------------------------------
 Kernel modules nfs, sunrpc and others come from the package
 rx-34-kernel-modules-extra. This package was installed using apt-get, so
 it was not compiled together with the kernel configs used in this tests.
 We believe it is the cause for some failed tests, because these modules
 don't have necessary DWARF information for debbuging. We've tried to
 build these modules on our own with "=m" option inside .config, but
 still the same error appears.

 FAIL: buildok/vfs-all-probes.stp
 FAIL: buildok/syscall.stp
 FAIL: buildok/tcp_test.stp
 FAIL: buildok/udp_test.stp
 FAIL: systemtap.samples/tcptest.stp compilation
 FAIL: pfaults (0)
 FAIL: semok/twentyseven.stp
 ------------------------------------------
 All these tests fail with a "semantic error: failed to retrieve return
 value location" error, due to missing return value locations support for
 ARM in elfutils backend. This issue also affects all LKET modules, so
 LKET is not working on ARM.

 FAIL: systemtap.samples/ioblocktest.stp shutdown (eof)
 ---------------------------------------------------------------------------------
 Test initially fails because it depends on direct block I/O activity.
 This can be triggered by reading directly from /dev/mtdblock4 using
 "dd". This will then trigger the mentioned bug. Due to this, block I/O
 tapset (ioblock.stp) does not work on ARM.
 This failure is related with bug 4592
 (http://sources.redhat.com/bugzilla/show_bug.cgi?id=4592)

 FAIL: transok/tval-opt.stp
 ------------------------------------
 Fails with the following output:
 semantic error: Expecting symbol or array index expression: identifier
 '$keycode' at <input>:1:58
 semantic error: unexpected type: identifier '$keycode' at <input>:1:44
 semantic error: failed to retrieve location attribute for local
 'keycode' (dieoffset: 0x9ec239): identifier '$keycode' at <input>:1:44

 FAIL: iostat-scsi.stp
 -----------------------------
 Fails with the following output:
 iostat-scsi.stp:
 semantic error: no match while resolving probe point
 kernel.function("st_do_scsi")
 This failure is related with bug 5422
 (http://sourceware.org/bugzilla/show_bug.cgi?id=5422)

 FAIL: iotime.stp
 FAIL: sys.stp
 FAIL: proc_snoop.stp
 -------------------------------
 Fails because of buggy $return on arm architecture:

 iotime.stp:
 semantic error: failed to retrieve return value location: identifier
 '$return' at iotime.stp:60:7

 sys.stp:
 semantic error: failed to retrieve return value location: identifier
 '$return' at /usr/share/systemtap/tapset/syscalls.stp:116:32

 proc_snoop.stp:
 semantic error: failed to retrieve return value location: identifier
 '$return' at iotime.stp:60:7

 FAIL: conversions.stp 0xffffffff (6)
 FAIL: conversions.stp 0xffffffffffffffff (6)
 -----------------------------------------------------
 This test depends on architecture-specific memory addressing
 conventions. There is no special treatment for ARM in this case. This
 failure does not affect SystemTap functionality.
 This failure is related with bug 5908
 (http://sourceware.org/bugzilla/show_bug.cgi?id=5908)

 FAIL: systemtap.stress/current.stp compilation
 --------------------------------------------------------------------
 Systemtap does not support probes for assembly functions.
 This failure is related with bug 4331
 (http://sourceware.org/bugzilla/show_bug.cgi?id=4331) and 4843
 ((http://sourceware.org/bugzilla/show_bug.cgi?id=4843)

 []s, and sorry for the long mail!

-- 
Bruno de Oliveira Abinader
Mobile Linux Software (MLS) / Instituto Nokia de Tecnologia (INdT)