linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: khilman@baylibre.com, Matthias Brugger <matthias.bgg@gmail.com>,
	linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Cc: kernel-build-reports@lists.linaro.org
Subject: Re: next/master boot: 310 boots: 11 failed, 292 passed with 6 offline, 1 untried/unknown (next-20190904)
Date: Wed, 4 Sep 2019 20:27:26 +0100	[thread overview]
Message-ID: <20190904192725.GI4348@sirena.co.uk> (raw)
In-Reply-To: <5d700b15.1c69fb81.2abcd.479b@mx.google.com>


[-- Attachment #1.1: Type: text/plain, Size: 959 bytes --]

On Wed, Sep 04, 2019 at 12:05:57PM -0700, kernelci.org bot wrote:

Since 30th August -next fails to boot with no kernel output on
mt7622-rfb1:

> arm64:
>     defconfig:
>         gcc-8:
>             mt7622-rfb1: 1 failed lab
> 
>     defconfig+CONFIG_RANDOMIZE_BASE=y:
>         gcc-8:
>             mt7622-rfb1: 1 failed lab

There's logging from ATF so it looks like we try to boot the kernel:

Starting kernel ...

[ATF][    36.199793]save kernel info
[ATF][    36.202824]Kernel_EL2
[ATF][    36.205580]Kernel is 64Bit
[ATF][    36.208768]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][    36.227037]el3_exit

but no output.  More details including full logs at:

	https://kernelci.org/boot/id/5d6fe70059b514164ef1224d/
	https://kernelci.org/boot/id/5d6fe6e259b514164ef12243/

[-- 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

       reply	other threads:[~2019-09-04 19:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5d700b15.1c69fb81.2abcd.479b@mx.google.com>
2019-09-04 19:27 ` Mark Brown [this message]
2019-09-05  0:15   ` next/master boot: 310 boots: 11 failed, 292 passed with 6 offline, 1 untried/unknown (next-20190904) Kevin Hilman
2019-09-05 15:39     ` Mark Brown
2019-09-05 15:40       ` Christoph Hellwig
2019-09-05 15:43         ` Mark Brown
2019-09-05 17:02       ` Catalin Marinas
2019-09-05 19:43         ` 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=20190904192725.GI4348@sirena.co.uk \
    --to=broonie@kernel.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=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;
as well as URLs for NNTP newsgroup(s).