Re: SYSTEMTAP TEST RESULTS : Kernel version 2.6.35-rc3 on POWER ppc64 architecture.

[David Smith <dsmith at redhat dot com>]

On 06/23/2010 04:48 AM, Mark Wielaard wrote:
> On Wed, 2010-06-23 at 14:25 +0530, Divya Vikas wrote:

Here's some discussion of some of these.

> FAIL: cmd_parse16: eof

The cmd_parse16 failure was PR11719 - should be fixed now.

> FAIL: buildok/nfsd-detailed.stp

nfsd-detailed.stp fails because we can't find the $filp argument of used
by nfsd.close (which ends up as either kernel.function("nfsd_close") or
module("nfsd").function("nfsd_close")).

Could you run the following command and show me the output: stap -L
nfsd.close

> FAIL: buildok/pr10678.stp

pr10678.stp fails because we can't find
'module("ne2k_pci").function("ne2k_pci_open")'.  You must have compiled
that driver into the kernel or not compiled it at all.

> FAIL: buildok/pretty.stp

pretty.stp fails because your kernel has no utrace support

> FAIL: buildok/process_test.stp

process_test.stp fails because we can't find
'kernel.function("handle_signal")', which is odd.  Can you run the
following command and show me the output:

stap -L 'kernel.function("handle_signal").*'

> FAIL: buildok/scsi.stp

scsi.stp fails because we can't find the $cmd arg of scsi.iodone (which
is really either
module("scsi_mod").function("scsi_done@drivers/scsi/scsi.c") or
kernel.function("scsi_done@drivers/scsi/scsi.c")).


Could you run the following command and show me the output: stap -L
scsi.iodone

> FAIL: buildok/signal-all-probes.stp

process_test.stp fails because we can't find
'kernel.function("handle_signal")'

> FAIL: buildok/syscall.stp

This one is failing in syscall.pipe.

Could you run the following command and show me the output: stap -L
syscall.pipe

> FAIL: semok/pretty.stp

pretty.stp fails because your kernel has no utrace support

> FAIL: systemtap.printf/bin6.stp

bin6.exp was just fixed today, PR11725.

-- 
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)