lttng on aarch64 platform
Quoted 19 lines · ----- On Nov 27, 2015, at 6:30 PM, Ronan CHAUVIN [email protected] 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(inlaunch_sessiond()atcommands/create.c:668) Spawning a session daemon
DEBUG1 - 02:36:24.275751 [850/850]: Session daemon terminated normally (exit status: 1) (inspawn_sessiond()atcommands/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 (inclean_exit()at lttng.c:193)
Quoted 2 lines
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
Quoted 19 lines
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
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Signature · 3 lines
Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com
Hi Mathieu,
Thank you for your answer. I have investigated the issue.
The trap wasn't the reason why the daemon was exited. The kernel doesn't kill the process when an unknow system call is invoked. As you mentioned some functionalities will not be available on this kernel version as it doesn't have new membarrier system call implementation.
I launched the daemon independently and got the following error:
"Error: URI parse bad hostname localhost for af 2 Segmentation fault
/# boxinit: untracked pid 12292 'lttng-runas' exited"
This behavior comes from the gethostbyname2 function used at src/common/uri.c line 119. It seems that this function read the /etc/hosts file which was not present on my system.
Everything else works fine.
Thanks for your help,
Ronan
Quoted 53 lines · Mathieu Desnoyers
Quoted 19 lines · ----- On Nov 27, 2015, at 6:30 PM, Ronan CHAUVIN [email protected] 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(inlaunch_sessiond()atcommands/create.c:668) Spawning a session daemon
DEBUG1 - 02:36:24.275751 [850/850]: Session daemon terminated normally (exit status: 1) (inspawn_sessiond()atcommands/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 (inclean_exit()at lttng.c:193)Quoted 2 lines
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
Quoted 18 lines
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
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Hi Mathieu,
I have another question related the syscall information on aarch64 platforms. It doesn't seems to be present on lttng 2.7.0 on my traces.
Do we need to extract and generate the syscall headers via extractor and script in lttng-modules for our kernel version (3.10.67)?
Thanks.
Ronan
Quoted 75 lines · Ronan CHAUVIN
Hi Mathieu,
Thank you for your answer. I have investigated the issue.
The trap wasn't the reason why the daemon was exited. The kernel doesn't kill the process when an unknow system call is invoked. As you mentioned some functionalities will not be available on this kernel version as it doesn't have new membarrier system call implementation.
I launched the daemon independently and got the following error:
"Error: URI parse bad hostname localhost for af 2 Segmentation fault
/# boxinit: untracked pid 12292 'lttng-runas' exited"This behavior comes from the gethostbyname2 function used at
src/common/uri.cline 119. It seems that this function read the/etc/hostsfile which was not present on my system.Everything else works fine.
Thanks for your help,
Ronan to genarate header
Quoted 54 lines · Mathieu Desnoyers
----- On Nov 27, 2015, at 6:30 PM, Ronan CHAUVIN
Quoted 19 lines · [email protected] 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(inlaunch_sessiond()atcommands/create.c:668) Spawning a session daemon
DEBUG1 - 02:36:24.275751 [850/850]: Session daemon terminated normally (exit status: 1) (inspawn_sessiond()atcommands/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 (inclean_exit()at lttng.c:193)Quoted 2 lines
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
Quoted 18 lines
Thanks in advance,
Signature · 15 lines
Ronan CHAUVIN Embedded Software Engineer ASIC & Video team -------------------------------- Parrot SA 174, quai de Jemmapes 75010 Paris, France -------------------------------- www.parrot.com _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev