With the 2.6.23-rc9 kernel the x86-64 and ia64 prc-all-probes fails, the same test passes on i686 machine running the same kernel. spawn1 stap -p4 /home/wcohen/stap_snap_200710081315/src/testsuite/buildok/rpc-all-probes.stp semantic error: probe point mismatch at position 4 (alternatives: part1 part2) while resolving probe point _sunrpc.clnt.create_client.return.* semantic error: probe point mismatch at position 4 (alternatives: part1 part2) while resolving probe point _sunrpc.clnt.create_client.return.* semantic error: no match for probe point while resolving probe point sunrpc.clnt.create_client.return semantic error: no match for probe point while resolving probe point sunrpc.clnt.create_client.return semantic error: no match for probe point while resolving probe point sunrpc.sched.release_task.return semantic error: no match for probe point while resolving probe point sunrpc.sched.release_task.return Pass 2: analysis failed. Try again with more '-v' (verbose) options. Pass 2: analysis failed. Try again with more '-v' (verbose) options. wait results: 5752 exp15 0 1 FAIL: buildok/rpc-all-probes.stp
This is a new test that exposes rpc tapset bugs that have been around for a while. Looks like some or all of the functions associated with these probes went away around 2.6.19.
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 ===============================================
Even proc_snoop.stp is also failing for the same reason(signal-all-probes.stp) ============================================================= ============================== Running stap -p4 /home/systemtap/tmp/stap_testing_200710150930/src/testsuite/../examples/small_demos/proc_snoop.stp FAIL: proc_snoop.stp semantic error: no match for probe point while resolving probe point kernel.function("handle_signal") semantic error: no match for probe point while resolving probe point signal.handle ===============================
Created attachment 2174 [details] patch to fix the problem Since hanlde_signal32(in ppc) is equvialent to handle_signal. We need to modify tapsets/signal.stp to reflect this. This will resolve 2 systemtap issues on ppc. Please let me know your comments. Thanks Srinivasa DS
Many tapset code & test improvements lately should nip this in the bud.