This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: scsi.stp won't run


Frank Ch. Eigler wrote:
There are some known problems with faulty .ko / .ko.debug files being
*generated* by recent elfutils - that is, with someone replacing the
system elfutils with one of the 0.11* series, and building a new
kernel.  It seems like the most robust way to go is to leave the old
system elfutils alone, and use the "--with-elfutils=PATH" systemtap
configure option to build a private copy.

No success, yet. *sigh*


My latest attempt comprised:

downgrading back to elfutils-0.108-1
downloading systemtap-0.5.2-1.src.rpm
rpm -ivh SRPMS/systemtap-0.5.2-1.src.rpm
rpmbuild -ba SPECS/systemtap.spec
	(something related to elfutils-0.118 happened as well
	 during this step,
	 2 systemtap testcases failed BTW)
rpm -ivh RPMS/i386/systemtap-0.5.2-1.i386.rpm

Still, I get:

[root@dyn-9-152-230-71 guanglei]# stap -vg -I . sample.stp
[...]
parsed 'scsi_io_completion' -> func 'scsi_io_completion'
pattern 'scsi_mod' matches module 'scsi_mod'
focused on module 'scsi_mod' = [f8857000-f8877ee9, bias 0]
semantic error: cannot find module scsi_mod debuginfo: Unsupported relocation type
semantic error: no match for probe point
while: resolving probe point module("scsi_mod").function("scsi_io_completion")
semantic error: no match for probe point
while: resolving probe point addevent.scsi.iocompleted
semantic error: no match for probe point
while: resolving probe point addevent.scsi
Pass 2: analyzed user script. 10 probe(s), 26 function(s), 15 global(s).
Pass 2: analysis failed. Try again with '-v' (verbose) option.


I am not sure whether I managed to followed your advice.
Do I need to change the systemtap.spec in order to the config option
you have mentioned?

I am running a recently updated Fedora Core 4 system
(2.6.15-1.1823_FC4 #1 Fri Jan 6 17:54:53 EST 2006 i686 i686 i386).

Since the problem seems to be related to the fact that I want
to place a probe in a module, what about rebuilding the kernel
with a built-in scsi_mod (as a workaround)?
I would need to rebuild the kernel-debuginfo rpm as well. How do
I do the latter? What is about kernel-devel?

Thanks.

Martin


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]