Created attachment 499907 [details]
upstream patch re-diffed for 1.3

Description of problem:
The trace point used by the softirq.entry and softirq.exit probes in the irq.stp tapset were renamed upstream but the RHEL5 kernel still uses the old names causing a resolution failure for scripts using these probes:

# stap -v softirq.stp 
Pass 1: parsed user script and 72 library script(s) using 87148virt/21484res/2612shr kb, in 100usr/10sys/119real ms.
semantic error: no match while resolving probe point softirq.entry
Pass 2: analyzed script: 2 probe(s), 7 function(s), 1 embed(s), 2 global(s) using 150976virt/25916res/4088shr kb, in 20usr/60sys/83real ms.
Pass 2: analysis failed.  Try again with another '--vp 01' option.


Version-Release number of selected component (if applicable):
systemtap-1.3-4.el5


How reproducible:
100%

Steps to Reproduce:
1. stap -e 'probe softirq.entry { print("foo\n") } probe softirq.exit {
print("bar\n")} probe timer.ms(1000) { exit() }'
  
Actual results:
# stap -e 'probe softirq.entry { print("foo\n") } probe softirq.exit {
print("bar\n")} probe timer.ms(1000) { exit() }'
semantic error: no match while resolving probe point softirq.entry
semantic error: no match while resolving probe point softirq.exit
Pass 2: analysis failed.  Try again with another '--vp 01' option.
[root@rhel5vm-0 tapset]# echo $?
1

Expected results:
# stap -e 'probe softirq.entry { print("foo\n") } probe softirq.exit {
print("bar\n")} probe timer.ms(1000) { exit() }'
foo
bar
foo
bar
foo
bar
foo
bar
foo
foo
bar
bar
[...]
# echo $?
0

Additional info:
http://sourceware.org/ml/systemtap/2011-q2/msg00199.html