Bug 6498

Summary:	Latencytop -d does not work for qemuppc and qemuarm
Product:	[Runtime] General Runtime	Reporter:	Catalin Scrieciu <catalin.scrieciu>
Component:	General Runtime	Assignee:	Unassigned <unassigned>
Status:	RESOLVED WONTFIX	QA Contact:	Juan Ramos <juan.fernandox.ramos.frayle>
Severity:	normal
Priority:	Low	CC:	alexandru.c.georgescu, jose.perez.carranza, richard.purdie, sgw
Version:	1.7
Target Milestone:	Future
Hardware:	Other
OS:	arm
Whiteboard:	Roxanna is no longer at Intel
OS type for building Yocto:	---	Type of Regression:	New (Never tested)
Verified:		Documentation change:	Don't know

Description Catalin Scrieciu 2014-07-01 14:46:51 UTC

While testing Yocto 1.7 M1 RC1 (poky 68824d9b8f6e290da078383316b3f4b732585f2b) we discovered that when executing latencytop -d the following output is diplayed:

root@qemuppc:~# latencytop -d
mount: none is already mounted or /sys/kernel/debug busy
root@qemuppc:~#

This is applicable for both qemuarm and qemuppc.

Comment 1 Saul Wold 2014-07-02 16:05:55 UTC

sysfs.sh already mounts debugfs, the message is harmess, we could add a check 
to ensure it's not mounted before trying to mount it.

Comment 2 Saul Wold 2014-12-11 16:09:05 UTC

This is really an upstream bug, I will attempt to file an issue with the upstream maintainer

Comment 3 Richard Purdie 2017-06-20 10:49:19 UTC

This seems to be an upstream issue in latencytop and is something the upstream software project would have to resolve if they have any interest in doing so, its not something the Yocto Project plan to resolve.