This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug kprobes/2726] systemtap.base/probefunc.exp crash in kernel/module.c:2114 on RHEL4
- From: "ananth at in dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 13 Jun 2006 07:06:57 -0000
- Subject: [Bug kprobes/2726] systemtap.base/probefunc.exp crash in kernel/module.c:2114 on RHEL4
- References: <20060601192814.2726.wcohen@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From ananth at in dot ibm dot com 2006-06-13 07:06 -------
Created an attachment (id=1082)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=1082&action=view)
C module probing scheduler_tick()
I've now tried today's systemtap snapshot with UNI and SMP .39 kernels while
simultaneously running:
1. A kernel build
2. The scheduler_tick script (with a timeout of 5 seconds) in a loop (to
simulate any issues with module loading/unloading)
3. The C module probing scheduler_tick() (attached to this bug)
4. The strace-open.stp example from the systemtap tutorial
I haven't been able to see a problem or any fatal errors in the dmesg (except:
ERROR: user string copy fault at 0x080c571a near identifier '$filename' at
/usr/local/share/systemtap/tapset/syscalls2.stp:27:25
when running the strace-open.stp).
[root@...]# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Xeon(TM) CPU 2.80GHz
stepping : 7
cpu MHz : 2795.658
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr
bogomips : 5591.89
Will, could you please try recreating the problem with the plain C module?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2726
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.