From: Vlastimil Babka <vbabka@suse.cz>
To: Dan Williams <dan.j.williams@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Brown <broonie@kernel.org>,
"kernelci.org bot" <bot@kernelci.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
guillaume.tucker@collabora.com, matthew.hart@linaro.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
khilman@baylibre.com, enric.balletbo@collabora.com,
Nicholas Piggin <npiggin@gmail.com>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Kees Cook <keescook@chromium.org>, Adrian Reber <adrian@lisas.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Linux MM <linux-mm@kvack.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Michal Hocko <mhocko@suse.com>,
Richard Guy Briggs <rgb@redhat.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>
Subject: Re: next/master boot bisection: next-20190215 on beaglebone-black
Date: Fri, 1 Mar 2019 10:02:23 +0100 [thread overview]
Message-ID: <07d4e843-8023-2041-22a7-b5b589f4d2c0@suse.cz> (raw)
In-Reply-To: <CAPcyv4ivjC8fNkfjdFyaYCAjGh7wtvFQnoPpOcR=VNZ=c6d6Rg@mail.gmail.com>
On 2/27/19 1:04 AM, Dan Williams wrote:
> On Tue, Feb 26, 2019 at 4:00 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>> On Fri, 15 Feb 2019 18:51:51 +0000 Mark Brown <broonie@kernel.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@kernelci.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'm afraid it couldn't have. Bisection identified the "enable all
shuffling" patch, but the free area mis-accounting happened regardless
of shuffling being enabled. And if dropping the "enable all shuffling"
patch stopped the problem even before the misacounting fix was merged,
that's another confirmation.
Is it possible that the platform silently depends on large contiguous
areas without a proper CMA reservation, and the shuffling fragments
them? Or maybe the CMA reservation happens too late?
> I assume you're not willing to entertain a "depends
> NOT_THIS_ARM_BOARD" hack in the meantime?
>
next prev parent reply other threads:[~2019-03-01 9:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 18:20 kernelci.org bot
2019-02-15 18:43 ` Andrew Morton
2019-02-15 18:51 ` Mark Brown
2019-02-15 19:00 ` Andrew Morton
2019-02-16 6:21 ` Stephen Rothwell
2019-02-26 23:59 ` Andrew Morton
2019-02-27 0:04 ` Dan Williams
2019-02-28 23:14 ` Andrew Morton
2019-02-28 23:55 ` Dan Williams
2019-03-01 8:25 ` Guillaume Tucker
2019-03-01 10:40 ` Mike Rapoport
2019-03-01 11:49 ` Mark Brown
2019-03-01 20:41 ` Andrew Morton
2019-03-01 21:04 ` Guillaume Tucker
2019-03-01 23:23 ` Dan Williams
2019-03-06 10:14 ` Guillaume Tucker
2019-03-06 14:05 ` Mike Rapoport
2019-03-07 9:16 ` Guillaume Tucker
2019-03-07 15:43 ` Dan Williams
2019-04-10 22:52 ` Kees Cook
2019-04-11 16:42 ` Guenter Roeck
2019-04-11 17:35 ` Kees Cook
2019-04-11 20:08 ` Guenter Roeck
2019-04-11 20:22 ` Dan Williams
2019-04-11 20:53 ` Guenter Roeck
2019-04-16 18:54 ` Dan Williams
2019-04-16 19:17 ` Mathieu Desnoyers
2019-04-16 19:25 ` Mathieu Desnoyers
2019-04-16 19:45 ` Mathieu Desnoyers
2019-04-16 19:33 ` Guenter Roeck
2019-04-16 20:37 ` Dan Williams
2019-04-16 21:04 ` Guenter Roeck
2019-04-17 3:30 ` Kees Cook
2019-04-16 20:05 ` Mathieu Desnoyers
2019-04-11 20:49 ` Mike Rapoport
2019-03-01 11:45 ` Mark Brown
2019-03-01 9:02 ` Vlastimil Babka [this message]
2019-02-18 9:44 ` Michal Hocko
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=07d4e843-8023-2041-22a7-b5b589f4d2c0@suse.cz \
--to=vbabka@suse.cz \
--cc=adrian@lisas.de \
--cc=akpm@linux-foundation.org \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=enric.balletbo@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=hannes@cmpxchg.org \
--cc=keescook@chromium.org \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@dominikbrodowski.net \
--cc=mathieu.desnoyers@efficios.com \
--cc=matthew.hart@linaro.org \
--cc=mhocko@suse.com \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=rgb@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=tomeu.vizoso@collabora.com \
--cc=yamada.masahiro@socionext.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