Runtime probe example causes oops

[Hien Nguyen <hien at us dot ibm dot com>]

Hi Martin,

I just get the latest runtime from the CVS, and try it out on my 
machine. My machine is running 2.6.13-rc1.

I did the following
make
cd probes/os_timer
./stp os_timers.ko
Press Control-C to stop.
Using channel with 4 sub-buffers of size 65536.

This message came in the log
Jul 12 10:41:53 elm3b99 kernel: os_timer: no version for 
"relay_subbufs_consumed" found: kernel tainted.

Press Control-c I got an Oops


Jul 12 10:42:32 elm3b99 kernel: Unable to handle kernel NULL pointer 
dereference at virtual address 0000004b
Jul 12 10:42:32 elm3b99 kernel:  printing eip:
Jul 12 10:42:32 elm3b99 kernel: c01424b2
Jul 12 10:42:32 elm3b99 kernel: *pde = 351f3001
Jul 12 10:42:32 elm3b99 kernel: Oops: 0002 [#1]
Jul 12 10:42:32 elm3b99 kernel: SMP
Jul 12 10:42:32 elm3b99 kernel: Modules linked in: os_timer stp_control 
relayfs parport_pc lp parport autofs4 rfcomm l2cap bluetooth sunrpc 
ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables dm_mod ipv6 
ohci_hcd i2c_piix4 i2c_core e100 pcnet32 mii tg3 e1000 floppy sg ext3 
jbd lpfc qla2300 qla2xxx scsi_transport_fc aic7xxx scsi_transport_spi 
sd_mod scsi_mod
Jul 12 10:42:32 elm3b99 kernel: CPU:    1
Jul 12 10:42:32 elm3b99 kernel: EIP:    0060:[<c01424b2>]    Tainted: 
GF     VLIJul 12 10:42:32 elm3b99 kernel: EFLAGS: 00010a87   (2.6.13-rc1)
Jul 12 10:42:32 elm3b99 kernel: EIP is at kallsyms_lookup+0x122/0x1f0
Jul 12 10:42:32 elm3b99 kernel: eax: 0000004b   ebx: 0000004b   ecx: 
f7feeeec edx: f7feeee8
Jul 12 10:42:32 elm3b99 kernel: esi: f8af0000   edi: f8b38b00   ebp: 
f8b35a20 esp: f7feee4c
Jul 12 10:42:32 elm3b99 kernel: ds: 007b   es: 007b   ss: 0068
Jul 12 10:42:33 elm3b99 kernel: Process events/1 (pid: 11, 
threadinfo=f7fee000 task=f7fef550)
Jul 12 10:42:33 elm3b99 kernel: Stack: f8b340d7 f7feeef0 f7feee68 
ffffffff 00000001 00000002 00001d8a f8b5b6b4
Jul 12 10:42:33 elm3b99 kernel:        0000000a 00000000 ffffffff 
f7feeefc f8b5b43f f8b5b449 f7feef10 f8b5b451
Jul 12 10:42:33 elm3b99 kernel:        f8b5d43d 0000004c c01e88d9 
000000c3 00000000 0000000a ffffffff 00000003
Jul 12 10:42:33 elm3b99 kernel: Call Trace:
Jul 12 10:42:33 elm3b99 kernel:  [<f8b340d7>] 
_stp_symbol_sprint+0x47/0x110 [os_timer]
Jul 12 10:42:33 elm3b99 kernel:  [<c01e88d9>] vsnprintf+0x349/0x600
Jul 12 10:42:33 elm3b99 kernel:  [<f8b3398e>] _stp_sprintf+0x8e/0xf0 
[os_timer]
Jul 12 10:42:33 elm3b99 kernel:  [<f8b344ce>] print_keytype+0x3e/0xd0 
[os_timer]Jul 12 10:42:33 elm3b99 kernel:  [<f8b33857>] 
next_fmt+0x37/0x90 [os_timer]
Jul 12 10:42:33 elm3b99 kernel:  [<f8b3470d>] _stp_map_print+0xad/0xd0 
[os_timer]
Jul 12 10:42:33 elm3b99 kernel:  [<f8b35803>] probe_exit+0x43/0x5b 
[os_timer]
Jul 12 10:42:33 elm3b99 kernel:  [<f8b3328f>] 
_stp_cleanup_and_exit+0x6f/0xa0 [os_timer]
Jul 12 10:42:33 elm3b99 kernel:  [<c0139dca>] remove_wait_queue+0x1a/0x50
Jul 12 10:42:33 elm3b99 kernel:  [<c0135882>] worker_thread+0x182/0x240
Jul 12 10:42:33 elm3b99 kernel:  [<f8b332c0>] stp_exit_helper+0x0/0x10 
[os_timer]
Jul 12 10:42:33 elm3b99 kernel:  [<c0120000>] default_wake_function+0x0/0x10
Jul 12 10:42:33 elm3b99 kernel:  [<c0135700>] worker_thread+0x0/0x240
Jul 12 10:42:33 elm3b99 kernel:  [<c0139a7c>] kthread+0xac/0xb0
Jul 12 10:42:33 elm3b99 kernel:  [<c01399d0>] kthread+0x0/0xb0
Jul 12 10:42:33 elm3b99 kernel:  [<c0102445>] kernel_thread_helper+0x5/0x10
Jul 12 10:42:33 elm3b99 kernel: Code: 02 8b 44 24 28 c7 00 00 00 00 00 
8b 3c b5 1c a8 3c c0 8b 54 24 04 29 fb 89 1a 8b 44 24 2c 83 c4 14 5b 5e 
5f 5d c3 89 d8 e8 3c a8 <01> 00 85 c0 0f 85 19 ff ff ff 8b 44 24 28 8b 
4c 24 04 8b 54 24

Do you or anyone know what happen?
Thanks, Hien.