[Xenomai] Xenomai: halcmd cannot map MAYDAY page
rpm at xenomai.org
Tue Dec 19 12:55:25 CET 2017
On 12/14/2017 06:07 PM, John Allwine wrote:
> I'm using the latest machinekit image for the 3.8 kernel on the Beaglebone
> Black (
> It's using xenomai 2.6.3. I follow the steps in this document to set up
> machinekit as a systemd service:
2.6.3 is fairly outdated, but I guess you have no choice with machinekit
at the moment.
> When I start machinekit manually after bootup, it seems to work fine. When
> the services are started during boot up as a systemd service, I get the
> following error (I can provide the full stack trace if that would help):
> [ 19.501859] Xenomai: halcmd cannot map MAYDAY page
> [ 19.956681] Unable to handle kernel NULL pointer dereference at virtual
> address 00000004
> [ 19.965136] pgd = de414000, hw pgd = de414000
> [ 19.969675]  *pgd=9e7c4831, *pte=00000000, *ppte=00000000
> [ 19.976229] Internal error: Oops: 817 [#1
> <https://github.com/machinekit/machinekit/issues/1>] THUMB2
> [ 19.981128] Modules linked in: g_ether libcomposite cpufreq_userspace
> I filed this issue on machinekit's github repo as well:
> Any thoughts on what the problem could be? Or how to debug this further?
Assuming the crash is an unexpected side-effect of not being able to map
the mayday page, the latter would be the issue to chase. Mapping the
mayday page to a userland app requires to have access to a chrdev named
/dev/rtheap, created by the Xenomai core, and later exposed by udev.
This mapping fails.
Since systemd is involved, I suspect that a real-time application
(halcmd?) is started by some unit before the Xenomai core has fully
More information about the Xenomai