From: Jan Kiszka <jan.kiszka@web.de>
To: "Proctor, Frederick M. (Fed)" <frederick.proctor@nist.gov>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: IPIPE patch causes hang during initrd boot; Ubuntu 18 desktop system
Date: Tue, 11 Jun 2019 11:09:08 +0200 [thread overview]
Message-ID: <4b6996dc-e425-cdfd-b95e-48c2aaa100d6@web.de> (raw)
In-Reply-To: <SN6PR09MB3069382F832609A66E69622A80100@SN6PR09MB3069.namprd09.prod.outlook.com>
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 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
next prev parent reply other threads:[~2019-06-11 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 13:02 IPIPE patch causes hang during initrd boot; Ubuntu 18 desktop system Proctor, Frederick M. (Fed)
2019-06-11 9:09 ` Jan Kiszka [this message]
2019-06-12 12:37 ` Proctor, Frederick M. (Fed)
2019-06-12 13:05 ` Jan Kiszka
2019-06-13 16:36 ` Jan Kiszka
2019-06-13 19:12 ` Jan Kiszka
2019-06-13 19:46 ` Proctor, Frederick M. (Fed)
2019-06-12 13:19 ` Philippe Gerum
2019-06-12 13:55 ` Proctor, Frederick M. (Fed)
2019-06-12 14:01 ` Philippe Gerum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4b6996dc-e425-cdfd-b95e-48c2aaa100d6@web.de \
--to=jan.kiszka@web.de \
--cc=frederick.proctor@nist.gov \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.