This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug runtime/2511] Transport Changes needed for kernel >= 2.6.17.*


------- Additional Comments From zanussi at us dot ibm dot com  2006-04-04 14:17 -------
(In reply to comment #0)
> kernel: 2.6.17-rc1
> machine: ppc64
> systemtap: snapshot 20060401
> 
> When I run the systemtap , error message was printed:
> -----------------------------------------------------------------------
> Pass 5: starting run.
> Running sudo /usr/local/libexec/systemtap/stpd -u root -d 
> 9788 /tmp/stap9RBcE4/stap_9788.ko
> mount: fs type relayfs not supported by kernel
> /usr/local/autobench/sources/tracetool/systemtap/libexec/systemtap/stp_check: 
> Success
> Could not 
> execute /usr/local/autobench/sources/tracetool/systemtap/libexec/systemtap/stp_
> check
> Pass 5: run completed in 10usr/180sys/216real ms.
> Pass 5: run failed.  Try again with more '-v' (verbose) options.
> Running rm -rf /tmp/stap9RBcE4
> ---------------------------------------------------------------------------
> 
> I found it is due to relayfs as a stand-alone filesystem is gone, to be 
> replaced with the ability to use relayfs files from within sysfs. You can 
> refer to http://lwn.net/Articles/174592/
> 
> Now, relayfs is gone, and all check about relayfs in systemtap should be 
> modified.

OK, I just checked in a fix for this, please refresh from CVS and try again.

The problem was that the check in stp_check was based on the sysfs changes, but
the sysfs changes haven't made it in yet.

-- 


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

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]