trace-cmd: Interrupted system call

[Dave Gilbert]

The trace-cmd in ubuntu ( 1.0.3-0ubuntu2 on saucy 3.11.0-4-generic ) gives 'interrupted system call' errors on the
example uses I could find.
Note that this also happens with the trace-cmd from Eric Miao's ppa referenced in bug 1068464,
but it all works fine if I build from current trace-cmd git

---------- Output from ubuntu version

root@saucy:~# trace-cmd record -e ext4 ls
disable all
enable ext4
path = /sys/kernel/debug/tracing/events/ext4/enable
path = /sys/kernel/debug/tracing/events/*/ext4/enable
0 Downloads Pictures trace-cmd trace.dat.cpu0 trace.dat.cpu3
Desktop examples.desktop Public trace-cmd_2.0.1-0ubuntu2_amd64.deb trace.dat.cpu1 Videos
Documents Music Templates trace.dat trace.dat.cpu2
trace-cmd: Interrupted system call
  recorder error in splice input
trace-cmd: Interrupted system call
  recorder error in splice input
trace-cmd: Interrupted system call
  recorder error in splice input
trace-cmd: Interrupted system call
  recorder error in splice input
uoffset=472000
offset=472000
offset=472000
offset=472000
Kernel buffer statistics:
  Note: "entries" are the entries left in the kernel ring buffer and are not
        recorded in the trace data. They should all be zero.

CPU: 0
entries: 0
overrun: 0
commit overrun: 0
bytes: 0
oldest event ts: 0.000000
now ts: 42714.021704
dropped events: 0
read events: 0

CPU: 1
entries: 4
overrun: 0
commit overrun: 0
bytes: 168
oldest event ts: 42713.903903
now ts: 42714.021841
dropped events: 0
read events: 0

CPU: 2
entries: 0
overrun: 0
commit overrun: 0
bytes: 0
oldest event ts: 0.000000
now ts: 42714.021978
dropped events: 0
read events: 0

CPU: 3
entries: 0
overrun: 0
commit overrun: 0
bytes: 0
oldest event ts: 0.000000
now ts: 42714.022127
dropped events: 0
read events: 0

root@saucy:~# trace-cmd report
version = 6
trace-cmd: No such file or directory
  bad op token {
  failed to read event print fmt for kvm_mmu_get_page
  bad op token {
  failed to read event print fmt for kvm_mmu_sync_page
  bad op token {
  failed to read event print fmt for kvm_mmu_unsync_page
  bad op token {
  failed to read event print fmt for kvm_mmu_prepare_zap_page
  function is_writable_pte not defined
  failed to read event print fmt for fast_page_fault
  Error: expected type 4 but read 7
  Error: expected type 5 but read 0
  failed to read event print fmt for kvm_apic
  Error: expected type 5 but read 4
  Error: expected type 5 but read 0
  failed to read event print fmt for kvm_exit
  Error: expected type 4 but read 7
  Error: expected type 5 but read 0
  failed to read event print fmt for kvm_inj_exception
  Error: expected type 5 but read 4
  Error: expected type 5 but read 0
  failed to read event print fmt for kvm_nested_vmexit
  Error: expected type 5 but read 4
  Error: expected type 5 but read 0
  failed to read event print fmt for kvm_nested_vmexit_inject
  function __print_hex not defined
  failed to read event print fmt for kvm_emulate_insn
  Error: expected type 4 but read 7
  Error: expected type 5 but read 0
  failed to read event print fmt for kvm_userspace_exit
  function sizeof not defined
  failed to read event print fmt for binder_command
  function sizeof not defined
  failed to read event print fmt for binder_return
  function scsi_trace_parse_cdb not defined
  failed to read event print fmt for scsi_dispatch_cmd_start
  function scsi_trace_parse_cdb not defined
  failed to read event print fmt for scsi_dispatch_cmd_error
  function scsi_trace_parse_cdb not defined
  failed to read event print fmt for scsi_dispatch_cmd_done
  function scsi_trace_parse_cdb not defined
  failed to read event print fmt for scsi_dispatch_cmd_timeout
  Error: expected type 5 but read 4
  failed to read event print fmt for ext4_es_lookup_extent_exit
  Error: expected type 5 but read 4
  failed to read event print fmt for do_sys_open
  Error: expected type 5 but read 4
  failed to read event print fmt for open_exec
  function xen_hypercall_name not defined
  failed to read event print fmt for xen_mc_entry
  function xen_hypercall_name not defined
  failed to read event print fmt for xen_mc_extend_args
  function sizeof not defined
  failed to read event print fmt for xen_mmu_set_pte
  function sizeof not defined
  failed to read event print fmt for xen_mmu_set_pte_atomic
  function sizeof not defined
  failed to read event print fmt for xen_mmu_set_domain_pte
  function sizeof not defined
  failed to read event print fmt for xen_mmu_set_pte_at
  function sizeof not defined
  failed to read event print fmt for xen_mmu_set_pmd
  function sizeof not defined
  failed to read event print fmt for xen_mmu_set_pud
  function sizeof not defined
  failed to read event print fmt for xen_mmu_set_pgd
  function sizeof not defined
  failed to read event print fmt for xen_mmu_ptep_modify_prot_start
  function sizeof not defined
  failed to read event print fmt for xen_mmu_ptep_modify_prot_commit
CPU 0 is empty
CPU 1 is empty
CPU 2 is empty
CPU 3 is empty
cpus=4

----- and from git version (from http://git.kernel.org/cgit/linux/kernel/git/rostedt/trace-cmd.git 0f2c2fb5dc22fd95812c754ab4829ed7c26e8844)

root@saucy:~# ./trace-cmd/trace-cmd record -e ext4 ls
/sys/kernel/debug/tracing/events/ext4/filter
/sys/kernel/debug/tracing/events/*/ext4/filter
0 Downloads Pictures trace-cmd trace.dat.cpu0 trace.dat.cpu3
Desktop examples.desktop Public trace-cmd_2.0.1-0ubuntu2_amd64.deb trace.dat.cpu1 Videos
Documents Music Templates trace.dat trace.dat.cpu2
Kernel buffer statistics:
  Note: "entries" are the entries left in the kernel ring buffer and are not
        recorded in the trace data. They should all be zero.

CPU: 0
entries: 0
overrun: 0
commit overrun: 0
bytes: 0
oldest event ts: 0.000000
now ts: 43265.666262
dropped events: 0
read events: 0

CPU: 1
entries: 0
overrun: 0
commit overrun: 0
bytes: 168
oldest event ts: 43265.664308
now ts: 43265.666397
dropped events: 0
read events: 4

CPU: 2
entries: 0
overrun: 0
commit overrun: 0
bytes: 0
oldest event ts: 0.000000
now ts: 43265.666521
dropped events: 0
read events: 0

CPU: 3
entries: 0
overrun: 0
commit overrun: 0
bytes: 0
oldest event ts: 0.000000
now ts: 43265.666642
dropped events: 0
read events: 0

CPU0 data recorded at offset=0x3de000
    0 bytes in size
CPU1 data recorded at offset=0x3de000
    4096 bytes in size
CPU2 data recorded at offset=0x3df000
    0 bytes in size
CPU3 data recorded at offset=0x3df000
    0 bytes in size
root@saucy:~#

root@saucy:~# ./trace-cmd/trace-cmd report
version = 6
CPU 0 is empty
CPU 2 is empty
CPU 3 is empty
cpus=4
              ls-13826 [001] 43265.664308: ext4_es_lookup_extent_enter: dev 253,1 ino 262579 lblk 0
              ls-13826 [001] 43265.664310: ext4_es_lookup_extent_exit: dev 253,1 ino 262579 found 1 [0/1) 1062889 W
              ls-13826 [001] 43265.664349: ext4_journal_start: dev 253,1 blocks, 2 rsv_blocks, 0 caller ext4_dirty_inode+0x2a
              ls-13826 [001] 43265.664350: ext4_mark_inode_dirty: dev 253,1 ino 262579 caller ext4_dirty_inode+0x40

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: trace-cmd 1.0.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Sat Sep 7 23:40:07 2013
Dependencies:
 gcc-4.8-base 4.8.1-10ubuntu1
 libc6 2.17-91ubuntu1
 libgcc1 1:4.8.1-10ubuntu1
 multiarch-support 2.17-91ubuntu1
InstallationDate: Installed on 2013-05-06 (124 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130506)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: trace-cmd
UpgradeStatus: No upgrade log present (probably fresh install)

[Seth Forshee (sforshee)]

trace-cmd 2.2.1 is now available in trusty, and I'm unable to reproduce this problem there. Can you check and see if you still see this issue?

[Dave Gilbert (ubuntu-treblig)]

Yeh, it seems to work in Trusty with the 2.3.0-1 which Trusty seems to have now (with 3.12.0-7-generic #15). Marking fixed-released