From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: GP Orcullo <kinsamanka@gmail.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Boot failure when CONFIG_XENOMAI is enabled
Date: Wed, 18 Mar 2015 15:21:19 +0100 [thread overview]
Message-ID: <20150318142119.GF24525@hermes.click-hack.org> (raw)
In-Reply-To: <CACreCVLijm5Wup7aTrRTq=SHBmEUQY5D2pYpXThWXSrGqpcuqw@mail.gmail.com>
On Wed, Mar 18, 2015 at 10:11:06PM +0800, GP Orcullo wrote:
> Hi,
>
> I'm trying to port xenomai 2.6.4 on an Amlogic S805 board running a
> 3.10.33 non-mainlined kernel.
>
> The kernel boots with CONFIG_IPIPE enabled but without CONFIG_XENOMAI.
> Once CONFIG_XENOMAI is set, the boot fails.
>
> Attached are the .config and the bootlog files. Turning
> CONFIG_SMP_ON_UP off gives a different result.
>
> Any pointers on where to start looking?
here:
https://xenomai.org/2014/09/porting-xenomai-dual-kernel-to-a-new-arm-soc/
Your diagnostic is not consistent with the kernel messages: the only
difference between CONFIG_XENOMAI and !CONFIG_XENOMAI is when
xenomai starts, however your kernel crashes before xenomai starts.
Your problem is probably, as usual, in the timer handling code, or
tsc emulation.
Other than that, I would disable the usually not recommended kernel
options.
--
Gilles.
next prev parent reply other threads:[~2015-03-18 14:21 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 14:11 [Xenomai] Boot failure when CONFIG_XENOMAI is enabled GP Orcullo
2015-03-18 14:21 ` Gilles Chanteperdrix [this message]
2015-03-18 14:48 ` GP Orcullo
2015-03-18 14:56 ` Gilles Chanteperdrix
2015-03-25 14:48 ` GP Orcullo
2015-03-25 14:57 ` Gilles Chanteperdrix
2015-03-25 15:25 ` GP Orcullo
2015-03-25 16:08 ` Gilles Chanteperdrix
2015-03-25 23:44 ` GP Orcullo
2015-03-27 10:19 ` GP Orcullo
2015-03-27 12:12 ` GP Orcullo
2015-03-28 9:05 ` GP Orcullo
2015-03-28 9:51 ` Philippe Gerum
2015-03-28 11:36 ` Gilles Chanteperdrix
2015-03-28 12:27 ` GP Orcullo
2015-03-28 13:06 ` Gilles Chanteperdrix
2015-03-28 13:12 ` Gilles Chanteperdrix
2015-03-28 13:22 ` Gilles Chanteperdrix
2015-03-28 13:37 ` Gilles Chanteperdrix
2015-03-28 15:20 ` GP Orcullo
2015-03-28 17:23 ` Gilles Chanteperdrix
2015-03-28 19:14 ` Gilles Chanteperdrix
2015-03-28 13:53 ` Gilles Chanteperdrix
2015-03-28 14:56 ` Gilles Chanteperdrix
2015-03-28 15:17 ` GP Orcullo
2015-03-28 15:19 ` Gilles Chanteperdrix
2015-03-28 15:56 ` GP Orcullo
2015-03-28 16:02 ` Gilles Chanteperdrix
2015-03-28 18:59 ` Gilles Chanteperdrix
2015-03-28 22:38 ` GP Orcullo
2015-03-29 11:06 ` Gilles Chanteperdrix
2015-03-29 11:59 ` GP Orcullo
2015-03-29 12:02 ` Gilles Chanteperdrix
2015-03-29 12:09 ` Gilles Chanteperdrix
2015-03-29 12:38 ` GP Orcullo
2015-03-29 12:44 ` Gilles Chanteperdrix
2015-03-29 12:56 ` GP Orcullo
2015-03-30 15:21 ` GP Orcullo
2015-03-30 15:28 ` Gilles Chanteperdrix
2015-04-10 20:08 ` Henry Bausley
2015-04-10 21:33 ` Gilles Chanteperdrix
2015-04-10 21:39 ` Gilles Chanteperdrix
2015-03-29 12:18 ` Gilles Chanteperdrix
2015-03-28 12:31 ` Philippe Gerum
2015-03-28 15:05 ` Gilles Chanteperdrix
2015-03-28 17:58 ` Philippe Gerum
2015-03-28 18:08 ` Philippe Gerum
2015-03-28 22:29 ` GP Orcullo
2015-03-28 18:10 ` Gilles Chanteperdrix
2015-03-28 18:18 ` Philippe Gerum
2015-03-28 18:28 ` Gilles Chanteperdrix
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=20150318142119.GF24525@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=kinsamanka@gmail.com \
--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.