This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
help: semantic error: no match while resolving probe point module
- From: Wendy Cheng <s dot wendy dot cheng at gmail dot com>
- To: systemtap at sourceware dot org
- Date: Wed, 28 Nov 2012 14:41:18 -0800
- Subject: help: semantic error: no match while resolving probe point module
Hi,
I have a system (2.6.32-279.el6.x86_64) where
/lib/module/$kversion/kernel/drivers/infinibandel is obsoleted by
/lib/modules/$kversion/updates/drivers/infiniband
After debuginfo rpm was installed, system-tap seemed to be confused by
the driver location. So I manually copied the
/lib/modules/$kversion/updates/drivers/infiniband/ulp/ipoib/ib_ipoib.ko into
/lib/modules/$kversion/kernel/drivers/infiniband/ulp/ipoib directory.
The following simple stap script worked correctly for a while:
[root@cst-kf5 wendy]# cat ipoib.stap
probe module("*ib_ipoib*").function("*").call
{
printf ("%d %s -> %s\n", tid(), thread_indent(1), probefunc())
}
probe module("*ib_ipoib*").function("*").return
{
printf ("%d %s <- %s\n", tid(), thread_indent(-1), probefunc())
}
Then .. after some kmod coding/rebuilt work, kernel crashed. After
reboot, system-tap no longer works:
[root@cst-kf5 wendy]# stap ipoib.stap
semantic error: no match while resolving probe point
module("*ib_ipoib*").function("*").call
semantic error: no match while resolving probe point
module("*ipoib*").function("*").return
Pass 2: analysis failed. Try again with another '--vp 01' option.
Any clue and help ?
Great Thanks,
Wendy