From: Darren Hart <dvhltc@us.ibm.com>
To: Jim Keniston <jkenisto@us.ibm.com>
Cc: systemtap <systemtap@sources.redhat.com>
Subject: Re: [Fwd: Re: stap early exit]
Date: Fri, 11 Apr 2008 19:20:00 -0000 [thread overview]
Message-ID: <1207868432.19797.21.camel@Aeon> (raw)
In-Reply-To: <1207840624.3989.5.camel@dyn9047018139.beaverton.ibm.com>
On Thu, 2008-04-10 at 08:17 -0700, Jim Keniston wrote:
> -------- Forwarded Message --------
> From: Frank Ch. Eigler <fche@redhat.com>
> To: Jim Keniston <jkenisto@us.ibm.com>
> Cc: systemtap <systemtap@sources.redhat.com>
> Subject: Re: stap early exit
> Date: Wed, 09 Apr 2008 22:05:02 -0400
>
> Jim Keniston <jkenisto@us.ibm.com> writes:
>
> > A SystemTap user at IBM is seeing his stap script terminate after a few
> > minutes, for no reason that he or I can figure out. The final message
> > is:
> > stapio:cleanup_and_exit:229 closing control channel
> >[...]
> > dvhltc@us.ibm.... stapio:cleanup_and_exit:229 closing control channel
> > Pass 5: run completed in 50usr/120sys/213446real ms.
>
> Indeed odd. A few things to try to help narrow it down:
>
> - check if the phenomenon reoccurs
It does.
> - check if it's a regular time interval
Appears to vary based on how much output I'm doing in the tap
> - change the "flag[tid()] = 0" to "delete flag[tid()]"
Good idea, done. Now the tapset will just stop... no longer getting the
cleanup_and_exit message.
> - try removing the print_backtrace() calls
This makes it run considerable longer.
> - run with "stap -t"
OK....
> - check whether any probes were skipped
Yes, I've seen between 30 and 100 probes skipped.
> - see whether the stap* processes may have operated under some
> resource limit like cpu time
Running as root, I think I'm OK here:
# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
max nice (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 40960
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
max rt priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 40960
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
> - try bumping up buffer size
How do I do that? the -s option? 'man stap' didn't state the default
for -s, what do you suggest I start with?
Thanks for all the tips!
>
>
> - FChE
>
--
Darren Hart
Real-Time Linux Team
IBM Linux Technology Center
next parent reply other threads:[~2008-04-10 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1207840624.3989.5.camel@dyn9047018139.beaverton.ibm.com>
2008-04-11 19:20 ` Darren Hart [this message]
2008-04-11 20:22 ` Frank Ch. Eigler
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=1207868432.19797.21.camel@Aeon \
--to=dvhltc@us.ibm.com \
--cc=jkenisto@us.ibm.com \
--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).