[lttng-dev] lttng on aarch64 platform

[Mathieu Desnoyers]

----- On Nov 27, 2015, at 6:30 PM, Ronan CHAUVIN ronan.chauvin at parrot.com wrote:

> Hello all,
> 
> I am trying to use lttng 2.7.0 on an aarch64 platform. When I create my
> session a trap is triggered which indicated that a unknow syscall (389)
> is called.
> 
> / # lttng -vvv create mysession
> DEBUG1 - 02:36:22.271714 [850/850]: Session daemon binary path:
> /usr/bin/lttng-sessiond (in launch_sessiond() at commands/create.c:668)
> Spawning a session daemon
> DEBUG1 - 02:36:24.275751 [850/850]: Session daemon terminated normally
> (exit status: 1) (in spawn_sessiond() at commands/create.c:606)
> Error: Session daemon terminated with an error (exit status: 1)
> Error: Problem occurred while launching session daemon
> (/usr/bin/lttng-sessiond)
> Error: Command error
> DEBUG1 - 02:36:24.275899 [850/850]: Clean exit (in clean_exit() at
> lttng.c:193)
> 
> It seems that lttng-sessiond deamon is directly exited. Has anyone
> already tried on a 3.10 kernel and aarch64 platform?

Hi Ronan,

That's because your liburcu calls the new membarrier system call, which was
introduced later than your kernel. The way it works is that if the membarrier
system call returns -1, errno=ENOSYS, it falls-back to a liburcu implementation
which does not need the membarrier system call. This question here is: why
does your kernel trap when an unknown system call is invoked ?

Thanks,

Mathieu

> 
> Thanks in advance,
> 
> --
> Ronan CHAUVIN
> Embedded Software Engineer
> ASIC & Video team
> --------------------------------
> Parrot SA
> 174, quai de Jemmapes
> 75010 Paris, France
> --------------------------------
> www.parrot.com
> 
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com