'perf record' does not work

Bug #1750479 reported by Steve Barcomb
20
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

$ perf archive
perf: 'archive' is not a perf-command. See 'perf --help'.

$ perf --help

 usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS]

 The most commonly used perf commands are:
   annotate Read perf.data (created by perf record) and display annotated code
   archive Create archive with object files with build-ids found in perf.data file <-----
   bench General framework for benchmark suites
   buildid-cache Manage build-id cache.
   buildid-list List the buildids in a perf.data file
   c2c Shared Data C2C/HITM Analyzer.
   config Get and set variables in a configuration file.
   data Data file related processing
   diff Read perf.data files and display the differential profile
   evlist List the event names in a perf.data file
   ftrace simple wrapper for kernel's ftrace functionality
   inject Filter to augment the events stream with additional information
   kallsyms Searches running kernel for symbols
   kmem Tool to trace/measure kernel memory properties
   kvm Tool to trace/measure kvm guest os
   list List all symbolic event types
   lock Analyze lock events
   mem Profile memory accesses
   record Run a command and record its profile into perf.data
   report Read perf.data (created by perf record) and display the profile
   sched Tool to trace/measure scheduler properties (latencies)
   script Read perf.data (created by perf record) and display trace output
   stat Run a command and gather performance counter statistics
   test Runs sanity tests.
   timechart Tool to visualize total system behavior during a workload
   top System profiling tool.
   probe Define new dynamic tracepoints
   trace strace inspired tool

 See 'perf help COMMAND' for more information on a specific command.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-tools-4.13.0-32-generic 4.13.0-32.35
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sbarcomb 2227 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 19 20:53:27 2018
HibernationDevice: RESUME=UUID=ac3f108f-4494-4f48-ae8c-fbab8a509ffc
InstallationDate: Installed on 2017-10-19 (123 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IwConfig:
 lo no wireless extensions.

 enp5s0 no wireless extensions.

 tun0 no wireless extensions.
MachineType: Alienware Aurora-R4
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic N/A
 linux-firmware 1.169.3
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2013
dmi.bios.vendor: Alienware
dmi.bios.version: A11
dmi.board.name: 07JNH0
dmi.board.vendor: Alienware
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Alienware
dmi.chassis.version: 00
dmi.modalias: dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00:
dmi.product.family: 0
dmi.product.name: Aurora-R4
dmi.product.version: 00
dmi.sys.vendor: Alienware

Revision history for this message
Steve Barcomb (linuxpng) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc2

affects: linux (Ubuntu) → perf-tools-unstable (Ubuntu)
Changed in perf-tools-unstable (Ubuntu):
status: Confirmed → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
affects: perf-tools-unstable (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
Zeno (zeno-endemann) wrote :

Same problem on 17.10. The packaging seems to be broken; no perf-archive script is installed anywhere. All I can find is /usr/src/linux-headers-4.13.0-38/tools/perf/perf-archive.sh but that is not used

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Andrew Somerville (andy-somerville) wrote :

@jsalisbury? Why was this originally marked as incomplete?

Changed in linux (Ubuntu):
status: Expired → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.