From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24251 invoked by alias); 13 Mar 2012 14:20:39 -0000 Received: (qmail 24235 invoked by uid 22791); 13 Mar 2012 14:20:35 -0000 X-SWARE-Spam-Status: No, hits=-6.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 13 Mar 2012 14:20:16 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q2DEKFnT031464 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 13 Mar 2012 10:20:15 -0400 Received: from fche.csb (vpn-11-56.rdu.redhat.com [10.11.11.56]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q2DEKEcX004779; Tue, 13 Mar 2012 10:20:14 -0400 Received: by fche.csb (Postfix, from userid 2569) id 1951A5816B; Tue, 13 Mar 2012 10:20:14 -0400 (EDT) To: ch huang Cc: systemtap@sourceware.org Subject: Re: problem in run systemtap script References: From: fche@redhat.com (Frank Ch. Eigler) Date: Tue, 13 Mar 2012 14:20:00 -0000 In-Reply-To: (ch huang's message of "Tue, 13 Mar 2012 16:17:23 +0800") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2012-q1/txt/msg00293.txt.bz2 ch huang 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 . 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