unable to run latencytop

[Viktor Szathmáry]

When running latencytop as root:

mount: none is already mounted or /sys/kernel/debug busy
Please enable the CONFIG_LATENCYTOP configuration in your kernel.
Exiting...

# uname -a
Linux foo 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

# lsb-release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial

LatencyTop used to work Ubuntu 14.04 distributions.
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Sep 18 17:01 seq
 crw-rw---- 1 root audio 116, 33 Sep 18 17:01 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 16.04
Ec2AMI: ami-643d4217
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-west-1c
Ec2InstanceType: m4.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Xen HVM domU
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=fd4912f3-5c00-4f21-93bb-6027f40d322a ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-36-generic N/A
 linux-backports-modules-4.4.0-36-generic N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial ec2-images
Uname: Linux 4.4.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 05/12/2016
dmi.bios.vendor: Xen
dmi.bios.version: 4.2.amazon
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
dmi.product.name: HVM domU
dmi.product.version: 4.2.amazon
dmi.sys.vendor: Xen

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1624885

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Viktor Szathmáry (phraktle)]

apport information

[Viktor Szathmáry (phraktle)]

apport information

[Viktor Szathmáry (phraktle)]

apport information

[Viktor Szathmáry (phraktle)]

apport information

[Viktor Szathmáry (phraktle)]

apport information

[Viktor Szathmáry (phraktle)]

apport information

[Viktor Szathmáry (phraktle)]

apport information

[Viktor Szathmáry (phraktle)]

apport information

[Alberto Salvia Novella (es20490446e)]

The last commit in latencytop was in 2009 (https://www.openhub.net/p/latencytop/commits/summary), so it could be that the project is dead.

[Adam Logghe (alogghe)]

I think this is simply turned off in the kernel as the error suggests.

grep LATENCY /boot/config*

shows

# CONFIG_LATENCYTOP is not set

I doubt this will be turned on and your best bet is to recompile your kernel or better perhaps look into newer methods of looking at linux latency issues, this might be a good start -

http://www.brendangregg.com/blog/2016-10-27/dtrace-for-linux-2016.html

Cheers.