public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed

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, 10 Sep 2014 11:46:14 -0700	[thread overview]
Message-ID: <7h7g1bwbyh.fsf@deeprootsystems.com> (raw)
In-Reply-To: <CANMBJr41TQx4jVjnOO9WThn=SiZCq12mx1xtGN8_ubzZrO1=YA@mail.gmail.com> (Tyler Baker's message of "Wed, 10 Sep 2014 11:20:19 -0700")

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

next prev parent reply	other threads:[~2014-09-10 18:46 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 [this message]
2014-09-13 12:59   ` Thomas Abraham
2014-09-18  0:39     ` Kevin Hilman
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=7h7g1bwbyh.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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox