[Xenomai] i-pipe patched 4.1.18 fails to boot on BeagleBoard-x15 (AM5728 processor)
ckiorpes at gmail.com
Thu Apr 14 21:54:12 CEST 2016
Thanks for the suggestion to disable PROVE_LOCKING. Disabling this and a
few other of the kernel trace/debug options has cleared up my output a bit.
I used addr2line on the vmlinux image, it pointed me to
kernel/ipipe/core.c:1304. This is in the midst of __ipipe_dispatch_irq().
The line directly before involves the use of a function pointer, but that
pointer is null checked before use.
I have checked the disassembly; the null check is present, yet somehow the
PC is being set to 0.
I have tried removing the palmas device from the kernel configuration, and
I still get a null dereference at the same location in
I will continue to try to discern what is going on here, particularly
concerning the values that are passed into __ipipe_dispatch_irq()
If you see any other things I should check out, please let me know.
On Wed, Apr 13, 2016 at 2:27 PM, Philippe Gerum <rpm at xenomai.org> wrote:
> On 04/13/2016 08:04 PM, Charles Kiorpes wrote:
> > Hello,
> > I have been trying to bring up a Rev A2 BeagleBoard-x15 with i-pipe, in
> > order to test Xenomai co-kernel functionality on this board.
> > I have verified that the kernel configuration settings that I'm using
> > create a bootable mainline 4.1.18 kernel.
> > Once I patch the 4.1.18 kernel with ipipe-core-4.1.18-arm-4.patch, and
> > the same configuration changes, I am unable to boot the resulting kernel.
> > I have attached my kernel config and the kernel output from a failed
> > The first major error (aside from some lock debug printouts) occurs at
> Those printouts are due to CONFIG_PROVE_LOCKING. The virtual interrupt
> state the pipeline introduces confuses that machinery, so you may want
> to disable this option until the pipeline is fixed regarding that
> particular issue.
> > 2.141340, when the kernel attempts to dereference a NULL pointer.
> > It appears that the problem is related to the PALMAS driver, but I am not
> > well-versed in kernel development and don't know how to proceed.
> > What steps can I take to better debug and eventually correct the problem?
> A NULL handler is called, weird. You can use addr2line on the vmlinux
> image of your kernel to match the faulty call site at 0xc00d00cc. Or
> dump that image as an annotated assembly file
> (arm-linux-gnueabihf-objdump -dl ...), looking for the call site in the
> You will need CONFIG_DEBUG_INFO enabled.
More information about the Xenomai