This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: SYSTEMTAP TEST RESULTS : Kernel version 2.6.35-rc3 on POWER ppc64 architecture.
Please find the o/p of the commands below
Thanks and Regards
Divya Vikas
David Smith
<dsmith@redhat.co
m> To
Mark Wielaard <mjw@redhat.com>
06/24/2010 02:21 cc
AM Divya Vikas/India/IBM@IBMIN,
systemtap@sources.redhat.com,
Sachin P Sant/India/IBM@IBMIN
Subject
Re: SYSTEMTAP TEST RESULTS : Kernel
version 2.6.35-rc3 on POWER ppc64
architecture.
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
semantic error: not accessible at this address (0x95a84): identifier
'$filp' at /usr/local/share/systemtap/tapset/nfsd.stp:1046:29
source: filename = __file_filename($filp)
^
semantic error: not accessible at this address (0x95b84): identifier
'$filp' at :1046:29
source: filename = __file_filename($filp)
^
semantic error: not accessible at this address (0x95ca0): identifier
'$filp' at :1046:29
source: filename = __file_filename($filp)
^
semantic error: not accessible at this address (0x95dac): identifier
'$filp' at :1046:29
source: filename = __file_filename($filp)
^
nfsd.close client_ip:string filename:string name:string argstr:string
> 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").*'
p55alp2:/home/linux-2.6.35-rc3 # stap -L 'kernel.function
("handle_signal").*'
p55alp2:/home/linux-2.6.35-rc3 #
> 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
semantic error: not accessible at this address (0x10d7c): identifier '$cmd'
at /usr/local/share/systemtap/tapset/scsi.stp:130:12
source: host_no = $cmd->device->host->host_no
^
semantic error: not accessible at this address (0x10d7c): identifier '$cmd'
at :131:12
source: channel = $cmd->device->channel
^
semantic error: not accessible at this address (0x10d7c): identifier '$cmd'
at :132:8
source: lun = $cmd->device->lun
^
semantic error: not accessible at this address (0x10d7c): identifier '$cmd'
at :133:11
source: dev_id = $cmd->device->id
^
semantic error: not accessible at this address (0x10d7c): identifier '$cmd'
at :134:17
source: device_state = $cmd->device->sdev_state
^
semantic error: not accessible at this address (0x10d7c): identifier '$cmd'
at :136:19
source: data_direction = $cmd->sc_data_direction
^
semantic error: not accessible at this address (0x10d7c): identifier '$cmd'
at :138:13
source: req_addr = $cmd->request
^
semantic error: not accessible at this address (0x10d7c): identifier '$cmd'
at :139:42
source: scsi_timer_pending = scsi_timer_pending($cmd);
^
semantic error: not accessible at this address (0x10e90): identifier '$cmd'
at :130:12
source: host_no = $cmd->device->host->host_no
^
semantic error: not accessible at this address (0x10e90): identifier '$cmd'
at :131:12
source: channel = $cmd->device->channel
^
semantic error: not accessible at this address (0x10e90): identifier '$cmd'
at :132:8
source: lun = $cmd->device->lun
^
semantic error: not accessible at this address (0x10e90): identifier '$cmd'
at :133:11
source: dev_id = $cmd->device->id
^
semantic error: not accessible at this address (0x10e90): identifier '$cmd'
at :134:17
source: device_state = $cmd->device->sdev_state
^
semantic error: not accessible at this address (0x10e90): identifier '$cmd'
at :136:19
source: data_direction = $cmd->sc_data_direction
^
semantic error: not accessible at this address (0x10e90): identifier '$cmd'
at :138:13
source: req_addr = $cmd->request
^
semantic error: not accessible at this address (0x10e90): identifier '$cmd'
at :139:42
source: scsi_timer_pending = scsi_timer_pending($cmd);
^
semantic error: not accessible at this address (0x10ef4): identifier '$cmd'
at :130:12
source: host_no = $cmd->device->host->host_no
^
semantic error: not accessible at this address (0x10ef4): identifier '$cmd'
at :131:12
source: channel = $cmd->device->channel
^
semantic error: not accessible at this address (0x10ef4): identifier '$cmd'
at :132:8
source: lun = $cmd->device->lun
^
semantic error: not accessible at this address (0x10ef4): identifier '$cmd'
at :133:11
source: dev_id = $cmd->device->id
^
semantic error: not accessible at this address (0x10ef4): identifier '$cmd'
at :134:17
source: device_state = $cmd->device->sdev_state
^
semantic error: not accessible at this address (0x10ef4): identifier '$cmd'
at :136:19
source: data_direction = $cmd->sc_data_direction
^
semantic error: not accessible at this address (0x10ef4): identifier '$cmd'
at :138:13
source: req_addr = $cmd->request
^
semantic error: not accessible at this address (0x10ef4): identifier '$cmd'
at :139:42
source: scsi_timer_pending = scsi_timer_pending($cmd);
^
semantic error: unresolved type : identifier 'host_no' at :130:2
source: host_no = $cmd->device->host->host_no
^
semantic error: unresolved type : identifier 'channel' at :131:2
source: channel = $cmd->device->channel
^
semantic error: unresolved type : identifier 'lun' at :132:2
source: lun = $cmd->device->lun
^
semantic error: unresolved type : identifier 'dev_id' at :133:2
source: dev_id = $cmd->device->id
^
semantic error: unresolved type : identifier 'req_addr' at :138:2
source: req_addr = $cmd->request
^
scsi.iodone device_state:long device_state_str:string data_direction:long
data_direction_str:string scsi_timer_pending:long
> 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
semantic error: invalid access '[0]' vs. long int: operator '['
at /usr/local/share/systemtap/tapset/syscalls2.stp:312:29
source: pipe0 = user_int(&$fildes[0]);
^
semantic error: invalid access '[1]' vs. long int: operator '[' at :313:29
source: pipe1 = user_int(&$fildes[1]);
^
syscall.pipe flags:long flag_str:string name:string fildes_uaddr:long
pipe0:long pipe1:long argstr:string $fildes:long int $flags:long int
> 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)