From: khilman@kernel•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: exynos5420/arndale-octa: imprecise external aborts on exynos_defconfig
Date: Wed, 17 Sep 2014 17:39:29 -0700 [thread overview]
Message-ID: <7hk351ep8e.fsf@deeprootsystems.com> (raw)
In-Reply-To: <CAJuA9ahkpZ4EJQz4DoAjYzo0OQw5zXLavAVoXRBdgPcm9EUQYA@mail.gmail.com> (Thomas Abraham's message of "Sat, 13 Sep 2014 18:29:58 +0530")
Thomas Abraham <ta.omasab@gmail•com> writes:
> On Thu, Sep 11, 2014 at 12:16 AM, Kevin Hilman <khilman@kernel•org> wrote:
>> Tyler Baker <tyler.baker@linaro•org> writes:
>>
>>> Exynos5420-based Arndale octa boards have recently started failing boot
>>> tests due to imprecise external aborts. This only appears to happen
>>> when using exynos_defconfig and boots fine with multi_v7_defconfig. The
>>> issue seems to be intermittent, so is not reliably reproducable and
>>> difficult to bisect. Here are a few boot logs from recent
>>> mainline/linux-next kernels that are failing:
>>
>> FYI, I'm seeing the same periodic aborts. For example, here's my boot
>> of next-20140910:
>> http://images.armcloud.us/kernel-ci/next/next-20140910/arm-exynos_defconfig/boot-exynos5420-arndale-octa.html
>>
>> However, my userspace is much simpler and doesn't seem to cause a panic,
>> so my boot tests report passing. (I should fixup my scripts so these
>> imprecise aborts are reported as a FAIL.)
>>
>> I'm glad you pointed out that it happens only with exynos_defconfig and
>> not multi_v7_defconfig because I noticed that too. I haven't had the
>> time to track it any further than that, so maybe the exynos folks can
>> help track it down from here.
>>
>> Thanks for reporting this,
>>
>> Kevin
>
> Hi Tyler, Kevin,
>
> From the bootlog you have shared,
>
> [ 1.060016] CPU4: failed to come online
> [ 2.070031] CPU5: failed to come online
> [ 3.080049] CPU6: failed to come online
> [ 4.090066] CPU7: failed to come online
> [ 4.090099] Brought up 4 CPUs
> [ 4.090109] SMP: Total of 4 processors activated.
> [ 4.090119] CPU: WARNING: CPU(s) started in wrong/inconsistent
> modes (primary CPU mode 0x13)
> [ 4.090128] CPU: This may indicate a broken bootloader or firmware.
>
> Would it be possible to set max cpus to 1, disable switcher and try
> again. I don't have a arndale octa board but I have tested mainline
> kernel with smdk5420 board. It boots all eight CPUs, switcher works
> fine and there are no imprecise aborts seen.
Sorry for the delay, I'm travelling this week.
FWIW, the same CPU boot failures you hilight above are happening on
multi_v7_defconfig[1] which is not getting the imprecise abort. This is
only happening on exynos_defconfig[2], so I'm curious why you think the
switcher or NR_CPUS might be the issues.
Anyways, I narrowed this down a bit and discovered it's
CONFIG_EXYNOS5420_MCPM=y that's the root cause. If I use
exynos_defconfig and then disable that option, I don't get any more
imprecise aborts.
Kevin
[1] http://images.armcloud.us/kernel-ci/mainline/v3.17-rc5-25-g8ba4caf/arm-multi_v7_defconfig/boot-exynos5420-arndale-octa.html
[2] http://images.armcloud.us/kernel-ci/mainline/v3.17-rc5-25-g8ba4caf/arm-exynos_defconfig/boot-exynos5420-arndale-octa.html
next prev parent reply other threads:[~2014-09-18 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 18:20 exynos5420/arndale-octa: imprecise external aborts on exynos_defconfig Tyler Baker
2014-09-10 18:46 ` Kevin Hilman
2014-09-13 12:59 ` Thomas Abraham
2014-09-18 0:39 ` Kevin Hilman [this message]
2014-09-30 18:17 ` Bartlomiej Zolnierkiewicz
2014-10-06 7:55 ` Thomas Abraham
2014-10-31 17:41 ` Kevin Hilman
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=7hk351ep8e.fsf@deeprootsystems.com \
--to=khilman@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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