From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ryan.Kyser@jci.com (Ryan.Kyser@jci.com)
Date: Wed, 11 Apr 2012 15:21:50 -0400
Subject: [lttng-dev] ARM syscall problems
In-Reply-To: <alpine.LFD.2.02.1204102117400.16314@xanadu.home>
References: <OF8C6B987A.03E85273-ON852579DC.006DE8C4-852579DC.007723B3@jci.com>
	<20120411005030.GB4690@Krystal>
	<alpine.LFD.2.02.1204102117400.16314@xanadu.home>
Message-ID: <OFC6969E03.0769F094-ON852579DD.006A4E14-852579DD.006A5E9B@jci.com>

Thank you -- that helped solve my problem.

Ryan Kyser




From:
Nicolas Pitre <nicolas.pitre at linaro.org>
To:
Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
Cc:
Ryan.Kyser at jci.com, lttng-dev at lists.lttng.org, Avik Sil 
<avik.sil at linaro.org>
Date:
04/10/2012 09:20 PM
Subject:
Re: [lttng-dev] ARM syscall problems



On Tue, 10 Apr 2012, Mathieu Desnoyers wrote:

> * Ryan.Kyser at jci.com (Ryan.Kyser at jci.com) wrote:
> > 2.) I'm seeing a sys_unknown with a suspicious NR ID of 983045. Any 
ideas 
> > on how to further debug this problem?
> > [19:01:09.009343858] (+0.000020500) sys_unknown: { 0 }, { id = 983045, 

> > args = [ [0] = 715846848, [1] = 715848600, [2] = 716677200, [3] = 
> > 715846848, [4] = 716677200, [5] = 1 ] }
> 
> I'm CCing Avik and Nicolas, they might have a clue about this
> high-numbered syscall number.

983045 == 0xf0005 == __ARM_NR_set_tls


Nicolas