linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eddie.huang@mediatek.com (Eddie Huang)
To: linux-arm-kernel@lists.infradead.org
Subject: MTK mt8173-evb: mainline unstable, and big-endian boot failures
Date: Thu, 28 Jan 2016 14:56:20 +0800	[thread overview]
Message-ID: <1453964180.26397.8.camel@mtksdaap41> (raw)
In-Reply-To: <CAF-23O3ps0Wt_UCmJbArpc5iJJryJKA0k_2qAyNb7op8O=UnAg@mail.gmail.com>

On Thu, 2016-01-28 at 13:41 +0800, Koan-Sin Tan wrote:
> Hi Kevin, 
> 
> On Thu, Jan 28, 2016 at 9:16 AM, Kevin Hilman <khilman@baylibre.com>
> wrote:
>         Kevin Hilman <khilman@baylibre.com> writes:
>         
>         [...]
>         
>         > It seems to be pretty stable up through v4.4 but
>         > unreliable/unpredictable in v4.5-rc1 and lots of places in
>         between.
>         > It's hard to bisect because it doesn't reliably fail, but
>         when it does
>         > fail to finish booting, it's typically after it reaches a
>         shell, and
>         > trying to run various simple shell commands fails to
>         complete, like
>         > this example from next-20160125[2].
>         >
>         > To me this suggests possibly an issue with the idle driver
>         where
>         > characters might be getting lost on the serial console,
>         which causes
>         > the automated boot scripts to fail because the shell is
>         still waiting
>         > for the command to be finished.
>         
>         FWIW, I think I confirmed my suspicion that it's an idle
>         driver issue
>         because adding 'nohlt' on the cmdline, which forces
>         cpuidle_poll mode
>         (essentially disabling cpuidle) makes mainline boot quite
>         reliably on my
>         mt8173-evb board now.
> 
> 
>    Thanks for the information. I'll try to reproduce it. The problem
> is that I have been using 4.5-rc1 based kernel for several days, but
> didn't run into such problem. Can tell me which version of firmware
> you are using? 

Hi Kevin,

I use firmware [0] to run kernel v4.5-rc1 on my MT8173-evb, both branch
v20150716 (psci-0.2 atf) and v20150902 (psci-1.0 atf) can't reproduce
this problem.

[0]: https://github.com/ibanezchen/evb-utils

Eddie

>   
>    And, YES, I can reproduce the CONFIG_CPU_BIG_ENDIAN=y problem. The
> 'nohlt' command line option didn't stop the problem. We'll investigate
> it.
> 
> 
> -- 
> // freedom

  parent reply	other threads:[~2016-01-28  6:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28  0:55 MTK mt8173-evb: mainline unstable, and big-endian boot failures Kevin Hilman
2016-01-28  1:16 ` Kevin Hilman
     [not found]   ` <CAF-23O3ps0Wt_UCmJbArpc5iJJryJKA0k_2qAyNb7op8O=UnAg@mail.gmail.com>
2016-01-28  6:56     ` Eddie Huang [this message]
2016-01-30  0:09       ` Kevin Hilman
2016-02-01  6:49         ` Eddie Huang
2016-02-02  1:17           ` Kevin Hilman
2016-02-02  2:17             ` Fan Chen
2016-02-02 18:46               ` Kevin Hilman
2016-02-03  1:38                 ` Fan Chen
2016-02-03  6:44                   ` Kevin Hilman
     [not found] ` <CAF-23O2y7qRB=ZoU8cn2gcX7rjFdXh+rdLXSjF1nnym79Mknug@mail.gmail.com>
2016-01-28  9:37   ` Johannes Berg

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=1453964180.26397.8.camel@mtksdaap41 \
    --to=eddie.huang@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).