From: Martin Hunt <hunt@redhat.com>
To: sourceware-bugzilla@sourceware.org
Cc: systemtap@sources.redhat.com
Subject: Re: [Bug kprobes/2726] systemtap.base/probefunc.exp crash in kernel/module.c:2114 on RHEL4
Date: Fri, 16 Jun 2006 15:33:00 -0000 [thread overview]
Message-ID: <1150472020.2571.5.camel@dragon> (raw)
In-Reply-To: <20060616104715.5498.qmail@sourceware.org>
On Fri, 2006-06-16 at 10:47 +0000, ananth at in dot ibm dot com wrote:
> ------- Additional Comments From ananth at in dot ibm dot com 2006-06-16 10:47 -------
> Created an attachment (id=1097)
> --> (http://sourceware.org/bugzilla/attachment.cgi?id=1097&action=view)
> ps aux output indicating systemtap tasks in interruptible sleep states
>
> Sometime between the 3 June and 10 June snapshots, a patch has sneaked in to
> systemtap that causes the systemtap tasks to hang around in interruptible sleep
> states, long after the test has been terminated. Attached here is the ps aux
> output indicating this. I'll attach a sysrq-t output in a subsequent
> attachment.
>
> I am not certain if this has something to do with the problem being
> investigated on this bug though.
AFAIK, that problem existed only over this last weekend. Is this
current code?
next prev parent reply other threads:[~2006-06-16 15:33 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
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 [this message]
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=1150472020.2571.5.camel@dragon \
--to=hunt@redhat.com \
--cc=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).