From: fche@redhat.com (Frank Ch. Eigler)
To: ch huang <justlooks@gmail.com>
Cc: systemtap@sourceware.org
Subject: Re: problem in run systemtap script
Date: Tue, 13 Mar 2012 14:20:00 -0000 [thread overview]
Message-ID: <y0m4ntsvazm.fsf@fche.csb> (raw)
In-Reply-To: <CACeqxwQRVHN0_wjMqpmi1WfaF6C6OZazvTscyzRX-8f5ww5VyA@mail.gmail.com> (ch huang's message of "Tue, 13 Mar 2012 16:17:23 +0800")
ch huang <justlooks@gmail.com> writes:
> how to handle this?
> [...]
> WARNING: probe module("ext3").function("ext3_journalled_set_page_dirty@fs/ext3/inode.c:1780").call
> (address 0xffffffff8804dff8) registration error (rc -22)
> WARNING: probe module("ext3").function("bget_one@fs/ext3/inode.c:1419").call
> (address 0xffffffff8804d50a) registration error (rc -22)
> [...]
This could be the kernel kprobes limitation also mentioned in
<https://bugzilla.redhat.com/show_bug.cgi?id=801785>. Some functions
will simply miss being probed. But note that they are all warnings.
> ERROR: probe overhead exceeded threshold
> WARNING: Number of errors: 1, skipped probes: 0
This would be the real problem. Rerun with -DSTP_NO_OVERLOAD to
disable the overload-prevention mechanism.
- FChE
prev parent reply other threads:[~2012-03-13 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 8:17 ch huang
2012-03-13 14:20 ` Frank Ch. Eigler [this message]
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=y0m4ntsvazm.fsf@fche.csb \
--to=fche@redhat.com \
--cc=justlooks@gmail.com \
--cc=systemtap@sourceware.org \
/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).