Test results of systemtap snapshot for Week 17 on kernel 2.6.30-rc2-next-20090420 on RHEL 5.3 on s390x

Test results of systemtap snapshot for Week 17 on kernel 2.6.30-rc2-next-20090420 on RHEL 5.3 on s390x

[maranp]

Hi,

Summary report of Snapshot: version 0.9.5/0.140.90 commit 7a2ee7a2 + changes
Arch: s390x

  === systemtap Summary ===

# of expected passes            637
# of unexpected failures        58
# of unexpected successes       8
# of expected failures          203
# of known failures             7
# of untested testcases         51
# of unsupported tests          2

Unexpected failures
=============================

FAIL: LOCAL1 (2)
FAIL: backtrace (1 0)
FAIL: backtrace-unwindsyms (1 0)
FAIL: debugpath-good (eof)
FAIL: systemtap.base/kmodule.stp startup (eof)
FAIL: MAXACTIVE02 compilation
FAIL: compiling sdt.c ""
FAIL: compiling sdt.c additional_flags=-std=gnu89
FAIL: compiling sdt.c additional_flags=-ansi
FAIL: compiling sdt.c additional_flags=-pedantic
FAIL: compiling sdt.c additional_flags=-ansi additional_flags=-pedantic
FAIL: compiling sdt.c additional_flags=-O2
FAIL: compiling sdt.c additional_flags="-O3"
FAIL: skip tracking (2 0)
FAIL: static_uprobes compiling C -g
FAIL: backtrace of yyy_func2 (2)
FAIL: print_stack of yyy_func2 (2)
FAIL: backtrace of yyy_func3 (2)
FAIL: print_stack of yyy_func3 (2)
FAIL: backtrace of yyy_func4 (2)
FAIL: print_stack of yyy_func4 (2)
FAIL: integer function arguments -- numeric
FAIL: unsigned function arguments -- numeric
FAIL: long function arguments -- numeric
FAIL: int64 function arguments -- numeric
FAIL: char function arguments -- numeric
FAIL: string function arguments -- numeric
FAIL: integer function arguments -- numeric --kelf --ignore-dwarf
FAIL: unsigned function arguments -- numeric --kelf --ignore-dwarf
FAIL: long function arguments -- numeric --kelf --ignore-dwarf
FAIL: int64 function arguments -- numeric --kelf --ignore-dwarf
FAIL: char function arguments -- numeric --kelf --ignore-dwarf
FAIL: string function arguments -- numeric --kelf --ignore-dwarf
FAIL: systemtap.examples/general/para-callgraph build
FAIL: systemtap.examples/general/para-callgraph run
FAIL: buildok/four.stp
FAIL: buildok/maxactive01.stp
FAIL: buildok/nfsd-all-probes.stp
FAIL: buildok/scheduler-all-probes.stp
FAIL: buildok/scsi-all-probes.stp
FAIL: buildok/scsi.stp
FAIL: buildok/seventeen.stp
FAIL: buildok/twentyfive.stp
FAIL: semok/twentyeight.stp
FAIL: semok/twentyfour.stp
FAIL: semok/twentyseven.stp
FAIL: transok/tval-opt.stp
FAIL: systemtap.printf/bin6.stp
FAIL: systemtap.printf/memory1.stp
FAIL: systemtap.stress/current.stp compilation
FAIL: 64-bit acct
FAIL: 64-bit mmap
FAIL: 64-bit net1
FAIL: 64-bit signal
FAIL: 32-bit acct
FAIL: 32-bit net1
FAIL: 32-bit signal
FAIL: 32-bit statfs

Regards,
Maran Pakkirisamy,
IBM ISTL - Linux Technology Center

Re: Test results of systemtap snapshot for Week 17 on kernel 2.6.30-rc2-next-20090420 on RHEL 5.3 on s390x

[Mark Wielaard]

Hi Maran,

On Fri, 2009-04-24 at 01:05 -0400, maranp@linux.ibm.com wrote:
> Summary report of Snapshot: version 0.9.5/0.140.90 commit 7a2ee7a2 + changes
> Arch: s390x

If you could repeat against the final 0.9.7 that would be nice. Also
elfutils 0.141 should be out by now (at least the elfutils git repo is
marked as 0.141), which contains at least one fix that should help
s390x.

> FAIL: LOCAL1 (2)

I have seen this fail sporadically, is it failing always for you?

> FAIL: backtrace (1 0)
> FAIL: backtrace-unwindsyms (1 0)

This is http://sourceware.org/bugzilla/show_bug.cgi?id=6961
"backtrace from non-pt_regs probe context"

> FAIL: debugpath-good (eof)
> FAIL: systemtap.base/kmodule.stp startup (eof)
> FAIL: MAXACTIVE02 compilation

These I have not seen before. Could you look at the
testsuite/systemtap.log file to see if you can deduce what is going
wrong here?

> FAIL: compiling sdt.c ""
> FAIL: compiling sdt.c additional_flags=-std=gnu89
> FAIL: compiling sdt.c additional_flags=-ansi
> FAIL: compiling sdt.c additional_flags=-pedantic
> FAIL: compiling sdt.c additional_flags=-ansi additional_flags=-pedantic
> FAIL: compiling sdt.c additional_flags=-O2
> FAIL: compiling sdt.c additional_flags="-O3"

There was a recent update to sdt.h that might help. If not, could you
see if testsuite/systemtap.log gives more hints about what is wrong?
What gcc version are you using?

> FAIL: skip tracking (2 0)

Not seen this before. A report with the relevant systemtap.log output
would be appreciated.

> FAIL: static_uprobes compiling C -g

This is most likely the same as the sdt.c failures above.

> FAIL: backtrace of yyy_func2 (2)
> FAIL: print_stack of yyy_func2 (2)
> FAIL: backtrace of yyy_func3 (2)
> FAIL: print_stack of yyy_func3 (2)
> FAIL: backtrace of yyy_func4 (2)
> FAIL: print_stack of yyy_func4 (2)

These might need support for the dwarf unwinder on s390x to provide more
accurate backtrace.
http://sourceware.org/ml/systemtap/2009-q2/msg00307.html

> FAIL: integer function arguments -- numeric
> FAIL: unsigned function arguments -- numeric
> FAIL: long function arguments -- numeric
> FAIL: int64 function arguments -- numeric
> FAIL: char function arguments -- numeric
> FAIL: string function arguments -- numeric
> FAIL: integer function arguments -- numeric --kelf --ignore-dwarf
> FAIL: unsigned function arguments -- numeric --kelf --ignore-dwarf
> FAIL: long function arguments -- numeric --kelf --ignore-dwarf
> FAIL: int64 function arguments -- numeric --kelf --ignore-dwarf
> FAIL: char function arguments -- numeric --kelf --ignore-dwarf
> FAIL: string function arguments -- numeric --kelf --ignore-dwarf

Could you post the relevant parts of systemtap.log to see what is going
wrong here?

> FAIL: systemtap.examples/general/para-callgraph build
> FAIL: systemtap.examples/general/para-callgraph run

Likewise.

> FAIL: buildok/four.stp
> FAIL: buildok/maxactive01.stp
> FAIL: buildok/nfsd-all-probes.stp
> FAIL: buildok/scheduler-all-probes.stp
> FAIL: buildok/scsi-all-probes.stp
> FAIL: buildok/scsi.stp
> FAIL: buildok/seventeen.stp
> FAIL: buildok/twentyfive.stp
> FAIL: semok/twentyeight.stp
> FAIL: semok/twentyfour.stp
> FAIL: semok/twentyseven.stp
> FAIL: transok/tval-opt.stp
> FAIL: systemtap.printf/bin6.stp
> FAIL: systemtap.printf/memory1.stp
> FAIL: systemtap.stress/current.stp compilation

Some of these might be solved with an updated elfutils (0.141).

> FAIL: 64-bit acct
> FAIL: 64-bit mmap
> FAIL: 64-bit net1
> FAIL: 64-bit signal
> FAIL: 32-bit acct
> FAIL: 32-bit net1
> FAIL: 32-bit signal
> FAIL: 32-bit statfs

The net1 failures are
http://sourceware.org/bugzilla/show_bug.cgi?id=6991
"accept system call missed on 2.6.27"

For the others look in the systemtap.log file and/or try running the
tests in testsuite/systemtap.syscall by hand. There is a README there
explaining how the tests work and how to use the tcl framework to see
how things should match.

Cheers,

Mark

Re: Test results of systemtap snapshot for Week 17 on kernel 2.6.30-rc2-next-20090420 on RHEL 5.3 on s390x

[Frank Ch. Eigler]

maranp@linux.ibm.com writes:

> Summary report of Snapshot: version 0.9.5/0.140.90 commit 7a2ee7a2 +
> changes Arch: s390x [...]

Please also email these reports (systemtap.sum files) to
dejazilla@elastic.org.

- FChE