[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220607162504.7fd5a92a@canb.auug.org.au>
Date: Tue, 7 Jun 2022 16:25:04 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Linux-Next Mailing List <linux-next@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
regressions@...ts.linux.dev, lkft-triage@...ts.linaro.org,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-mm <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ard Biesheuvel <ardb@...nel.org>,
Arnd Bergmann <arnd@...db.de>,
Catalin Marinas <catalin.marinas@....com>,
Raghuram Thammiraju <raghuram.thammiraju@....com>,
Mark Brown <broonie@...nel.org>, Will Deacon <will@...nel.org>,
Shakeel Butt <shakeelb@...gle.com>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Vasily Averin <vvs@...nvz.org>,
Qian Cai <quic_qiancai@...cinc.com>
Subject: Re: [next] arm64: boot failed - next-20220606
Hi Naresh,
On Tue, 7 Jun 2022 11:00:39 +0530 Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
>
> On Mon, 6 Jun 2022 at 17:16, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> >
> > Linux next-20220606 arm64 boot failed. The kernel boot log is empty.
> > I am bisecting this problem.
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> >
> > The initial investigation show that,
> >
> > GOOD: next-20220603
> > BAD: next-20220606
> >
> > Boot log:
> > Starting kernel ...
>
> Linux next-20220606 and next-20220607 arm64 boot failed.
> The kernel panic log showing after earlycon.
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
Can you test v5.19-rc1, please? If that does not fail, then you could
bisect between that and next-20220606 ...
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists