[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4ivjC8fNkfjdFyaYCAjGh7wtvFQnoPpOcR=VNZ=c6d6Rg@mail.gmail.com>
Date: Tue, 26 Feb 2019 16:04:04 -0800
From: Dan Williams <dan.j.williams@...el.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Mark Brown <broonie@...nel.org>,
"kernelci.org bot" <bot@...nelci.org>,
Tomeu Vizoso <tomeu.vizoso@...labora.com>,
guillaume.tucker@...labora.com, matthew.hart@...aro.org,
Stephen Rothwell <sfr@...b.auug.org.au>, khilman@...libre.com,
enric.balletbo@...labora.com, Nicholas Piggin <npiggin@...il.com>,
Dominik Brodowski <linux@...inikbrodowski.net>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Kees Cook <keescook@...omium.org>,
Adrian Reber <adrian@...as.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Johannes Weiner <hannes@...xchg.org>,
Linux MM <linux-mm@...ck.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Michal Hocko <mhocko@...e.com>,
Richard Guy Briggs <rgb@...hat.com>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>
Subject: Re: next/master boot bisection: next-20190215 on beaglebone-black
On Tue, Feb 26, 2019 at 4:00 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Fri, 15 Feb 2019 18:51:51 +0000 Mark Brown <broonie@...nel.org> wrote:
>
> > On Fri, Feb 15, 2019 at 10:43:25AM -0800, Andrew Morton wrote:
> > > On Fri, 15 Feb 2019 10:20:10 -0800 (PST) "kernelci.org bot" <bot@...nelci.org> wrote:
> >
> > > > Details: https://kernelci.org/boot/id/5c666ea959b514b017fe6017
> > > > Plain log: https://storage.kernelci.org//next/master/next-20190215/arm/multi_v7_defconfig+CONFIG_SMP=n/gcc-7/lab-collabora/boot-am335x-boneblack.txt
> > > > HTML log: https://storage.kernelci.org//next/master/next-20190215/arm/multi_v7_defconfig+CONFIG_SMP=n/gcc-7/lab-collabora/boot-am335x-boneblack.html
> >
> > > Thanks.
> >
> > > But what actually went wrong? Kernel doesn't boot?
> >
> > The linked logs show the kernel dying early in boot before the console
> > comes up so yeah. There should be kernel output at the bottom of the
> > logs.
>
> I assume Dan is distracted - I'll keep this patchset on hold until we
> can get to the bottom of this.
Michal had asked if the free space accounting fix up addressed this
boot regression? I was awaiting word on that.
I assume you're not willing to entertain a "depends
NOT_THIS_ARM_BOARD" hack in the meantime?
Powered by blists - more mailing lists