All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: Boot issue with imx6 quad
Date: Thu, 29 May 2014 16:02:18 -0600	[thread overview]
Message-ID: <5387AE6A.2070408@mlbassoc.com> (raw)
In-Reply-To: <CAP9ODKq7YAus9TmnpY4fonqTWgnFJD9MBZL4WijsgT4qtQK9NA@mail.gmail.com>

On 2014-05-29 13:43, Otavio Salvador wrote:
> On Thu, May 29, 2014 at 1:12 PM, Jerome Smith <jerome.emb@gmail.com> wrote:
>> Hi all,
>> I'm facing a strange boot issue with Yocto Dora on a Freescale sabre auto
>> (quad and solo version).
>>
>> The configuration is the following:
>> * kernel 3.0.35
>> * systemd
>> * namespace
>> * linux containers
>>
>> The boot on imx6 Solo takes around 6 sec, instead on the Quad it takes
>> around 35 seconds.
>>
>> After boot both systems are responsive and work well.
>>
>> If I add nosmp to kernel cmdline the imx6 Quad boots as fast as the Solo.
>>
>> If I remove the namespace from the kernel the Quad system boots fast as
>> well. The problem seems to be caused by namespace and the way it interacts
>> with smp.
>>
>> Do you have any idea on how to solve the problem?
>
> My simple advise is for you to try  the Daisy branch with 3.10.17 and
> see if you reproduce it.
>

Also try using sysvinit instead of systemd - I've experienced some very
strange/slow startup times when using systemd, at least on i.MX6Q

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2014-05-29 22:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 16:12 Boot issue with imx6 quad Jerome Smith
2014-05-29 19:43 ` Otavio Salvador
2014-05-29 22:02   ` Gary Thomas [this message]
2014-05-30  5:59     ` Maciej Borzecki

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=5387AE6A.2070408@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=meta-freescale@yoctoproject.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.