This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug testsuite/13193] Running bz6503.exp results in unresponsive/crashed machine
- From: "masami.hiramatsu.pt at hitachi dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 10 Nov 2011 14:28:08 +0000
- Subject: [Bug testsuite/13193] Running bz6503.exp results in unresponsive/crashed machine
- Auto-submitted: auto-generated
- References: <bug-13193-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13193
--- Comment #5 from Masami Hiramatsu <masami.hiramatsu.pt at hitachi dot com> 2011-11-10 14:28:08 UTC ---
(In reply to comment #4)
> I strongly suspect this is a kernel bug that we'll just have to work
> around somehow, perhaps by teaching staprun to turn off kprobes optimization.
Hmm, it seems that an aggr probe(which wasn't optimized) was gone and child
probes were also gone, but the aggr probe was not released and on the kprobe's
hash table.
BTW, I'd like to get more information:
- does this happen on x86-64 too?
- does this happen on upstream kernel too?
- what the actual version of systemtap did you use?
- is there any C code of stap code?
I'm not sure why systemtap tries to put a probe on the "TAIL" of a function in
.init.text...
[157018.227386] Warning: found a stray unused aggrprobe@f8942011
[157018.228133] [<f8942011>] ? jffs2_compressors_init+0x11/0x11 [jffs2]
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.