From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Pavan Naregundi <pavan.naregundi@in.ibm.com>
Cc: Mark Wielaard <mjw@redhat.com>, systemtap@sourceware.org
Subject: Re: Systemtap snap:b6371390 test on kernel 2.6.30-rc3-git2
Date: Tue, 28 Apr 2009 06:07:00 -0000 [thread overview]
Message-ID: <20090428060730.GB1531@in.ibm.com> (raw)
In-Reply-To: <OF7F01BC7C.C3DE65C3-ON652575A6.001DF96D-652575A6.00212F6D@in.ibm.com>
On Tue, Apr 28, 2009 at 11:30:09AM +0530, Pavan Naregundi wrote:
> Mark Wielaard <mjw@redhat.com> wrote on 04/27/2009 08:12:50 PM:
>
> > From:
> >
> > Mark Wielaard <mjw@redhat.com>
> >
> > To:
> >
> > Pavan Naregundi/India/IBM@IBMIN
> >
> > Cc:
> >
> > systemtap@sourceware.org
> >
> > Date:
> >
> > 04/27/2009 08:10 PM
> >
> > Subject:
> >
> > Re: Systemtap snap:b6371390 test on kernel 2.6.30-rc3-git2
> >
> > Hi Pavan,
> >
> > On Mon, 2009-04-27 at 17:17 +0530, Pavan Naregundi wrote:
> > > Results of systemtap snap:b6371390 test on kernel 2.6.30-rc3-git2
> > > Arch: ppc64
> > >
> > > Please contact me, for any other details.
> >
> > Thanks for testing this combination. Which elfutils version did you use?
>
> elfutils-0.141
>
> >
> > > Unexpected failures
> > > =============================
> > > FAIL: LOCAL1 (0)
> >
> > I have seen this fail sporadically, is it failing always for you?
> I have seen this every time.
>
> >
> > > FAIL: STRUCT1 (0)
> >
> > Could you post the relevant part of the testsuite/systemtap.log?
>
> Running /home/pavan/systemtap/src/testsuite/systemtap.base/alternatives.exp
> ...
> starting stap -vu -p2 -e {
> probe kernel.function("sys_getrlimit") { x = $z; }
> }
> Pass 1: parsed user script and 53 library script(s) in 320usr/20sys/344real
> ms.^M
> Pass 1: parsed user script and 53 library script(s) in 320usr/20sys/344real
> ms.^M
> wait results: 15196 exp6 0 1
> FAIL: LOCAL1 (0)
> starting stap -vu -p2 -e {
> probe kernel.function("sys_getrlimit") { rlim_cur = $rlim->rlim_cud; }
> }
This and some of the others here are victims of SYSCALL_WRAPPERS
changes. I have a patch (yet to be checked in) for this. See bz10007.
Can you please try with the patch at:
http://sources.redhat.com/bugzilla/attachment.cgi?id=3896&action=view
Ananth
next prev parent reply other threads:[~2009-04-28 6:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 11:49 Pavan Naregundi
2009-04-27 14:43 ` Mark Wielaard
2009-04-28 5:11 ` Pavan Naregundi
2009-04-28 6:02 ` Pavan Naregundi
2009-04-28 6:07 ` Ananth N Mavinakayanahalli [this message]
2009-04-29 9:37 ` Mark Wielaard
2009-04-29 19:01 ` Josh Stone
2009-04-29 9:41 ` Mark Wielaard
2009-04-28 6:56 ` Ananth N Mavinakayanahalli
2009-04-29 8:57 ` Mark Wielaard
2009-04-29 9:26 ` Ananth N Mavinakayanahalli
2009-04-29 12:08 ` Mark Wielaard
2009-04-29 12:21 ` Ananth N Mavinakayanahalli
2009-04-29 12:27 ` Mark Wielaard
2009-04-29 13:15 ` David Smith
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=20090428060730.GB1531@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=mjw@redhat.com \
--cc=pavan.naregundi@in.ibm.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).