This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Systemtap results on power64 box against kernel version 2.6.35-rc4-git5
On Monday 19 July 2010 11:22 PM, David Smith wrote:
On 07/13/2010 09:53 AM, David Smith wrote:
On 07/13/2010 08:40 AM, divya wrote:
Hi Everyone,
Here is the result of systemtap snap test on kernel 2.6.35-rc4-git5
Arch - ppc64
elfutils version - 0.148
Divya was kind enough to send me the full log file, so I've had a look
at some of these errors. Most of the errors look to be debuginfo
problems with 1 build-id problem.
FAIL: systemtap.examples/general/badname build
FAIL: systemtap.examples/general/badname run
Hmm, it looks like the test should be a bit smarter and not try to run a
script if it fails to build. Anyway, this one fails with errors like:
semantic error: failed to retrieve location attribute for local 'child'
(dieoffset: 0xf3c95c): identifier '$child' at badname.stp:16:7
source: if ($child->d_inode || $dir->i_flags& 16) next
This looks like a debuginfo problem. Can you show me the output of:
# stap -L 'kernel.function("may_create@fs/namei.c")'
p55alp7:~ # stap -L 'kernel.function("may_create@fs/namei.c")'
kernel.function("may_create@fs/namei.c:1354")
FAIL: systemtap.examples/io/iostat-scsi run
This one failed with:
ERROR: Build-id mismatch: "sd_mod" vs. "sd_mod.ko" byte 0 (0xc1 vs 0x00)
rc 0 -14
which means that stap doesn't think your debuginfo and the actual module
match. Other stap folk can probably expound more here.
FAIL: systemtap.examples/network/netdev build
FAIL: systemtap.examples/network/netdev run
This one failed with:
semantic error: failed to retrieve location attribute for local 'dev'
(dieoffset: 0x2daa6f2): identifier '$dev' at
/usr/local/share/systemtap/tapset/networking.stp:159:29
source: dev_name = get_netdev_name($dev)
I'd bet this one is a debuginfo problem. Can you show me the output of:
# stap -L netdev.change_rx_flag
p55alp7:~ # stap -L netdev.change_rx_flag
semantic error: failed to retrieve location attribute for local 'dev' (dieoffset: 0x2daa6f2): identifier '$dev' at /usr/local/share/systemtap/tapset/networking.stp:159:29
source: dev_name = get_netdev_name($dev)
^
semantic error: failed to retrieve location attribute for local 'flags' (dieoffset: 0x2daa6ed): identifier '$flags' at :160:10
source: flags = $flags
^
semantic error: failed to retrieve location attribute for local 'dev' (dieoffset: 0x2daa899): identifier '$dev' at :159:29
source: dev_name = get_netdev_name($dev)
^
semantic error: failed to retrieve location attribute for local 'flags' (dieoffset: 0x2daa894): identifier '$flags' at :160:10
source: flags = $flags
^
semantic error: failed to retrieve location attribute for local 'dev' (dieoffset: 0x2daa9a1): identifier '$dev' at :159:29
source: dev_name = get_netdev_name($dev)
^
semantic error: failed to retrieve location attribute for local 'flags' (dieoffset: 0x2daa99c): identifier '$flags' at :160:10
source: flags = $flags
^
semantic error: unresolved type : identifier 'flags' at :160:2
source: flags = $flags
^
netdev.change_rx_flag dev_name:string flags:unknown
FAIL: systemtap.examples/network/socktop run
This one was a testcase problem that I just fixed.
Hmm, I'm surprised the examples failed. Can you privately email me the
systemtap.log output for systemtap.examples/check.exp?
FAIL: buildok/nfsd-detailed.stp
This one dies with:
semantic error: not accessible at this address (0x1703c): identifier
'$filp' at /usr/local/share/systemtap/tapset/nfsd.stp:1046:29^M
source: filename = __file_filename($filp)^M
This looks like a debuginfo problem. Can you show me the output of:
# stap -L nfsd.close
p55alp7:~ # stap -L nfsd.close
semantic error: not accessible at this address (0x1703c): identifier '$filp' at /usr/local/share/systemtap/tapset/nfsd.stp:1046:29
source: filename = __file_filename($filp)
^
semantic error: not accessible at this address (0x1713c): identifier '$filp' at :1046:29
source: filename = __file_filename($filp)
^
semantic error: not accessible at this address (0x17258): identifier '$filp' at :1046:29
source: filename = __file_filename($filp)
^
semantic error: not accessible at this address (0x17364): 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
This one dies with:
semantic error: no match while resolving probe point
module("ne2k_pci").function("ne2k_pci_open")
This is a test problem, not a real problem.
FAIL: buildok/scsi-detailed.stp
This one dies errors like:
semantic error: not accessible at this address (0x10e34): identifier
'$cmd' at /usr/local/share/systemtap/tapset/scsi.stp:133:12^M
source: host_no = $cmd->device->host->host_no^M
This looks like another debuginfo problem. Can you show me the output of:
# stap -L scsi.iodone
p55alp7:~ # stap -L scsi.iodone
semantic error: not accessible at this address (0x10e34): identifier '$cmd' at /usr/local/share/systemtap/tapset/scsi.stp:133:12
source: host_no = $cmd->device->host->host_no
^
semantic error: not accessible at this address (0x10e34): identifier '$cmd' at :134:12
source: channel = $cmd->device->channel
^
semantic error: not accessible at this address (0x10e34): identifier '$cmd' at :135:8
source: lun = $cmd->device->lun
^
semantic error: not accessible at this address (0x10e34): identifier '$cmd' at :136:11
source: dev_id = $cmd->device->id
^
semantic error: not accessible at this address (0x10e34): identifier '$cmd' at :137:17
source: device_state = $cmd->device->sdev_state
^
semantic error: not accessible at this address (0x10e34): identifier '$cmd' at :139:19
source: data_direction = $cmd->sc_data_direction
^
semantic error: not accessible at this address (0x10e34): identifier '$cmd' at :141:13
source: req_addr = $cmd->request
^
semantic error: not accessible at this address (0x10e34): identifier '$cmd' at :142:42
source: scsi_timer_pending = scsi_timer_pending($cmd);
^
semantic error: not accessible at this address (0x10f48): identifier '$cmd' at :133:12
source: host_no = $cmd->device->host->host_no
^
semantic error: not accessible at this address (0x10f48): identifier '$cmd' at :134:12
source: channel = $cmd->device->channel
^
semantic error: not accessible at this address (0x10f48): identifier '$cmd' at :135:8
source: lun = $cmd->device->lun
^
semantic error: not accessible at this address (0x10f48): identifier '$cmd' at :136:11
source: dev_id = $cmd->device->id
^
semantic error: not accessible at this address (0x10f48): identifier '$cmd' at :137:17
source: device_state = $cmd->device->sdev_state
^
semantic error: not accessible at this address (0x10f48): identifier '$cmd' at :139:19
source: data_direction = $cmd->sc_data_direction
^
semantic error: not accessible at this address (0x10f48): identifier '$cmd' at :141:13
source: req_addr = $cmd->request
^
semantic error: not accessible at this address (0x10f48): identifier '$cmd' at :142:42
source: scsi_timer_pending = scsi_timer_pending($cmd);
^
semantic error: not accessible at this address (0x10fac): identifier '$cmd' at :133:12
source: host_no = $cmd->device->host->host_no
^
semantic error: not accessible at this address (0x10fac): identifier '$cmd' at :134:12
source: channel = $cmd->device->channel
^
semantic error: not accessible at this address (0x10fac): identifier '$cmd' at :135:8
source: lun = $cmd->device->lun
^
semantic error: not accessible at this address (0x10fac): identifier '$cmd' at :136:11
source: dev_id = $cmd->device->id
^
semantic error: not accessible at this address (0x10fac): identifier '$cmd' at :137:17
source: device_state = $cmd->device->sdev_state
^
semantic error: not accessible at this address (0x10fac): identifier '$cmd' at :139:19
source: data_direction = $cmd->sc_data_direction
^
semantic error: not accessible at this address (0x10fac): identifier '$cmd' at :141:13
source: req_addr = $cmd->request
^
semantic error: not accessible at this address (0x10fac): identifier '$cmd' at :142:42
source: scsi_timer_pending = scsi_timer_pending($cmd);
^
semantic error: unresolved type : identifier 'host_no' at :133:2
source: host_no = $cmd->device->host->host_no
^
semantic error: unresolved type : identifier 'channel' at :134:2
source: channel = $cmd->device->channel
^
semantic error: unresolved type : identifier 'lun' at :135:2
source: lun = $cmd->device->lun
^
semantic error: unresolved type : identifier 'dev_id' at :136:2
source: dev_id = $cmd->device->id
^
semantic error: unresolved type : identifier 'req_addr' at :141: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
Hi David,
Pls find the o/p of the commands mentioned above.
Also sending systemtap.examples/check.exp privately to your email.
Thanks
Divya