[Bug tapsets/5151] rpc-all-probes.stp fails on 2.6.23-rc9 kernel

[srinivasa at in dot ibm dot com]

------- Additional Comments From srinivasa at in dot ibm dot com  2007-10-15 13:32 -------
I could see nfs-all-probes.stp,signal-all-probes.stp also failing on systemtap
20071013 snapshot.

========================================
Running
/home/systemtap/tmp/stap_testing_200710150930/src/testsuite/buildok/nfs-all-probes.stp
starting
/home/systemtap/tmp/stap_testing_200710150930/src/testsuite/buildok/nfs-all-probes.stp
spawn1 stap -p4
/home/systemtap/tmp/stap_testing_200710150930/src/testsuite/buildok/nfs-all-probes.stp
semantic error: no match for probe point while resolving probe point
nfs.fop.sendfile^M
semantic error: no match for probe point while resolving probe point
nfs.fop.sendfile^M
semantic error: no match for probe point while resolving probe point
nfs.fop.sendfile.return^M

semantic error: no match for probe point while resolving probe point
nfs.fop.sendfile.return^M
semantic error: no match for probe point while resolving probe point
nfs.proc3.commit^M

semantic error: no match for probe point while resolving probe point
nfs.proc3.commit^M
semantic error: no match for probe point while resolving probe point
nfs.proc4.commit^M

semantic error: no match for probe point while resolving probe point
nfs.proc4.commit^M
semantic error: no match for probe point while resolving probe point
nfs.proc2.read^M

semantic error: no match for probe point while resolving probe point
nfs.proc2.read^M
semantic error: no match for probe point while resolving probe point
nfs.proc3.read^M

semantic error: no match for probe point while resolving probe point
nfs.proc3.read^M
semantic error: no match for probe point while resolving probe point
nfs.proc4.read^M

semantic error: no match for probe point while resolving probe point
nfs.proc4.read^M
semantic error: no match for probe point while resolving probe point nfs.proc.read^M

semantic error: no match for probe point while resolving probe point nfs.proc.read^M
semantic error: no match for probe point while resolving probe point
nfs.proc2.write^M

semantic error: no match for probe point while resolving probe point
nfs.proc2.write^M
semantic error: no match for probe point while resolving probe point
nfs.proc3.write^M

semantic error: no match for probe point while resolving probe point
nfs.proc3.write^M
semantic error: no match for probe point while resolving probe point
nfs.proc4.write^M

semantic error: no match for probe point while resolving probe point
nfs.proc4.write^M
=============================================


=====================================================
Running
/home/systemtap/tmp/stap_testing_200710150930/src/testsuite/buildok/signal-all-probes.stp
starting
/home/systemtap/tmp/stap_testing_200710150930/src/testsuite/buildok/signal-all-probes.stp
spawn1 stap -p4
/home/systemtap/tmp/stap_testing_200710150930/src/testsuite/buildok/signal-all-probes.stp
semantic error: no match for probe point while resolving probe point
kernel.function("handle_signal")^M
semantic error: no match for probe point while resolving probe point
kernel.function("handle_signal")^M
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.^M

Pass 2: analysis failed.  Try again with more '-v' (verbose) options.^M
wait results: 4905 exp17 0 1
FAIL: buildok/signal-all-probes.stp
===============================================

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=5151

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.