[Bug tapsets/5150] New: buildok/nfs-all-probes.stp fails

public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed

* [Bug tapsets/5150] New: buildok/nfs-all-probes.stp fails
@ 2007-10-09 15:33 wcohen at redhat dot com
  2007-10-09 16:53 ` [Bug tapsets/5150] " mmlnx at us dot ibm dot com
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: wcohen at redhat dot com @ 2007-10-09 15:33 UTC (permalink / raw)
  To: systemtap

With the 2.6.23-rc9 kernel the probe points for some of the nfs.* nfs.*.* probes
are available.

Running /home/wcohen/stap_snap_200710081315/src/testsuite/buildok/nfs-all-probes.stp
starting
/home/wcohen/stap_snap_200710081315/src/testsuite/buildok/nfs-all-probes.stp
spawn1 stap -p4
/home/wcohen/stap_snap_200710081315/src/testsuite/buildok/nfs-all-probes.stp
semantic error: no match for probe point while resolving probe point
nfs.fop.sendfile

semantic error: no match for probe point while resolving probe point
nfs.fop.sendfile

semantic error: no match for probe point while resolving probe point
nfs.fop.sendfile.return


semantic error: no match for probe point while resolving probe point
nfs.fop.sendfile.return

semantic error: no match for probe point while resolving probe point
nfs.proc3.commit


semantic error: no match for probe point while resolving probe point
nfs.proc3.commit

semantic error: no match for probe point while resolving probe point
nfs.proc4.commit


semantic error: no match for probe point while resolving probe point
nfs.proc4.commit

semantic error: no match for probe point while resolving probe point nfs.proc2.read


semantic error: no match for probe point while resolving probe point nfs.proc2.read

semantic error: no match for probe point while resolving probe point nfs.proc3.read


semantic error: no match for probe point while resolving probe point nfs.proc3.read

semantic error: no match for probe point while resolving probe point nfs.proc4.read


semantic error: no match for probe point while resolving probe point nfs.proc4.read

semantic error: no match for probe point while resolving probe point nfs.proc.read


semantic error: no match for probe point while resolving probe point nfs.proc.read

semantic error: no match for probe point while resolving probe point nfs.proc2.write


semantic error: no match for probe point while resolving probe point nfs.proc2.write

semantic error: no match for probe point while resolving probe point nfs.proc3.write


semantic error: no match for probe point while resolving probe point nfs.proc3.write

semantic error: no match for probe point while resolving probe point nfs.proc4.write


semantic error: no match for probe point while resolving probe point nfs.proc4.write

semantic error: no match for probe point while resolving probe point nfs.proc.write


semantic error: no match for probe point while resolving probe point nfs.proc.write

semantic error: no match for probe point while resolving probe point nfs.proc.commit


semantic error: no match for probe point while resolving probe point nfs.proc.commit

semantic error: no match for probe point while resolving probe point
nfs.proc2.read.return


semantic error: no match for probe point while resolving probe point
nfs.proc2.read.return

semantic error: no match for probe point while resolving probe point
nfs.proc3.read.return


semantic error: no match for probe point while resolving probe point
nfs.proc3.read.return

semantic error: no match for probe point while resolving probe point
nfs.proc4.read.return


semantic error: no match for probe point while resolving probe point
nfs.proc4.read.return

semantic error: no match for probe point while resolving probe point
nfs.proc.read.return


semantic error: no match for probe point while resolving probe point
nfs.proc.read.return

semantic error: no match for probe point while resolving probe point
nfs.proc2.write.return


semantic error: no match for probe point while resolving probe point
nfs.proc2.write.return

semantic error: no match for probe point while resolving probe point
nfs.proc3.write.return


semantic error: no match for probe point while resolving probe point
nfs.proc3.write.return

semantic error: no match for probe point while resolving probe point
nfs.proc4.write.return


semantic error: no match for probe point while resolving probe point
nfs.proc4.write.return

semantic error: no match for probe point while resolving probe point
nfs.proc.write.return


semantic error: no match for probe point while resolving probe point
nfs.proc.write.return

semantic error: no match for probe point while resolving probe point
nfs.proc3.commit.return


semantic error: no match for probe point while resolving probe point
nfs.proc3.commit.return

semantic error: no match for probe point while resolving probe point
nfs.proc4.commit.return


semantic error: no match for probe point while resolving probe point
nfs.proc4.commit.return

semantic error: no match for probe point while resolving probe point
nfs.proc.commit.return


semantic error: no match for probe point while resolving probe point
nfs.proc.commit.return

Pass 2: analysis failed.  Try again with more '-v' (verbose) options.


Pass 2: analysis failed.  Try again with more '-v' (verbose) options.

wait results: 2766 exp15 0 1
FAIL: buildok/nfs-all-probes.stp

-- 
           Summary: buildok/nfs-all-probes.stp fails
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: wcohen at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=5150

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug tapsets/5150] buildok/nfs-all-probes.stp fails
  2007-10-09 15:33 [Bug tapsets/5150] New: buildok/nfs-all-probes.stp fails wcohen at redhat dot com
@ 2007-10-09 16:53 ` mmlnx at us dot ibm dot com
  2009-11-09 15:58 ` dsmith at redhat dot com
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: mmlnx at us dot ibm dot com @ 2007-10-09 16:53 UTC (permalink / raw)
  To: systemtap


------- Additional Comments From mmlnx at us dot ibm dot com  2007-10-09 16:53 -------
This is a new test that exposes nfs tapset bugs that have been around for a
while.  Looks like some or all of the functions associated with these probes
went away around 2.6.21.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=5150

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug tapsets/5150] buildok/nfs-all-probes.stp fails
  2007-10-09 15:33 [Bug tapsets/5150] New: buildok/nfs-all-probes.stp fails wcohen at redhat dot com
  2007-10-09 16:53 ` [Bug tapsets/5150] " mmlnx at us dot ibm dot com
@ 2009-11-09 15:58 ` dsmith at redhat dot com
  2009-11-09 16:00 ` dsmith at redhat dot com
  2009-11-16 19:01 ` dsmith at redhat dot com
  3 siblings, 0 replies; 5+ messages in thread
From: dsmith at redhat dot com @ 2009-11-09 15:58 UTC (permalink / raw)
  To: systemtap


------- Additional Comments From dsmith at redhat dot com  2009-11-09 15:58 -------
*** Bug 10900 has been marked as a duplicate of this bug. ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dsmith at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=5150

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug tapsets/5150] buildok/nfs-all-probes.stp fails
  2007-10-09 15:33 [Bug tapsets/5150] New: buildok/nfs-all-probes.stp fails wcohen at redhat dot com
  2007-10-09 16:53 ` [Bug tapsets/5150] " mmlnx at us dot ibm dot com
  2009-11-09 15:58 ` dsmith at redhat dot com
@ 2009-11-09 16:00 ` dsmith at redhat dot com
  2009-11-16 19:01 ` dsmith at redhat dot com
  3 siblings, 0 replies; 5+ messages in thread
From: dsmith at redhat dot com @ 2009-11-09 16:00 UTC (permalink / raw)
  To: systemtap


------- Additional Comments From dsmith at redhat dot com  2009-11-09 16:00 -------
(Here's some info copied over from bug #10900 with up-to-date testing results.)

There are several problems in the nfs tapset.  During testing I used:
- a x86_64 rhel5 system (kernel 2.6.18-164.2.1.el5)
- a ia64 rhel5 system (kernel 2.6.18-157.el5)
- a rawhide system (kernel 2.6.31.5-96.fc12.x86_64.debug).

- probes 'nfs.fop.fsync' & 'nfs.fop.fsync.return' didn't work on rawhide

- probes 'nfs.fop.sendfile' & 'nfs.fop.sendfile.return' didn't work on rawhide

- probes 'nfs.fop.check_flags' & 'nfs.fop.check_flags.return' don't work on
either ia64 rhel5 or rawhide.  They did work on the x86_64 rhel5 system.

- probe 'nfs.aop.readpages.return' has a mistake in it. 'size = retstr' should
be 'size = $return' (to match the other return probes)

- probes 'nfs.aop.prepare_write' & 'nfs.aop.prepare_write.return' don't work on
either rhel5 or rawhide

- probes 'nfs.aop.commit_write' & 'nfs.aop.commit_write.return' don't work on
either rhel5 or rawhide

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=5150

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug tapsets/5150] buildok/nfs-all-probes.stp fails
  2007-10-09 15:33 [Bug tapsets/5150] New: buildok/nfs-all-probes.stp fails wcohen at redhat dot com
                   ` (2 preceding siblings ...)
  2009-11-09 16:00 ` dsmith at redhat dot com
@ 2009-11-16 19:01 ` dsmith at redhat dot com
  3 siblings, 0 replies; 5+ messages in thread
From: dsmith at redhat dot com @ 2009-11-16 19:01 UTC (permalink / raw)
  To: systemtap


------- Additional Comments From dsmith at redhat dot com  2009-11-16 19:00 -------
(In reply to comment #3)
> (Here's some info copied over from bug #10900 with up-to-date testing results.)
...
> - probes 'nfs.aop.prepare_write' & 'nfs.aop.prepare_write.return' don't work on
> either rhel5 or rawhide
> 
> - probes 'nfs.aop.commit_write' & 'nfs.aop.commit_write.return' don't work on
> either rhel5 or rawhide

Fixed the prepare_write()/commit_write() problem in commit 1bc3d8e.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|systemtap at sources dot    |dsmith at redhat dot com
                   |redhat dot com              |
             Status|NEW                         |ASSIGNED


http://sourceware.org/bugzilla/show_bug.cgi?id=5150

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2009-11-16 19:01 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-10-09 15:33 [Bug tapsets/5150] New: buildok/nfs-all-probes.stp fails wcohen at redhat dot com
2007-10-09 16:53 ` [Bug tapsets/5150] " mmlnx at us dot ibm dot com
2009-11-09 15:58 ` dsmith at redhat dot com
2009-11-09 16:00 ` dsmith at redhat dot com
2009-11-16 19:01 ` dsmith at redhat dot com

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).