All of lore.kernel.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: mirabox boot fails in linux-next (was: next boot: 94 boots: 79 pass, 13 fail, 2 untried (next-20141117))
Date: Mon, 17 Nov 2014 19:21:46 +0100	[thread overview]
Message-ID: <20141117192146.23df4006@free-electrons.com> (raw)
In-Reply-To: <7h61ed4xm3.fsf@deeprootsystems.com>

Dear Kevin Hilman,

On Mon, 17 Nov 2014 08:09:56 -0800, Kevin Hilman wrote:
> FYI...
> 
> armada-370-mirabox started failing boot tests in linux-next as of
> next-20141117.  Excerpt of boot report below, or you can see all the recent
> boots of mirabox here:
> 
>    http://status.armcloud.us/boot/?mirabox
> 
> I bisected it down to a PCI commit[2], but it didn't revert cleanly on
> top of next/master so didn't fully verify it is the root cause.  I'll
> let one of you MVEBU maintainers take it the next step.

Thanks a lot for the report, very useful. I haven't yet looked at the
PCI commit itself, but reading the commit log indicates that it plays
with sizing the BARs, and we're doing some fairly funky stuff with this
in pci-mvebu, so I'm not entirely surprised such a commit can break
stuff. I'll have a look tomorrow.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2014-11-17 18:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1XqKYI-0000pQ-4b@ip-10-35-177-41.ec2.internal>
2014-11-17 15:57 ` exynos boot falures in linux-next (was: next boot: 94 boots: 79 pass, 13 fail, 2 untried (next-20141117)) Kevin Hilman
2014-11-17 16:57   ` exynos boot falures in linux-next Krzysztof Kozłowski
2014-11-17 16:57     ` Krzysztof Kozłowski
2014-11-17 22:24   ` Kevin Hilman
2014-11-17 22:24     ` Kevin Hilman
2014-11-17 23:25     ` Javier Martinez Canillas
2014-11-17 23:25       ` Javier Martinez Canillas
2014-11-18  2:30       ` Inki Dae
2014-11-18  2:30         ` Inki Dae
2014-11-18  3:49       ` Kevin Hilman
2014-11-18  3:49         ` Kevin Hilman
2014-11-19 17:01         ` Kevin Hilman
2014-11-19 17:01           ` Kevin Hilman
2014-11-19 17:06           ` Javier Martinez Canillas
2014-11-19 17:06             ` Javier Martinez Canillas
2014-11-20  1:55             ` Kukjin Kim
2014-11-20  1:55               ` Kukjin Kim
2014-12-02  8:32               ` Javier Martinez Canillas
2014-12-02  8:32                 ` Javier Martinez Canillas
     [not found] ` <7h61ed4xm3.fsf@deeprootsystems.com>
2014-11-17 18:21   ` Thomas Petazzoni [this message]

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=20141117192146.23df4006@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 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.