ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #08435
Re: Identifying memory issues, #2
On Thu, Jun 05, 2014 at 11:22:25AM +0200, Oliver Grawert wrote:
> Am Mittwoch, den 04.06.2014, 11:07 -0700 schrieb Steve Langasek:
> > Hi Colin,
> > On Wed, Jun 04, 2014 at 06:44:08PM +0100, Colin Ian King wrote:
> > > I suggest trying out smemstat which is my in my PPA: ppa:colin-king/white
> > > see: http://kernel.ubuntu.com/~cking/smemstat/
> > > one can run this with a suitable delay and capture any memory changes
> > > over a specified number of iterations. The data can be also output to a
> > > JSON formatted file for later processing and analysis.
> > Are you targeting smemstat for inclusion in Ubuntu for utopic? Should we
> > consider including smemstat in the phone images, so that we have it to hand
> > for debugging when we need it?
> we discussed these tools at the sprint and I took a TODO home with me to
> implement proper script wrappers around these tools in the phablet-tools
> suite (i.e. resulting in phablet-memtest, phablet-powertest etc) so we
> can have properly comparable reports from a combination of pre defined
> test runs ... eventually these tools will then be integrated in the
> smoke testing suite. I will announce it here once we have something
> usable ....
But putting them into the smoketest suite doesn't give them to us in the
image, correct? So this would still limit our ability to use them for
opportunistic debugging.
Given that these tools are all (AIUI) small, it would be nice to have them
there. You never know when you're going to need to debug an issue, and if
you have to remount rw and install a .deb to catch it, it may be too late.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek@xxxxxxxxxx vorlon@xxxxxxxxxx
Attachment:
signature.asc
Description: Digital signature
Follow ups
References