From: Mark Brown <broonie@kernel.org>
To: Kevin hilman <khilman@baylibre.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-next@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
"kernelci.org bot" <bot@kernelci.org>,
kernel-build-reports@lists.linaro.org
Subject: Re: next/master boot: 173 boots: 4 failed, 136 passed with 32 offline, 1 untried/unknown (next-20180710)
Date: Tue, 10 Jul 2018 15:02:13 +0100 [thread overview]
Message-ID: <20180710140213.GB8104@sirena.org.uk> (raw)
In-Reply-To: <5b44b87b.1c69fb81.97804.0122@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1163 bytes --]
On Tue, Jul 10, 2018 at 06:45:31AM -0700, kernelci.org bot wrote:
Today's linux-next fails to boot on mt7622-rfb1 with defconfig and
defconfig+RANDOMIZE_BASE:
> arm64:
> defconfig:
> mt7622-rfb1:
> lab-baylibre-seattle: new failure (last pass: next-20180709)
> defconfig+CONFIG_RANDOMIZE_BASE=y:
> mt7622-rfb1:
> lab-baylibre-seattle: new failure (last pass: next-20180709)
I'm not 100% sure if this is a lab failure or an early boot failure:
| Starting kernel ...
| [ATF][ 34.233534]save kernel info
| [ATF][ 34.236565]Kernel_EL2
| [ATF][ 34.239322]Kernel is 64Bit
| [ATF][ 34.242509]pc=0x40080000, r0=0x5cf48000, r1=0x0
| INFO: BL3-1: Preparing for EL3 exit to normal world, Kernel
| INFO: BL3-1: Next image address = 0x40080000
| INFO: BL3-1: Next image spsr = 0x3c9
| [ATF][ 34.260778]el3_exit
| ~$off
| # PYBOOT: Exception: kernel: ERROR: did not start booting.
It only seems to affect this platform, other arm64 platforms seem fine.
More details at:
https://kernelci.org/boot/id/5b44981a59b5141e5996baa1/
for the defconfig case, symptoms seem similar with RANDOMIZE_BASE.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2018-07-10 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5b44b87b.1c69fb81.97804.0122@mx.google.com>
2018-07-10 14:02 ` Mark Brown [this message]
2018-07-12 6:01 ` next/master boot: 173 boots: 4 failed, 136 passed with 32 offline, 1 untried/unknown (next-20180710) Sean Wang
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=20180710140213.GB8104@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bot@kernelci.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
/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