public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1)
Date: Wed, 15 Jun 2016 12:50:00 +0200	[thread overview]
Message-ID: <6653268.nXQo6Otgxu@wuerfel> (raw)
In-Reply-To: <20160615091806.GU3240@piout.net>

On Wednesday, June 15, 2016 11:18:06 AM CEST Alexandre Belloni wrote:
> On 15/06/2016 at 11:10:29 +0200, Arnd Bergmann wrote :
> > On Tuesday, June 14, 2016 6:18:08 PM CEST kernelci. org bot wrote:
> > > arm:
> > > 
> > >     multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
> > >         exynos5410-odroidxu: 1 failed lab
> > > 
> > >     multi_v7_defconfig+CONFIG_LKDTM=y:
> > >         exynos5410-odroidxu: 1 failed lab
> > > 
> > >     multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y+CONFIG_ARM_MODULE_PLTS=y:
> > >         exynos5410-odroidxu: 1 failed lab
> > > 
> > >     multi_v7_defconfig+CONFIG_EFI=y:
> > >         exynos5410-odroidxu: 1 failed lab
> > > 
> > >     exynos_defconfig:
> > >         exynos5410-odroidxu: 1 failed lab
> > > 
> > >     multi_v7_defconfig+CONFIG_ARM_LPAE=y:
> > >         exynos5410-odroidxu: 1 failed lab
> > > 
> > >     multi_v7_defconfig:
> > >         exynos5410-odroidxu: 1 failed lab
> > > 
> > >     multi_v5_defconfig:
> > >         at91sam9261ek: 1 failed lab
> > >         at91sam9m10g45ek: 1 failed lab
> > >         at91sam9x25ek: 1 failed lab
> > >         at91sam9x35ek: 1 failed lab
> > 
> > These all seem to have broken after yesterday's merges, adding
> > Alexandre and Krzysztof to Cc here so they can have a look.
> > 
> 
> Well, multi_v5 is not broken, this is an issue with the lab setup that
> is being solved right now.
> As for multi_v7, as the 8250 driver is included in multi_v5, the Atmel
> UARTs are called ttyATx instead of ttySx. Until now,
> "console=ttyS0,115200" was passed to the kernel, hence no output was
> present on the UART but the boards are booting fine.

Ok, thanks for having a look!

	Arnd

  reply	other threads:[~2016-06-15 10:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5760acd0.571a1c0a.34a58.7333@mx.google.com>
2016-06-15  9:10 ` arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1) Arnd Bergmann
2016-06-15  9:18   ` Alexandre Belloni
2016-06-15 10:50     ` Arnd Bergmann [this message]
2016-06-15 18:07   ` Kevin Hilman
2016-06-15 19:12     ` Krzysztof Kozlowski
2016-06-15 20:08       ` 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=6653268.nXQo6Otgxu@wuerfel \
    --to=arnd@arndb.de \
    --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