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]

Re: Arm Fedora 18 systemtap test results


Hi, Will -

wcohen wrote:

> I have a Fedora 18 arm environment set up and ran the systemtap tests
> on the git repo and posted them to dejazilla: [...]

Thank you.


> probed functions not available or found in the kernel
> FAIL: ./systemtap.examples/network/tcpipstat build (ip_route_input inlined)
> FAIL: buildok/ipmib-all-probes.stp (ip_route_input inlined)
> FAIL: buildok/ipmib-detailed.stp (ip_route_input inlined)
> FAIL: buildok/nfs-all-probes.stp (nfs.proc3.commit_done)
> FAIL: buildok/syscalls-arch-detailed.stp (arm missing syscall.sigaltstack) **
> FAIL: buildok/eighteen.stp (can't find kernel.function(**audit_getname")

Could you fix these, but changing the testsuite to (also?) look for
something that does exist on these ARM kernels?


> flagged as needing
> user-space facilities not available without kernel CONFIG_UTRACE or CONFIG_TRACEPOINTS/CONFIG_ARCH_SUPPORTS_UPROBES/CONFIG_UPROBES
>
> FAIL: bad-code
> FAIL: poll_map (0)
> FAIL: compiling pr10854.stp: user-space facilities not available without kernel CONFIG_UTRACE or CONFIG_TRACEPOINTS/CONFIG_ARCH_SUPPORTS_UPROBES/CONFIG_UPROBES
> FAIL: probefunc:.statement.(0xaddr).absolute startup (eof)
> FAIL: probefunc:kernel.function("scheduler_tick") startup (eof)
> FAIL: probefunc:kernel.function("context_switch").inline startup (eof)
> FAIL: utf_pretty
> FAIL: utf_user_trunc
> FAIL: ./systemtap.examples/general/para-callgraph-verbose build
> FAIL: ./systemtap.examples/general/para-callgraph build
> FAIL: ./systemtap.examples/io/inodewatch build
> FAIL: ./systemtap.examples/io/inodewatch2 build
> FAIL: ./systemtap.examples/io/traceio2 build
> FAIL: ./systemtap.examples/network/socket-trace build
> FAIL: ./systemtap.examples/process/auditbt build
> FAIL: ./systemtap.examples/profiling/fntimes build
> FAIL: ./systemtap.examples/profiling/functioncallcount build
> FAIL: buildok/context-symbols-embedded.stp
> FAIL: buildok/memory.stp
> FAIL: buildok/nd_syscalls-all-probes.stp
> FAIL: buildok/nd_syscalls2-detailed.stp
> FAIL: buildok/scsi-detailed.stp
> FAIL: 32-bit access nd_syscall
> FAIL: 32-bit acct nd_syscall
> FAIL: 32-bit alarm nd_syscall
> FAIL: 32-bit chmod nd_syscall
> FAIL: 32-bit clock nd_syscall
> FAIL: 32-bit dir nd_syscall
> FAIL: 32-bit dup nd_syscall
> FAIL: 32-bit eventfd nd_syscall
> FAIL: 32-bit forkwait nd_syscall
> FAIL: 32-bit futimes nd_syscall
> FAIL: 32-bit inotify nd_syscall
> FAIL: 32-bit itimer nd_syscall
> FAIL: 32-bit link nd_syscall
> FAIL: 32-bit mmap nd_syscall
> FAIL: 32-bit mount nd_syscall
> FAIL: 32-bit net1 nd_syscall
> FAIL: 32-bit openclose nd_syscall
> FAIL: 32-bit pipe nd_syscall
> FAIL: 32-bit poll nd_syscall
> FAIL: 32-bit readwrite nd_syscall
> FAIL: 32-bit rt_signal nd_syscall
> FAIL: 32-bit select nd_syscall
> FAIL: 32-bit sendfile nd_syscall
> FAIL: 32-bit signal nd_syscall
> FAIL: 32-bit signalfd nd_syscall
> FAIL: 32-bit stat nd_syscall
> FAIL: 32-bit statfs nd_syscall
> FAIL: 32-bit swap nd_syscall
> FAIL: 32-bit sync nd_syscall
> FAIL: 32-bit timer nd_syscall
> FAIL: 32-bit trunc nd_syscall
> FAIL: 32-bit uid nd_syscall
> FAIL: 32-bit umask nd_syscall
> FAIL: 32-bit unlink nd_syscall
> FAIL: 32-bit alarm syscall
> FAIL: 32-bit stat syscall

These should more or less work; could you dig a bit deeper as to why
they don't?


- FChE


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