From: "ananth at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2726] systemtap.base/probefunc.exp crash in kernel/module.c:2114 on RHEL4
Date: Tue, 13 Jun 2006 07:07:00 -0000 [thread overview]
Message-ID: <20060613070657.16885.qmail@sourceware.org> (raw)
In-Reply-To: <20060601192814.2726.wcohen@redhat.com>
------- 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.
next prev parent reply other threads:[~2006-06-13 7:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 19:28 [Bug kprobes/2726] New: " wcohen at redhat dot com
2006-06-01 19:58 ` Vara Prasad
2006-06-01 19:58 ` [Bug kprobes/2726] " prasadav at us dot ibm dot com
2006-06-01 20:30 ` wcohen at redhat dot com
2006-06-02 5:13 ` bibo dot mao at intel dot com
2006-06-05 17:29 ` wcohen at redhat dot com
2006-06-05 19:24 ` wcohen at redhat dot com
2006-06-12 14:48 ` ananth at in dot ibm dot com
2006-06-12 14:55 ` ananth at in dot ibm dot com
2006-06-12 18:38 ` wcohen at redhat dot com
2006-06-12 18:52 ` wcohen at redhat dot com
2006-06-13 7:07 ` ananth at in dot ibm dot com [this message]
2006-06-13 22:59 ` wcohen at redhat dot com
2006-06-15 19:36 ` wcohen at redhat dot com
2006-06-15 19:51 ` wcohen at redhat dot com
2006-06-16 10:11 ` ananth at in dot ibm dot com
2006-06-16 10:47 ` ananth at in dot ibm dot com
2006-06-16 15:33 ` Martin Hunt
2006-06-16 10:52 ` ananth at in dot ibm dot com
2006-06-16 15:33 ` hunt at redhat dot com
2006-06-16 19:58 ` wcohen at redhat dot com
2006-06-16 20:04 ` fche at redhat dot com
2006-06-16 20:29 ` wcohen at redhat dot com
2006-06-19 6:35 ` 76306 dot 1226 at compuserve dot com
2006-06-19 7:18 ` ananth at in dot ibm dot com
2006-06-19 9:23 ` ananth at in dot ibm dot com
2006-06-20 6:51 ` 76306 dot 1226 at compuserve dot com
2006-10-12 15:30 ` wcohen at redhat dot com
2006-11-01 21:37 ` fche at redhat dot com
2006-11-08 23:24 ` jlayton at redhat dot com
2006-11-16 18:07 ` wcohen at redhat dot com
2006-11-16 23:37 ` wcohen at redhat dot com
2007-01-16 16:57 ` wcohen at redhat dot com
2007-01-16 16:58 ` wcohen at redhat dot com
2007-01-16 17:00 ` wcohen at redhat dot com
2007-03-01 21:25 ` wcohen at redhat dot com
2007-05-01 9:34 ` nclsfabre at yahoo dot fr
2007-05-01 12:51 ` fche at redhat dot com
2007-06-22 11:49 ` ananth at in dot ibm dot com
2007-06-22 15:17 ` wcohen at redhat dot com
2010-04-08 19:17 ` fche at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060613070657.16885.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).