linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Wang <sean.wang@mediatek.com>
To: Mark Brown <broonie@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>
Cc: "kernelci.org bot" <bot@kernelci.org>,
	kernel-build-reports@lists.linaro.org,
	Kevin hilman <khilman@baylibre.com>,
	linux-next@vger.kernel.org, linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: next/master boot: 173 boots: 4 failed, 136 passed with 32 offline, 1 untried/unknown (next-20180710)
Date: Thu, 12 Jul 2018 14:01:44 +0800	[thread overview]
Message-ID: <1531375304.26214.26.camel@mtkswgap22> (raw)
In-Reply-To: <20180710140213.GB8104@sirena.org.uk>

Hi, Mark

thanks for reporting this issue.

I have fixed the issue in [1], which is caused by an update on pinctrl
core and the driver doesn't have an immediate follow-up to the change.

Hi, Matthias

Could you help to add earlycon I posted in [2], which is helpful to
identify at which point the boot is stuck instead of no any hint in the
console?

[1]
http://lists.infradead.org/pipermail/linux-mediatek/2018-July/014070.html


[2]
http://lists.infradead.org/pipermail/linux-mediatek/2018-June/013709.html


On Tue, 2018-07-10 at 15:02 +0100, Mark Brown wrote:
> 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.
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek

      reply	other threads:[~2018-07-12  6:01 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 ` next/master boot: 173 boots: 4 failed, 136 passed with 32 offline, 1 untried/unknown (next-20180710) Mark Brown
2018-07-12  6:01   ` Sean Wang [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=1531375304.26214.26.camel@mtkswgap22 \
    --to=sean.wang@mediatek.com \
    --cc=bot@kernelci.org \
    --cc=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=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;
as well as URLs for NNTP newsgroup(s).