From: Pavan Naregundi <pavan.naregundi@in.ibm.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: Systemtap snap:b6371390 test on kernel 2.6.30-rc3-git2
Date: Tue, 28 Apr 2009 06:02:00 -0000 [thread overview]
Message-ID: <OF7F01BC7C.C3DE65C3-ON652575A6.001DF96D-652575A6.00212F6D@in.ibm.com> (raw)
In-Reply-To: <1240843370.4387.45.camel@fedora.wildebeest.org>
Mark Wielaard <mjw@redhat.com> wrote on 04/27/2009 08:12:50 PM:
> From:
>
> Mark Wielaard <mjw@redhat.com>
>
> To:
>
> Pavan Naregundi/India/IBM@IBMIN
>
> Cc:
>
> systemtap@sourceware.org
>
> Date:
>
> 04/27/2009 08:10 PM
>
> Subject:
>
> Re: Systemtap snap:b6371390 test on kernel 2.6.30-rc3-git2
>
> Hi Pavan,
>
> On Mon, 2009-04-27 at 17:17 +0530, Pavan Naregundi wrote:
> > Results of systemtap snap:b6371390 test on kernel 2.6.30-rc3-git2
> > Arch: ppc64
> >
> > Please contact me, for any other details.
>
> Thanks for testing this combination. Which elfutils version did you use?
elfutils-0.141
>
> > Unexpected failures
> > =============================
> > FAIL: LOCAL1 (0)
>
> I have seen this fail sporadically, is it failing always for you?
I have seen this every time.
>
> > FAIL: STRUCT1 (0)
>
> Could you post the relevant part of the testsuite/systemtap.log?
Running /home/pavan/systemtap/src/testsuite/systemtap.base/alternatives.exp
...
starting stap -vu -p2 -e {
probe kernel.function("sys_getrlimit") { x = $z; }
}
Pass 1: parsed user script and 53 library script(s) in 320usr/20sys/344real
ms.^M
Pass 1: parsed user script and 53 library script(s) in 320usr/20sys/344real
ms.^M
wait results: 15196 exp6 0 1
FAIL: LOCAL1 (0)
starting stap -vu -p2 -e {
probe kernel.function("sys_getrlimit") { rlim_cur = $rlim->rlim_cud; }
}
Pass 1: parsed user script and 53 library script(s) in 320usr/20sys/345real
ms.^M
Pass 1: parsed user script and 53 library script(s) in 320usr/20sys/345real
ms.^M
semantic error: no match while resolving probe point
kernel.function("sys_getrlimit")^M
semantic error: no match while resolving probe point
kernel.function("sys_getrlimit")^M
semantic error: no probes found^M
Pass 2: analyzed script:
semantic error: no probes found^M
0 probe(s), 0 function(s), 0 embed(s), 0 global(s) in
1430usr/960sys/2385real ms.^M
Pass 2: analysis failed. Try again with another '--vp 01' option.^M
Pass 2: analyzed script: 0 probe(s), 0 function(s), 0 embed(s), 0 global(s)
in 1430usr/960sys/2385real ms.^M
Pass 2: analysis failed. Try again with another '--vp 01' option.^M
wait results: 15216 exp7 0 1
FAIL: STRUCT1 (0)
testcase
/home/pavan/systemtap/src/testsuite/systemtap.base/alternatives.exp
completed in 114 seconds
>
> > 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: systemtap.base/cast.stp
> > FAIL: debugpath-bad (eof)
> > FAIL: debugpath-good (eof)
>
> Could you post the relevant parts of the testsuite/systemtap.log for the
> above failures?
Running /home/pavan/systemtap/src/testsuite/systemtap.base/cast.exp ...
executing: stap /home/pavan/systemtap/src/testsuite/systemtap.base/cast.stp
-g
FAIL: systemtap.base/cast.stp
line 4: expected "tv_sec OK"
Got "tv_sec 42 != 0"
testcase /home/pavan/systemtap/src/testsuite/systemtap.base/cast.exp
completed in 8 seconds
Running /home/pavan/systemtap/src/testsuite/systemtap.base/debugpath.exp
...
semantic error: no match while resolving probe point
kernel.function("sys_open")^M
semantic error: no probes found^M
Pass 2: analysis failed. Try again with another '--vp 01' option.^M
FAIL: debugpath-bad (eof)
semantic error: no match while resolving probe point
kernel.function("sys_open")^M
semantic error: no probes found^M
Pass 2: analysis failed. Try again with another '--vp 01' option.^M
FAIL: debugpath-good (eof)
testcase /home/pavan/systemtap/src/testsuite/systemtap.base/debugpath.exp
completed in 6 seconds
>
> > FAIL: gtod (9)
>
> This is probably http://sourceware.org/bugzilla/show_bug.cgi?id=5094
> "gtod.exp fails on ppc64/i386"
>
> > FAIL: MAXACTIVE01 compilation
> > FAIL: MAXACTIVE02 compilation
Running /home/pavan/systemtap/src/testsuite/systemtap.base/maxactive.exp
...
executing: stap -v -e {
global foo
probe kernel.function("sys_select").return,
kernel.function("sys_read").return { foo++ }
probe timer.ms(5000) { exit(); }
probe begin { log("systemtap starting probe"); log("systemtap ending
probe");}
}
Pass 1: parsed user script and 53 library script(s) in 320usr/20sys/346real
ms.^M
semantic error: no match while resolving probe point
kernel.function("sys_select").returnFAIL: MAXACTIVE01 compilation
executing: stap -v -e {
global foo
probe kernel.function("sys_select").return.maxactive(1),
kernel.function("sys_read").return.maxactive(1) { foo++ }
probe timer.ms(5000) { exit(); }
probe begin { log("systemtap starting probe"); log("systemtap ending
probe");}
}
Pass 1: parsed user script and 53 library script(s) in 320usr/20sys/347real
ms.^M
semantic error: no match while resolving probe point
kernel.function("sys_select").return.maxactive(1)FAIL: MAXACTIVE02
compilation
PASS: MAXACTIVE03
testcase /home/pavan/systemtap/src/testsuite/systemtap.base/maxactive.exp
completed in 6 seconds
> > FAIL: conditional probes (0)
Running /home/pavan/systemtap/src/testsuite/systemtap.base/onoffprobe.exp
...
semantic error: no match while resolving probe point
kernel.function("sys_write").return if ((switch) == (1))^M
semantic error: no match while resolving probe point
kernel.function("sys_write") if ((switch) == (2))^M
Pass 2: analysis failed. Try again with another '--vp 01' option.^M
FAIL: conditional probes (0)
testcase /home/pavan/systemtap/src/testsuite/systemtap.base/onoffprobe.exp
completed in 3 seconds
> > FAIL: OVERLOAD1 compilation
> > FAIL: OVERLOAD2 compilation
> > FAIL: OVERLOAD3 compilation
testcase
/home/pavan/systemtap/src/testsuite/systemtap.base/overflow_error.exp
completed in 5 seconds
Running /home/pavan/systemtap/src/testsuite/systemtap.base/overload.exp ...
Pass 1: parsed user script and 53 library script(s) in 330usr/20sys/353real
ms.^M
semantic error: no match while resolving probe point
kernel.function("sys_read")FAIL: OVERLOAD1 compilation
Pass 1: parsed user script and 53 library script(s) in 320usr/20sys/344real
ms.^M
semantic error: no match while resolving probe point
kernel.function("sys_read")FAIL: OVERLOAD2 compilation
Pass 1: parsed user script and 53 library script(s) in 330usr/20sys/350real
ms.^M
semantic error: no match while resolving probe point
kernel.function("sys_read")FAIL: OVERLOAD3 compilation
testcase /home/pavan/systemtap/src/testsuite/systemtap.base/overload.exp
completed in 9 seconds
>
> Could you post the relevant parts of the testsuite/systemtap.log for the
> above failures?
>
> > 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: static_uprobes compiling C -g
Running /home/pavan/systemtap/src/testsuite/systemtap.base/sdt.exp ...
Executing on host: gcc
/home/pavan/systemtap/src/testsuite/systemtap.base/sdt.c -g
-I/home/pavan/systemtap/src/testsuite/../includes/sys -Wall -Wextra -Werror
-lm -o sdt.c.exe.0 (timeout = 300)
/tmp/ccastHp6.s: Assembler messages:^M
/tmp/ccastHp6.s:57: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:116: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:179: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:246: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:317: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:392: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:471: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:554: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:640: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:729: Error: junk at end of line: `0'^M
compiler exited with status 1
output is:
/tmp/ccastHp6.s: Assembler messages:^M
/tmp/ccastHp6.s:57: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:116: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:179: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:246: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:317: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:392: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:471: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:554: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:640: Error: junk at end of line: `0'^M
/tmp/ccastHp6.s:729: Error: junk at end of line: `0'^M
FAIL: compiling sdt.c ""
UNTESTED: sdt ""
>
> That probably means the sdt.h header doesn't compile on ppc.
> Could you see if testsuite/systemtap.log gives more hints about what is
> wrong? What gcc version are you using?
gcc version 4.3.2 20081007 (Red Hat 4.3.2-6) (GCC)
>
> > FAIL: stmtvars - .function
Running /home/pavan/systemtap/src/testsuite/systemtap.base/stmtvars.exp ...
SystemTap translator/driver (version 0.9.7/0.141 non-git sources)^M
Copyright (C) 2005-2009 Red Hat, Inc. and others^M
This is free software; see the source for copying conditions.^M
Session arch: ppc64 release: 2.6.30-rc3-git2^M
Created temporary directory "/tmp/stapQQdYat"^M
Searched '/usr/local/share/systemtap/tapset/ppc64/*.stp', found 2^M
Searched '/usr/local/share/systemtap/tapset/*.stp', found 51^M
Pass 1: parsed user script and 53 library script(s) in 320usr/20sys/344real
ms.^M
semantic error: no match while resolving probe point
kernel.function("sys_open")^M
semantic error: no probes found^M
Pass 2: analyzed script: 0 probe(s), 0 function(s), 0 embed(s), 0 global(s)
in 1410usr/950sys/2361real ms.^M
Pass 2: analysis failed. Try again with another '--vp 01' option.^M
Running rm -rf /tmp/stapQQdYat^M
pc=0 vars=
FAIL: stmtvars - .function
SystemTap translator/driver (version 0.9.7/0.141 non-git sources)^M
Copyright (C) 2005-2009 Red Hat, Inc. and others^M
> > FAIL: system_func (0,0,0)
Running /home/pavan/systemtap/src/testsuite/systemtap.base/system_func.exp
...
semantic error: no match while resolving probe point
kernel.function("sys_open")^M
Pass 2: analysis failed. Try again with another '--vp 01' option.^M
FAIL: system_func (0,0,0)
testcase /home/pavan/systemtap/src/testsuite/systemtap.base/system_func.exp
completed in 2 seconds
>
> Could you post the relevant parts of the testsuite/systemtap.log for the
> above failures?
>
> > FAIL: backtrace of yyy_func2 (1)
> > FAIL: print_stack of yyy_func2 (1)
> > FAIL: backtrace of yyy_func3 (1)
> > FAIL: print_stack of yyy_func3 (1)
> > FAIL: backtrace of yyy_func4 (1)
> > FAIL: print_stack of yyy_func4 (1)
>
> These might need support for the dwarf unwinder on ppc to provide more
> accurate backtraces.
> 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
>
sourcing:
/home/pavan/systemtap/src/testsuite/systemtap.context/num_args.tcl
READY^M
yyy_int -4611686018425998288 -4611686018425998288 -4611686018425998288^M
yyy_int returns 499^M
FAIL: integer function arguments -- numeric
yyy_uint 1389616 1389616 1389616^M
yyy_uint returns 499^M
FAIL: unsigned function arguments -- numeric
yyy_long -4611686018425998288 -4611686018425998288 -4611686018425998288^M
yyy_long returns 499^M
FAIL: long function arguments -- numeric
yyy_int64 -4611686018425998288 -4611686018425998288 -4611686018425998288^M
yyy_int64 returns 499^M
FAIL: int64 function arguments -- numeric
yyy_char 0 0 0^M
yyy_char returns Q^M
FAIL: char function arguments -- numeric
yyy_str
ûaÿØ|^H^B¦û<81>ÿà|<9b>#xû¡ÿèxc-ûaÿØ|^H^B¦û<81>ÿà|<9b>#xû¡ÿèxc-ûaÿØ|^H^B¦û<81>ÿà|<9b>#xû¡ÿèxc^M
yyy_str returns XYZZY^M
FAIL: string function arguments -- numeric
READY^M
yyy_int -4611686018425998288 -4611686018425998288 -4611686018425998288^M
yyy_int returns 499^M
FAIL: integer function arguments -- numeric --kelf --ignore-dwarf
yyy_uint 1389616 1389616 1389616^M
yyy_uint returns 499^M
FAIL: unsigned function arguments -- numeric --kelf --ignore-dwarf
yyy_long -4611686018425998288 -4611686018425998288 -4611686018425998288^M
yyy_long returns 499^M
FAIL: long function arguments -- numeric --kelf --ignore-dwarf
yyy_int64 -4611686018425998288 -4611686018425998288 -4611686018425998288^M
yyy_int64 returns 499^M
FAIL: int64 function arguments -- numeric --kelf --ignore-dwarf
yyy_char 0 0 0^M
yyy_char returns Q^M
FAIL: char function arguments -- numeric --kelf --ignore-dwarf
yyy_str
ûaÿØ|^H^B¦û<81>ÿà|<9b>#xû¡ÿèxc-ûaÿØ|^H^B¦û<81>ÿà|<9b>#xû¡ÿèxc-ûaÿØ|^H^B¦û<81>ÿà|<9b>#xû¡ÿèxc^M
yyy_str returns XYZZY^M
FAIL: string function arguments -- numeric --kelf --ignore-dwarf
as_root /bin/rm -f
/lib/modules/2.6.30-rc3-git2/kernel/systemtap_test_module1.ko
OUT
RC 0
as_root /sbin/rmmod systemtap_test_module1
OUT
RC 0
as_root /bin/rm -f
/lib/modules/2.6.30-rc3-git2/kernel/systemtap_test_module2.ko
OUT
RC 0
as_root /sbin/rmmod systemtap_test_module2
OUT
RC 0
> Could you post the relevant parts of the testsuite/systemtap.log for the
> above failures?
>
> > FAIL: systemtap.examples/general/para-callgraph build
> > FAIL: systemtap.examples/general/para-callgraph run
>
> Likewise.
>
> > FAIL: buildok/maxactive01.stp
> > FAIL: buildok/signal-all-probes.stp
> > FAIL: buildok/thirteen.stp
> > FAIL: semok/thirtytwo.stp
> > FAIL: semok/twentyeight.stp
> > FAIL: semok/twentyfour.stp
> > FAIL: semok/twentynine.stp
> > FAIL: semok/twentyseven.stp
> > FAIL: systemtap.printf/bin6.stp
> > FAIL: systemtap.stress/current.stp shutdown (eof)
>
>
> Some of these might be solved with an updated elfutils (0.141). At least
> that was the case for s390.
Using the same elfutils-0.141.
>
> > FAIL: 64-bit acct
> > FAIL: 64-bit net1
> > FAIL: 64-bit readwrite
> > FAIL: 64-bit signal
> > FAIL: 32-bit acct
> > FAIL: 32-bit net1
> > FAIL: 32-bit readwrite
> > 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.
>
> Thanks,
>
> Mark
>
Thanks
Pavan
next prev parent reply other threads:[~2009-04-28 6:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 11:49 Pavan Naregundi
2009-04-27 14:43 ` Mark Wielaard
2009-04-28 5:11 ` Pavan Naregundi
2009-04-28 6:02 ` Pavan Naregundi [this message]
2009-04-28 6:07 ` Ananth N Mavinakayanahalli
2009-04-29 9:37 ` Mark Wielaard
2009-04-29 19:01 ` Josh Stone
2009-04-29 9:41 ` Mark Wielaard
2009-04-28 6:56 ` Ananth N Mavinakayanahalli
2009-04-29 8:57 ` Mark Wielaard
2009-04-29 9:26 ` Ananth N Mavinakayanahalli
2009-04-29 12:08 ` Mark Wielaard
2009-04-29 12:21 ` Ananth N Mavinakayanahalli
2009-04-29 12:27 ` Mark Wielaard
2009-04-29 13:15 ` David Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OF7F01BC7C.C3DE65C3-ON652575A6.001DF96D-652575A6.00212F6D@in.ibm.com \
--to=pavan.naregundi@in.ibm.com \
--cc=mjw@redhat.com \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).