On 6/12/19 2:37 PM, Proctor, Frederick M. (Fed) via Xenomai wrote: >> On 07.06.19 15:02, Proctor, Frederick M. (Fed) via Xenomai wrote: >>> I am installing Xenomai + Cobalt with the IPIPE patch on a Ubuntu >>> 18-based x86/64 desktop system. I have these versions: >>> >>> Linux kernel 4.14.71 PREEMPT_RT patch 4.14.71-rt44 IPIPE 4.14.71 >> >> Latest stable I-pipe version is ipipe-core-4.14.111-x86-3. >> > > I was using 4.14.71 since it has patches for both IPIPE and PREEMPT_RT. I had > used 4.14.111 also, but had the same kernel hang problem at boot time. > >>> >>> I have compiled the kernel three different ways: the stock >>> configuration, with the PREEMPT_RT patch, and with the IPIPE patch (no >>> PREEMPT_RT). I have configured out the ACPI processor, CPU_FREQ, and >>> CPU_IDLE options in all cases. The first two boot fine (stock kernel, >>> PREEMPT_RT). The IPIPE-patched kernel hangs during the initrd loading >>> phase. >>> >>> I've tailored the kernel configuration somewhat based on the hardware >>> I have, but nothing has worked to get a booting IPIPE kernel. >>> >>> Does anyone have guidance on setting up the IPIPE patch on an x86/64 >>> kernel on a desktop Ubuntu 18 machine? I am planning on continuing to >>> trim down the kernel config options, but before I do this, I want to >>> ask this group if anyone has had a similar problem. >>> >> >> Does yous system start to boot again when the I-pipe kernel is built without >> CONFIG_IPIPE and CONFIG_XENOMAI? If no, compare the config to a >> working one, step-wise aligning to it. >> >> Jan > > Yes it does - with the kernel patched with IPIPE and Xenomai, but with IPIPE > and Xenomai *not selected* in the kernel config, the kernel boots fine. With > IPIPE and Xenomai *selected* in a subsequent kernel config, that kernel > hangs. Here's the diff on the config files:
This may be a timer issue. You could try booting with xenomai.state=stopped on the kernel command line. If that boots as I suspect, then you can try issuing the following command: $ corectl --start If that starts the core properly and no lockup, then this may have to do with the timer grabbing sequence proper. If that hangs, then this may be a general issue with the timing device when handling ticks for real-time delivery. -- Philippe.
